I'm working on implementing mobile data plans for social networking
sites including Twitter. Requirement is to identify Twitter traffic
from mobile devices and charge distinctively from other data packets.
Since there are different ways that Twitter can be accessed from a
mobile device (browser, client app, embedded links etc), i would like
to know the possible patterns that i should identify. Clients using
standard Twitter APIs would be RESTful and generating HTTP traffic
eventually. Question is does the prepackaged client apps (such as HTC
Sense, SE Timescape, Moto Blur, Samsung Social Hub etc ) also use
public Twitter APIs ? Or is it a different arrangement altogether.


Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 

Reply via email to