You’re nobody in this town unless you’re building an application.
App development seems to have become the de facto next step in the evolution of a web designer. Shaun Inman led the way with the phenomenal Mint, but since then we’ve seen an explosion in freelancers moving into the application development arena. Garrett Dimon’s bug-tracking app, Sifter, has been accompanied by beautifully detailed posts on interface design; Clearleft took a slightly different path and built Silverback as an OS X app; and the Carsonified camp built Amigo, and then failed to sell Dropsend, all the while chronicling their progress on the Bare Naked App blog. Drew and Rachel at edgeofmyseat are setting up their own project even as I type.
Time to throw my own hat in the ring.
Add It Up
I’m a strong believer in 37signals‘ notion of “scratching your own itch”. My itch, in this case, is financial management.
Our finances, like many other families, are spread over several different accounts. I have a business account and a couple of credit cards; we have joint current and savings accounts; and the children have their own savings accounts that we never dip into when we have a tight month. (Ahem.) Gaining an overview of our entire financial position is fairly difficult, then - if I want to compare how much we’re spending on food over the last few months, it’s virtually impossible to do manually.
So of course there are programs to do that sort of thing for me. Microsoft Money and Quicken are probably the most well-known, but there are also others, and there are a few web applications as well, Mint and Wesabe being the biggest (that I’m aware of). I’ve also tried Money, Cha-Ching, and a few other Mac-only applications - and, so far, nothing has met my specific requirements.
Data capture
The most critical part of any finance application (IMHO) is the data capture stage. Most apps offer two ways to do this: Either by exporting data from your online bank in the correct format (MS Money or Quicken both have their own proprietary formats), or by entering each transaction by hand. In either case, your transactions then have to be categorised by you.
My problem is that my bank doesn’t offer downloadable data, so I have no choice but to enter everything manually. One day it occurred to me that it would almost certainly be possible to automate this process by copying+pasting the data from the browser and running a simple PHP script on it. So that - with a plethora of Ajax-powered bells-and-whistles - is what I’ll be building. A way to copy+paste your online statement, categorise any new payees, and generate reports from your saved data.
Personal development
The chances of wresting market share away from the existing personal finance applications is slim to non-existent, so of course there has to be another reason for doing this. In my case, I’ve suddenly found myself at somewhat of a loose end recently; I tried spending the weekend sprawled in front of the TV or playing games, but apparently I need something more stimulating to occupy my time. I also wanted an opportunity to flex my coding muscles, after spending most of my freelance time writing nothing but HTML and CSS. Add It Up will be built on top of my favourite PHP framework, CodeIgniter, and this development blog will in all likelihood be more about coding than interface design. (Not that I could even do justice to the topic - I’m no Garrett.)
So, there you have it. I’ll be posting thoughts, questions, and code examples here as I work on the application - I hope you’ll stick around to see what happens.


July 7th, 2008 at 3:00 pm
Wee! First comment.
It’s good to see that Code Igniter is getting so much airplay.
Best of luck on the project. I’ll be seeing where it goes.
And if you need any help, I’m here. 
July 9th, 2008 at 10:27 pm
Hey,
(I’m the CEO of Wesabe.) You’re welcome to use our API to provide automatic bank sync for all the banks we support. Not sure if you want to, but it’s free, and believe me it’s way easier than implementing it yourself. We have API calls for OFX, QIF, Excel, CSV, and others, and also a custom XML format that contains a bunch of data.
This would also let you pull out community edits from our database — rather than seeing the banks’ mangled version, you’d see something edited by a person.
Let me know if you want help with this.
Marc Hedlund, marc@wesabe.com
July 10th, 2008 at 10:32 am
Thanks, Marc, that sounds great - I’m sure I’ll be touch when I reach that stage of development.