Splitwise is an app that helps you keep a record of all the money you borrow or lend to people, helping you get paid back efficiently. People who don’t use this app keep track using a Notes App. People seem to be largely comfortable with the Notes App due to the simple input method. The problem arises in the long term though. The record-keeping starts out simple but gets very clumsy soon enough. There are so many combinations in terms of the individuals sharing an expense and the share of each individual, that understanding the records or doing the calculations gets very confusing. The maths is simple, that’s why most people think they can get by a Notes App, but it gets very confusing.
People tend to avoid a dedicated app because all this work doesn’t help them make or achieve something. It is just overhead work in an unfortunate situation. Splitwise is an ‘overheads necessity’. Hence, the challenge is:
To design an app where the UI flow correlates with the immediate thought flow of the user, akin to writing a sentence in a Notes App.
To that end, the most obvious thing an app like this needs is a widget. It must display a list of pre-defined groups, individuals, or a combination of them among whom an expense was recently shared. The current version doesn’t have a widget.

Why is the key-color Dark Blue?
For an app that notes expenses, green and red universally represents positive and negative respectively. Here, green is money you will get back, and red is money you have to pay back. Hence, blue is a natural choice for a neutral colour. A darker shade is used to visually highlight it from the rainbow of colours that will be used in our representations henceforth.
Why is the complimentary-color Orange?
Orange in our visual representations of the split will be used to denote the owner. And hence it is constant to any split and to further drive this point home visually, I have made it ubiquitous through the app. The most important buttons the user will be interacting with are orange, for example, the Add Expense button.
Continue reading “Redesigning an Unproductive but a Necessary App – Splitwise”