Expense splitter


92
views
0
22 months ago by
1. Upload examples of what you've used for your project (and what worked/didn't work)
2. Comment on the patterns that are posted below (and why you think it works, doesn't work)

2 Answers


0
22 months ago by

Design pattern for Expense Splitter seen in Design Clinic 24/11/16:

WESTPAC MOBILE APP: 

State 1

 State 2: Add an expense

 State 3: Expense details

 State 4:

Dashboard:

Send a SMS:

Expense details 

Do we typically put the add buttons at the top of a list? 

written 22 months ago by Stephen Cox 

It depends on the user flow and type of list. Some considerations are:

1) a button at the top of the list is useful if the list is likely to get quite long. I think that what might not work with the current design is that it interrupts the flow because the purple heading says ‘I paid $300 for..’ and then it has the 'Add expense' button - so it doesn’t read well. What might help is to visually separate the button from the flow of content.

2) if the main task for the majority of users is to scan the list first, before creating a new item, it might make sense to have a button at the bottom of the list.

Essentially you’d want a solution that supports the user workflow/productivity. 

written 22 months ago by Amritah Pathak 
0
22 months ago by

Design pattern for Expense Splitter seen in Design Clinic 24/11/16:

STG MOBILE APP

State 1:

State 2:

State 3:

 

State 4:

State 5:

 

State 6:

 

Please login to add an answer/comment or follow this question.

Similar posts:
Search »
  • Mobile Wallet (AKA Tap n' Pay)
    1. Upload examples of what you've used for your project (and what worked/didn't work) 2. Comment ...
  • Search pattern
    1. Upload examples of what you've used for your project (and what worked/didn't work) 2. Comment ...
  • Off-canvas menu (AKA navigation drawer, hamburger, kebab, shelf menu)
    1. Upload examples of what you've used for your project (and what worked/didn't work) 2. Comment ...
  • Date input
    1. Upload examples of what you've used for your project (and what worked/didn't work) 2. Comment ...
  • Next Best Action (NBAs)
    1. Upload examples of what you've used for your project (and what worked/didn't work) 2. Comment ...
  • Validation - errors
    1. Upload examples of what you've used for your project (and what worked/didn't work) 2. Comment ...
  • Electronic verification
    1. Upload examples of what you've used for your project (and what worked/didn't work) 2. Comment ...
  • Help text
    Link to audit and desk research: https://digital.westpacgroup.com.au/confluence/display/CPL/Help+...
  • Progress stepper
    Link to the audit of existing stepper patterns: https://digital.westpacgroup.com.au/confluence/di...
  • Validation - success
    Link to audit and desk research: https://digital.westpacgroup.com.au/confluence/display/CPL/Valid...