Written by Derrick Luyen and Yiwen Chen
The problem: Nowadays, many people drink boba drinks and at each store, there are typically stamp cards that are given to customers as some form of loyalty program. However, stamp cards are very easy to lose and can be misplaced at times. It would be more convenient to have some other way to keep track of these stamp cards.
The solution: Keeping all the stamp cards on an app/website, where people can have easy access to it. This app essentially acts as an electronic wallet for the stamp cards that people can use across different drink places. The app can also act as a coupon keeper, where customers can receive coupon rewards as a result of being consistent with stamp cards depending on the drink places that they go to.
Users will need to sign up for an account with our application, or if they already have an account, they can sign in with their existing account. Users will need to connect their phone numbers to their account.
For users, once they sign up for their account, they will be redirected to the Stamp Card Wallet page, which will be empty at first. Users have the choice to create an empty stamp card and choose which drink place they want to retain a stamp card from. They may choose from the list of preexisting drink place stamp cards that are registered with the website. From there, the stamp cards on the website will be updated by the boba tea shop owners as the users purchase their drinks, and this will be achieved by having the user input their phone number that is linked to their Stamp Card Wallet account.
Boba tea shop owners will need to sign up with the address, name, and upload a stamp card design/detail that will be shown on the user’s end. Owners can choose how much drinks need to be purchased in order for the stamp card to be filled as different drink places have different numbers of stamps received to fill the stamp card.
Some possible mockup pages include:
Whether or not the following bullet points list all pages or not, the completed use case should show an end-to-end scenario of using the system.
After implementing the basic functionality, here are ideas for more advanced features: