I’m not sure what’s confusing you. I’ll try and explain the situation as clearly as possible.
The end goal is to authorize my app so I can send out a tweet using my app with one click. (In reality, it’s a lot more complex than that. But as far as Twitter is concerned it boils down a tweet)
Let’s say the app I’m developing is called…"ExampleApp"
The flow to authorize ExampleApp normally looks like this:
ExampleApp -> Authorization Page -> Redirect BACK to ExampleApp (iOS) via Custom URL Scheme
The redirect back to the ExampleApp is easily accomplished by setting up a custom URL scheme, such as “exampleApp://”, within my app’s settings. Most services allow a custom URL Scheme to be used as the callback URL when registering an application for API access. This enables the developer to get a callback directly to the app.
Twitter, however, will only accept an HTTP/HTTPS scheme for the callback URL I would have to have my own website that receives the callback, and redirects to my app using my custom URI scheme. Visually, the flow for Twitter looks like this:
ExampleApp -> Authorization Page -> Callback is sent to “https://www.example.com/callback/…” -> “https://www.example.com/callback/…” redirects to app using custom URL scheme (exampleApp://)
Does this make more sense?