SplitSmart - AI Receipt Scanner

Project Overview

Managing group payments, like splitting grocery or restaurant bills, can be confusing and time-consuming. One person usually pays the full amount, leaving the challenge of dividing costs fairly. This often leads to mistakes, delays, and awkward follow-ups, making the process more complicated than it should be.

PROBLEM STATEMENT

Individuals who make purchases for others need a tool to track their spending.

SOLUTION

Design an app to scan receipts and track spending, set to launch by 2025.

ROLES

Product Designer

RESPONSIBILITIES

Wireframes, information architecture, user flows, design communication, brand

FREELANCE DURATION

September 2024 - Present

Process

1. Design System

2. Information Architecture

3. User Flow

4. Wireframe

5. Team Feedback

6. Iterate Design

How it started…

REQUIREMENTS

1. Branding for “SplitSmart”

  • Color

  • Logo

  • Typography

2. Design main user flow

3. Design while expanding this vision

Design System

Information Architecture

User Flow

Iterative Design

Settle Transaction

Revising “Debt Relationship”

Before

  • Users want to track how much everyone owes, but “Debt Relationship” only identifies a single relationship for the user, not accounting for all involved.

Iteration 1.1

  • Shifts the concept from “owe” to “spent,” emphasizing the overall transaction rather than individual transactions.

  • “Who Paid?” communicates everyone’s relationship to a single person.

Entering Transaction Details

Iteration 1.0

  • Each member has their list of items purchased, making it challenging for users to co-pay.

  • Users are limited to a single tip and tax input.

Iteration 1.1

  • Now a single list for all items purchased.

  • Users add items, tips, and taxes invariably without limit.

Iteration 1.2

  • Tip and tax inputs are added distinctly and are divided equally for ease of development for now.

Assign Member Spending

Iteration 1.1

  • The default screen state always selects the first member.

  • The visual layout was not appealing to stakeholders.

Iteration 1.2

  • Default screen state disables “Select Member” button, requiring users to make an intentional selection.

  • Updated layout based on feedback.

Dev Handoff - User Flows

Next Steps

2. Iterate Design

3. Launch Product

1. Usability Testing