Web2.5 Loyalty

Demo

About

The problem it solves Our team introduced the Web2.5 concept to address the shift from Web2 to Web3. We believe that Web3's fully decentralized model can be complex for end-users. By utilizing Flow's technology and adopting a hybrid custody model that provides the full benefits of both app and self-custody, including a user-friendly Walletness experience, we can apply blockchain to the Web2 model and simplify mass adoption for everyone. Traditional loyalty application are limited flexibility and often expired vouchers that cannot be traded or used beyond a specific date. Additionally, traditional vouchers lack transparency and can be difficult to track and redeem, resulting in delays and errors that frustrate both customers and businesses. These systems are also costly for businesses to produce, marketing and distribute, reducing their return on investment. Web2.5 Loyalty offers solutions to these problems. Cross-marketing between businesses enables vouchers to be used globally, while blockchain-based systems provide secure and transparent redemption tracking and fraud prevention. Web2.5 Loyalty also offers enhanced branding opportunities for businesses to create customized NFT vouchers/gifts that represent their brand and values, increasing brand recognition and loyalty. Additionally, our application can reduce costs by eliminating intermediaries and marketing fees, providing valuable customer data and streamlined processes. For customers, Web2.5 Loyalty programs allow for $Points to be earned and redeemed for vouchers every time we purchase at restaurant, shop, providing flexibility and cost savings. NFT or $Points can be trade on exchanges would make vouchers easily transferable and increase their perceived value, potentially increasing adoption. Furthermore, $Points can facilitate charitable donations and encourage businesses to participate in philanthropic activities, improving their social reputation and contributing to a more socially responsible business model.

How it's made

Challenges we ran into During the project, we faced a number of challenges, including limited time and a small team of only two members. One of the biggest hurdles was our lack of familiarity with the programming language we were using. However, we overcame this obstacle by focusing on the most critical aspects of the project and leveraging online resources, such as tutorials and forums, to quickly learn the new language. We also prioritized effective communication and teamwork to ensure that we were making the most of our limited time and resources. Although we were not initially aware of Niftory, we overcame this hurdle by creating our own Walletless Onboarding as a Service and integrating it with more databases to customize it to our needs. We successfully deployed it in AWS and plan to open-source it for the community. Github is on the Link! At first, we developed the mobile UI/UX using Flutter due to its smooth performance. We successfully integrated Google Authenticator for login and created a custodial wallet using our service. However, we later encountered difficulties with Flutter's UI/UX, prompting us to switch to React Native, a language we are more familiar with, resulting in a faster interface. Despite the change, we will still open source the Login Code we developed on Flutter for other developers to use. Adapting to Flow's SmartContract Cadence posed challenges for us. Notably, the difference lies in how the resource is stored in the user account and how to utilize the optional feature. Throughout our journey, we encountered multiple bugs but managed to resolve them gradually with the help of the available documentation.