0% found this document useful (0 votes)
132 views2 pages

Simple Splitwise / Tricount Clone: Description

This document outlines requirements for an app to help friends track expenses from gatherings. The app should allow users to create groups, add expenses with details of the date, amount, participants and payer. It should show individual and overall balances owed between members. The app needs to persist data and have a simple UI, with optional use of libraries and unit tests. Submissions are due in 7 days and should include a git repository with clear commits.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
132 views2 pages

Simple Splitwise / Tricount Clone: Description

This document outlines requirements for an app to help friends track expenses from gatherings. The app should allow users to create groups, add expenses with details of the date, amount, participants and payer. It should show individual and overall balances owed between members. The app needs to persist data and have a simple UI, with optional use of libraries and unit tests. Submissions are due in 7 days and should include a git repository with clear commits.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Simple Splitwise / Tricount clone

Description
Build an app to help you and your friends keep track of expenses after gatherings and parties

Features
With this app you should be able to
• Create a group with participants and optional brief description.
o E.g: Office pals - Alice, Bob, Matt, Dave
• Add expense for each gathering, details should include date, description, total amount,
participants and person who paid for it. Expense doesn't have to be equally split - like
sometime someone may order an extra for themselves, so details should include that.
o E.g:
§ March 4th - Homecoming party - $200 - Alice, Bob, Matt, Dave - Alice
paid.
§ March 6th - Coffee and croissant for Alice - $19 - Alice + 5, Bob - Bob
paid.
• Review expenses for each person: you can choose to be any person and see their
"expense diary".
o E.g: Alice - March 4th - Homecoming party - $150; March 6th - Coffee - -$7
• Review overall balance for your group: you can see how much who owe whom.
o Eg: Matt owes Alice $50, Dave owes Alice $50, Bob owes $31

Other requirements for the app


• Data should be persisted.
• Simple and clear UI - app doesn't have to look fancy but should be user friendly and easy
to use.
• There's no limit to the use of 3rd party libraries, but make sure you can explain why you
choose to use them.
• Extra point if you have your logic unit-tested.
• Extra point if you use RxSwift

Expectations
• Level 1: app works perfectly
• Level 2: app has unit tests and the tests make sense
• Level 3: app written with perfect RxSwift
Submission
• Deadline: 7 days
• Must attach a git repo. Commits must be clear and trackable. Prefer github / bitbucket.

You might also like