Split is a conceptual application that could be installed on iOS devices. It was intended to seamlessly integrate and improve the way users split their bills when going to restaurants. Based on the research, Interviews, A/B testing, goals, usability, and solutions I was able to enhance and reimagine the modern-day split bills for easier usability among friends and family.
protoProto 2
Duration: 3 weeks, July 2021
My role: UX/UI Designer
Tools: Adobe XD
Overview Process
Process View
What is the problem?
Users rely on system 2 (requires mental complex computations) when paying bill separately or together.
How can SPLITBILL create system 1 Thinking?
The product will mitigate the cognitive load of making manual calculations and automate payments with little or not effort at all.
Competitive Analysis Research
In this research, I conducted a competitive analysis, compared different interaction models, and studied best-split bill applications. This chart demonstrates the features and solutions that each application has. This helped me to understand how various applications for splitting bills are perceived usable fro their efficiency, convenience, reliability, and affordability.
Quantitative & Qualitative Data
In this early part of the process, I was able to collect quantitative and qualitative data from 3 participants. Once the data was collected, the tasks, actions, and observations were divided to analyze and compare the struggles the user encountered while completing the given tasks. At this point, the main pain points have to be extracted from the experience map to come up with a set of goals and metrics.

Pain Points, Goals, & Metrics
The pain points extracted from the experience map were mainly focused on simplifying the experience for the user. In this case, finding the solution to split the bill among friends, and family. Ultimately, this application was meant to not disturb the user's experience. Once the pain points were targeted, the main goal was to upload receipt, bill quick, being able to split their bill among friends tip, send or request money without getting fees.
Scenarios & Storyboards
Two scenarios and storyboards were created based on personas, pain points, and goals. These four scenarios show the possible interactions from the user and application. Moreover, the scenarios and storyboard demonstrate the goals and solutions that the user may encounter.
Low-fidelity Wireframe
User testing # 1:
2 Participants & observations

After using the paper-fidelity wireframes, I have decided to make a few adjustments on the "splitting bill" feature by simplifying its usability and interface for an easier interactivity. ​​​​​​​
This was my initial round and tested a variety of interface styles using different concepts to make the task easier and understanding what types of interfaces user’s found appropriate. This was followed up by short feedback to understand not only their pain points but what they wanted to see within the application
Low Fidelity Prototypes  V2
A/B Testing
In this part of the process I was able to get valuable feedback from users by using the poll platform installed in instagram. In this case, I utilized this medium to conduct A/B Testing for icons, menu bar, and lay outs.
User testing # 2:
2 Participants & observations

After using the low-fidelity wireframes, I have decided to make more adjustments on the "splitting bill" feature and adding more interactivity to the feed/comment section.
My goal in this part of the process was to use the A/B testing for the new interfaces and icons for development. The user was able to select the icons that were closely associated with the tasks. Finally, by comparing the consistency of the user's intuition when given tasks. This helped me to develop a more efficient product and surrounding my focus in the areas the user pointed out.
High Fidelity Prototypes:
With user research and iterations, I progressed from low-fidelity to high-fidelity prototyping. I aimed to take our user-driven concept to a professional product with the three testing methods found below.
User testing # 3:
2 Participants, A/B testing, More Feedback

After the second round of usability, the new high-fidelity wireframes included new improvements but the splitting unfamiliar patterns causes some decision fatigue.
After receiving more feedback from the users, I was able to continue to make the new adjustments and attempt to make a more cohesive product. I found the A/B testing has been useful in my design process by constantly receiving feedback which helped a lot to stay focus on the pain points.
Final Design
Interactive Prototypes
Split was built to meet user needs and address current pain points with splitting the bill. Using an iterative design process, I was able to narrow our design down to the critical features. I used After Effects, and Adobe XD to demonstrate some of the functionality.
Scanning receipt
After the usability tests and iterations made during the process. The scanning feature was the easiest solution to start the procedure of splitting the bill.
Splitting bill
One of the most helpful features when it comes to selecting the items with a click.
Adding Tip
The solution I found to maximize the users experience was the implementation of the tip in the same page as the splitting is happening.
After selecting the items and tip, the user is taken to the review section where he or she will make adjustments if necessary.
An additional feature was added based on the usability tests and the what the user wanted to see. This will allow to communicate with other friends and see the rates given to the place.
The contacts section was the easiest to create based on the user's feedback and usability tests.
An additional motion graphic was added to confirm that the money was sent or received.
What is the application solving?

This app is making splitting bills easier and convenient when going out to places.
What does this app include?
I decided to include the following features in order to maximize the usability of the application. These were the most demanded features during the research and interviewing process. Receipt Picture Feature,Profile,History, Pictures/Likes/Comments and Interactivity

What does this app not include?
I decided to not include the following features in order to maximize the usability of the application. These were the least demanded features during the research and interviewing process. Fees, Video Stories.
Managing feedback from users between changes in the paper prototypes. There were a lot of challenges when it came to making quick adjustments due to the time limit as well.

However, I was able to complete this project while working by minimizing the amount of time spent in areas that did not need much improvement.
Communicating high-fidelity concepts during the paper phase
At the beginning of the stage, it was challenging to introduce the sketch ideas to the user and explain it in detail so there is no confusion.

However, on some occasions, I have overthought the words that came out from my mouth. As a designer, I knew I had a more dynamic way of thinking but reassuring the concept with the users has made my product more valuable.
Testing high-fidelity prototypes and making design decisions
Collecting the quantitative and qualitative date from the users allowed me to get a clear idea of the main pain points. However, with the limited amount of testers, it was challenging to get more feedback.

Therefore, I had to spend more time with the user to come up with more cohesive solutions. As the product designer, I had to make design decisions based on the user's expectations, not mine.
In my final round of user testing, the 3 participants accomplished tasks with ease and found the experience intuitive and visually appealing. I hope you enjoy Split as much as myself and our users. A lot of coffee and thinking was involved!

Thank you, for your time! (: