1. The droid in the URL bar once the page has loaded.
2. The "Open in an app" alternative in a link's long-press menu, which often tells you which app when the destination is clear.
1. The droid in the URL bar once the page has loaded.
2. The "Open in an app" alternative in a link's long-press menu, which often tells you which app when the destination is clear.
Sure Google solution is crap, right now following a link to a Play Store app generates this [1], you really need to be a Firefox Power User in order to tap the droid in the URL bar (on this point Firefox should prompt a tip, at least the first time).
[0] http://developer.android.com/guide/components/intents-filter...
Honestly, the intent system really sucks for the use case that you mostly want to set a default app but occasionally want to do something different. Basically your choice is "be annoyed all the time" or "never have an option again until you install a new app or go in and delete all the default app's intent preferences".
Long-press/right-click for rarely used obscure options is pretty standard.
I definitely would not hold up Google's intent design UI in Android as some sort UI panacea.
Yeah, I completely agree with this. Both Google and the hardware vendors have tried many different ways to both select and change the default. They are all terrible, just in different ways.
I had a Samsung phone (T-989) that would open a popup after you selected a default app informing you of how to change the default later. It would do this every single time, so picking a default always took at least three taps. It was by far the worst implementation that I have seen.
The AOSP behavior in Kit Kat is still the best so far, IMO, but it still isn't friendly at all to non-technical users.
It's a hard problem. If it wasn't someone would have solved it already.