Tipping Calculator App
Timeframe
1 month
Role
Junior UX/UI Designer for Travelingape, a startup company.
Tools
Figma, Adobe Illustrator, Invision, Zoom, & Zeplin
Overview
Western culture values tipping. Tipping and recordkeeping require multiple apps. This tipping calculator records tips and calculates split tips, among other features.
Problem
They’re many alternatives for a user to calculate a tip using their phone. The obvious one is using the native calculator app. This app needs to find a way to convince users to use its experience.
Solution
What if a user wants to do more than just calculate a tip? This tipping app is an experience that surpasses a standard calculator app.
Make the app multifunctional and lifestyle-focused. Users can log previous tips, calculate a tip, split it, and send a tip overview.
1/ DEFINING
1.1/ Feature
prioritizing
CEO, developer, and UX/UI team decided to launch the MVP before presenting the app to potential stakeholders. Future updates will improve user experience.
Objective
-
Establish the MVP features.
-
Determine future features.
MVP:
-Changing precise dollar amount
-Changing precise percentage amount
-Changing the preset percentage amount
-Split bill option
-Copy of report
To include in the future:
-Currency converter
-Tipping log
-Rating restaurant experience
-Personalize profile
What I learned
-
Add-on features can enhance any user experience, but first, the app's fundamentals must be established.
-
Future plans are beneficial, but they do not have to be concrete.
2/ RESEARCH
2.1/
Survey/ Interview
Objective
-
Obtain a strong foundation for our user base.
-
Begin an anchor point of user comprehension.
-
Collect data for features to add on in the future.
-What is your name?
-What is your age?
-Are you single or married?
-How many people live in your household?
-How many times a week do you go out to eat?
-Do you tip with cash or a card?
-Do you keep track of your finances?
-would you like to keep better track of your finances?
-Have you not tipped before?
-How often do you travel?
-How often do you convert your currency?
-Do you read reviews first before you go into restaurants?
-How often do you tip?
-Do you keep track of how much you tip?
If yes: Do you remember the last amount you tipped?
What I learned
-
14/20 people want better financial records. Half of the respondents keep financial records. 2/20 people remember past tips.
-
Tip logging, a copy of your tip report, and a currency converter will draw in users.
-
Identified two types of app users. One keeps track of finances, and the other travels and converts currency and tips.
2.2/ Competitor analysis
Apple's app store has over 10 tip calculators. They're similar. 3 competitors were analyzed.
Objective
-
Analyzing three major competitors to discover how we can differentiate.
-
Find the industry standard.
What I learned
-
Like our competitors, we want a simple MVP.
-
Currency converter, tip logs, and establishment ratings will be added. In doing so will add something new to the app store.
3/ ITERATION
3.1/ Drawing board
3.2/ Wireframe & site map
3.3/ Lo-fi iteration usability test
3.4/ Back to the drawing board
The team tested this low fidelity to see what was missing and how to improve it.
I noticed that the user flow could be improved during the first iteration. We rearranged some components.
3.5/ Hi-fi iteration usability test
3.6/ Prototype, test, & repeat
The default percentage button makes editing percentages convenient. For hierarchy, I filled the buttons with solid blue.
4/ PROTOTYPE
4.1/ Style guide
4.2/ MVP
Splash page
Landing page
Overview page
Setting page
4.3/ FUTURE
Log-in page
Sign-up page
Currency conversion page
REFLECTION
What I learned so far
ORGANIZATION
-The process of creating and designing can get messy. It’s best to keep files organized. Organizing the file also makes it easier to pass along the project to the developer. It eliminates frustration, and it creates a clear vision for the developer.
COMMUNICATION IS KEY WHILE WORKING WITH A TEAM
-One of the biggest takeaways from this project was the flow of working with a developer. Strong communication between us was key. We try to understand each other and make compromises.
-There were components I wanted for the design. Due to the time restraint, it wasn't possible. I have a better understanding of the workflow between designer and developer. This is all thanks to my wonderful developer, Jackson!
