Thanks everyone, I'm glad people find it useful.
I've been using the full address API to resolve Firstbits addresses, but the request time grows linearly to the amount of transactions associated with that address. Can you add a new API method or just a small switch to only resolve the address? I get faster request times, and you reduce unnecessary server load. Win/win!
You can use
/q/getfirstbits/$address
find the firstbits from an address
or
/q/resolvefirstbits/$firstbits
to find the address from firstbits
Those calls are used in the javascript client, not sure why I haven't document them.
New Version of the android app (2.

* Automatic fee calculation
* Separation between active and archived address
* Wallets should update live (i.e. any changes you make in the web interface will immediately show on the android app and visa versa - it's a bit flaky though)
* Further improvements to wallet synchronization
