Create New Features or Uncover The Existing?
We like a lot of what 37 Signals have to say. If you’re in the software or design business give their writings a good look.
One of their recurring themes is keeping things simple and knowing when to say no to features. We were discussing this recently when an interesting topic came up: what about the existing features?
We’ve done some analysis and found that the majority of our users aren’t aware of the majority of features Xpenser offers. Which is odd in some ways, given the relatively few features we’ve exposed.
There’s a very good argument to be made for putting time and effort into making the existing features more obvious, more accessible, and more usable, instead of introducing new features. We’ve attempted to keep the features in the product flexible so you can use them in a variety of ways; in fact we’re continually surprised by the innovative ways you use and combine features to solve problems. This is the mark of a good feature. We’d create more value for more people by making these building blocks better known.
We’re not going to stop introducing new features; we have a fairly clear set of things we want to implement to make Xpenser more useful. However, we will be going back and looking at how to make the existing features and capabilities more discoverable and easier to use. And as always, we’d love to hear your take on it. Drop us a comment below or let us know at feedback@xpenser.com.

I’ve just come across Xpenser yesterday when looking for a tool to track my expenses and it’s great, lightweight application. I think nowadays no web application can aim to do everything, simplicity and ease of use are more important.
Therefore I encourage you to work a bit on the documentation, and just implement a simple little feature for me (and the rest of the non-US world): setting custom base currency. I really don’t care how many equivalent US Dollars I spend here in Hungary…
Zsolt, setting of base currency is on its way. Keep an eye on the blog and we’ll email you to let you know once it’s available.
Documenting (a lost art amongst Web2.0-isms) current features would work