First of all, I think Twitter should make it more clear that this implementation is focused on providing Twitter access for non-client apps. Think of this implementation as a 'post on Twitter' feature that doesn't require any API knowledge or other very complicated stuff. That, and you have the ability to get some information about the user. I think it would be a very bad thing if this gave the app DM level access as that kind of access is either abused or for client apps and this framework isn't for either of those.
What I noticed while studying the framework (and I'll avoid violating the Apple NDA here) is that the requests are signed using a fixed pair of credentials and always say 'from iOS'. It would be very nice to be able to make that say something like 'from <appname> on iOS' or something. I think that a LOT of devs are going to ask for that. I have some other ideas but they are improvements over the current framework and if I posted them on a public list I'd have to shoot you ;-) Tom On Jun 29, 2011, at 1:44 AM, Ryan Sarver <[email protected]> wrote: > Hey all, > > With iOS 5 and the Twitter integration coming in a few months, we have been > getting a ton of inbound interest and questions around how to effectively > leverage the Twitter integration. We wanted to get your feedback on how we > can best support you and your users in developing meaningful experiences. I > also hope you have had a chance to dig into the documentation and watch the > WWDC session video. > > We've heard that it would be helpful for us to provide some standard graphics > for use with your upcoming iOS integrations. We wanted to understand what > types of buttons and styles would be most helpful. We think the most common > use case is going to be "Sign in with Twitter" (SSO) but let us know what > formats would be helpful. > > The two use cases that we're hearing the most interest around are: > > 1. Instant personalization - frictionless Single Sign-on (SSO) and social > graph will allow apps to provide a personalized experience to their users > with one click. What things can we provide to make this more effective for > you. > 2. Distribution - using the build-in Tweet Sheet functionality to post great > content from your app out to the Twitter stream where it will drive > engagement and clicks back to your application. > > Let us know if there are any other resources that would help make your > Twitter iOS integrations easier on you or help you provide more value to your > users on iOS. > > We'd love to see your apps, give feedback and help make developing on Twitter > and iOS 5 a great experience so let us know how we can help. > > Ryan > > -- > Ryan Sarver > @rsarver > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
