After I got the UI in place, and the timeline loaded correctly now I have to make it human-readable.
I designed the tweet display to be similar to Twitica Desktop, but I added Geolocation support. Desktop’s implementation is just a pin, while I shouldn’t do that in Mobile because it would be slow to know where that user is so I need to fire Google’s reverse geocoding server. (Too bad, while searching for the docs I found GMapsv3 docs instead and included full Google Maps system in.) To do reverse-geocoding, just call the [API](http://code.google.com/apis/maps/documentation/geocoding/#ReverseGeocoding) with lat,lon of the tweet and it just return the result. Desktop use granularity to the street level, but I think it’s too much so I decided to use district level result to display. When clicked, it would show the map just like in Desktop. This can be accomplished easily by just navigate the browser to Google Maps and Android will handle the rest. (I learned this trick while making Twitica Desktop for Android)
Also, I moved the time to under user’s avatar which I copied from [Yak for webOS](http://www.precentral.net/review-yak)
**Today’s tip (& what I’ve learned):** Pass –disable-web-security to Chrome and it will allow cross domain XHR. I use this to test Twitica Mobile.
*Twitica Mobile (PhoneGap) is open source, you can fork it at [http://github.com/whs/Twitica-Mobile](http://github.com/whs/Twitica-Mobile)*