01

BILL/SPLIT

Don't argue over the bill, split it

Making your group night out and shopping trip a little easier. Bill/Split allows you to itemize receipts and select which items are yours. Share the bill with your friends and pay only for what you bought.

Problem Statement

Going out to dinner with friends, or shopping with your roommates always ends in the same dreaded way. You’ve eventually got to figure out how to pay the bill. Everyone has to take out their wallets and start pouring over the tiny little font on the receipt, trying to figure out how much each person owes each other. It's way too much work. This takes forever and don't forget the awkwardness of the scenario

Our Solution

Bill/Split is a way to simplify the bill-paying process. First, take the receipt and scan it using in-app camera on your mobile phone. Once the receipt is scanned, the system will read the bill and extract all necessary data including each item, place, date, time, and total amount, separating each item into drag-able objects. Users have the freedom to choose as many people as they like in the transaction. They can split the bill equally with each person at a family-style eatery, or depending on their purchase, drag and drop items they want to pay for onto their own account, such as at the grocery store. The app will send an individualized total to each user in the transaction, allowing them to quickly send money via the cash app of their choice. The app will save all previous receipts and show how they were split, streamlining the bookkeeping process.

Personas

Affinity Mapping

Our main user base is students, so to understand their needs and problems we interviewed university teenagers and young students. We conducted contextual inquiry focusing mainly on the frustration faced by people while splitting bills and sorting their finances.

To create the affinity diagram, we used the Holtzblatt method.

This diagram is a hierarchical representation of the issues for your user population built from interpretation session affinity notes. In the diagram:

  • Yellow notes indicate affinity notes

  • Blue notes indicate the theme of multiple affinity notes

  • Pink notes indicate common theme obtained from blue notes

  • Green notes summaries the theme of affinity notes. It tells the main user story.

Low-fidelity Prototype

High-fidelity Prototype