Mere hours ago, Apple approved version 2.5 of Splitwise for iPhone. We weren’t expecting this to get through the review queue before the holidays, but lo and behold, we’re here!
As we described in the version 2.5 web preview Ryan and Jon just posted, we’ve been trying to make Splitwise continuously more simple and delightful as we release new versions. This is just the beginning, but we’d love to get your feedback, either here, at our dedicated feedback site http://feedback.splitwise.com, or email us via firstname.lastname@example.org.
The iPhone app started in this release cycle with fewer structural issues than the website – it’s already simpler to use, faster to add bills across friendships, and easier to view everything in one place. But we really wanted to add the visual feedback of category icons to the mobile experience (see image right). We think this makes it more fun! The iPhone app also auto-categorizes expenses now, just like the web version.
As you can see in the screenshot, we also (finally) differentiated payments visually from IOUs and expenses – something we have done since version 1.0 on the web version of Splitwise.
We also made some improvements to the expense details view, which was quite an ugly screen in the previous iPhone version of Splitwise. We’re not sure if we’ll keep the “spotted” wording or not (to explain who owes who), but in general we are trying to improve the tense of the verbs so that it’s clear what has gone one with old expenses. More to come on this in version 3.0.
As always, we welcome and encourage feedback on these visual improvements!
The new ways of viewing “friends/groups” data will first be available on the web version of Splitwise, and is not in this iPhone release – it will take us until version 3.0 to harmonize this approach across iPhone and the website.
What about our poor Android users? As Splitwise’s most loyal Android fan, Jon sympathizes. Android users will have to wait a bit longer for these snazzy interface improvements. Developing for Android is more difficult and more expensive than developing for iPhone, in part because there are so many different devices to test on. Splitwise is still a small team, and we are more experienced in iPhone development.
Marshall has been hard at work releasing rapid bug-fixes to Android – the crash rate is now half the rate it was in August, after much hard work and re-writing. If you are a great Android developer yourself, and are passionate about making Splitwise’s Android app kick butt, please send us an email at email@example.com – we’re hiring!
– Jon and Marshall