It presents two main views: a Home view that pulls in messages from Twitter and Twinkle friends, and a Nearby view that pulls in messages from Twinkle users near me. 
The Nearby view adds a new dimension to Twitter (one that Twitterrific also tries to add, but doesn't succeed in such a clean way). It lets you find out what the folks in your neighborhood are doing. What's that cute guy down the block doing this morning? If he uses Twinkle, you can find out. The main problems Twinkle has are network-related. Twitter has had problems with scalability for years, and even invented the Fail Whale to symbolize it. Twinkle in turn is dependent upon Twitter for the vast majority of their messaging data. (To their credit, Twinkle acts as a kind of messaging buffer between Twitter and the end user, so not every Twitter failure translates into a Twinkle failure.) The location data Twinkle uses is in turn dependent upon Apple, AT&T, and Skyhook Wireless. If you're using an iPod Touch, for instance, it's unlikely you'll get accurate Location info unless you're in a fairly dense urban area and happen to be near a WiFi access point that Skyhook has already mapped. Generally if you're using an iPhone, you'll get location data that is sufficiently accurate for Twinkle.
I'm a big fan of using location-based services to help support local businesses and local communities, and I think Twinkle is a nice step in that direction.
1 comment:
Great post, protection data is where money should be spent! I agree. Not every website can afford responsive design. There are other things the money would be better spent on.
design an iphone app
Post a Comment