> A common and frustrating use-case was mobile Twitter: Someone would share a new favorite or upload on Twitter, you tap on it, and it tried to load the regular

> A common and frustrating use-case was mobile Twitter: Someone would share a new favorite or upload on Twitter, you tap on it, and it tried to load the regular site on your tiny smartphone screen. Pushing the whole desktop site over a mobile connection would be a waste of precious bandwidth, if you only want to check out a track. Alternatively we could try to redirect to our native apps, but there’s no guarantee that the user has it installed and the mobile vendors don’t offer any APIs for verifying that in advance. Somewhat off-topic, but for any devs interested: Android allows you to do that. From your native app, you can essentially hook into whenever the user tries to open a URL that looks like your site (soundcloud.com, etc), and through the Intent system the OS will offer the user the option of opening that URL through your application. From there you can parse the URL, see what they were trying to look at, and dive deep into the app to whatever screen (Activity) makes sense for that content. Here's an example from StackOverflow: http://stackoverflow.com/questions/2448213/how-to-implement-my-very-own-uri-schema-on-android/2448531#2448531 http://stackoverflow.com/questions/2448213/how-to-implement-... I'm not as familiar with iOS, so I don't know if something similar exists for that environment.