WebIntents are Links 2.0
blog.superfeedr.com
blog.superfeedr.com
For example, I can send an intent off to send an email. Then, any email application on the device that has declared itself as able to receive that intent with an <intent-filter>, can respond to it.
The problem is that there is no way for the response to be standardized. Applications often give you back different results for the same intents, that lack the extras you expected, or don't respond at all.
The end result is when you try to use an intent to add a cool feature to your app, you run into the problem of the user potentially having an app installed that doesn't handle it correctly, but publishes itself as able to do so.
The aftermath is that the user tries to use this app, then when it doesn't work, to them it is a bug with my app. When there's really not a thing I can do about it.
Does Web Intents address this issue at all?
There is a fork of CM somewhere that has the ability to remove things from the Intent responder list and I think there's a root-enabled third-party app as well.
There's no reason the User-Agent couldn't give you the ability to "hide" an Intent receiver from the default list of applications. (In fact I expect it) What you're describing is an application failure, not a design problem, there's literally no way to enforce the correct behavior of an application the way you're expecting.
Watch the SMS app show on some phones when using Intent.createChooser and totally misinterpret the intent to the astonishment of the user.
You wouldn't see this problem if you didn't test on a LOT of phones.
It's not immediately obvious. I've been developing for Android for a while now.
Example use cases where file is at an arbitrary URL: 1. Save a file - saves file in your dropbox. 2. favorite a song - music service (i.e. soundcloud) saves to your favorites 3. get copy of code repo - forks the repo for you on a versioning system service (i.e. github) 4. register for event - adds event to your scheduling service (i.e. plancast, google calendar)
What other ideas can you think of?
<intent action="http://webintents.org/share type="image/" href="share.html" disposition="window|inline" />
<link rel="http://webintents.org/share type="image/" href="share.html" disposition="window|inline" />
So I'll state my original point- there has to be more leverage behind web intents that I'm missing? Does anyone have good links that may shed more light?
Also, it will do exactly that: help bloggers get rid of all the dummy buttons ont their sites for these services who track _their_ readers, audience and make the loading slower... while still allowing everyone to chose their platform of choice :)
The goal is that users will not know about or need to know about intents, they just get the flexibility to use the services that they prefer to use in the apps and sites that they visit.
For developers it is about not having to create or build native, or tightly coupled integrations to a select few services. The app just asks for a service and the browser knows the list that the user can use.
The "download" or install part you mention is just for now whilst we get the intent tag and other discovery mechanisms landed.
If you look at AddThis, they offer support for intents in their widget, so it is not aimed at being tech centric at all.
I would also add that we are not finished yet, there is still a lot to do such as setting defaults, and building explicit intents (let the dev define the endpoint of the action) and also getting more apps to provide or integrate with services.
Sharing in just one of the many examples of intents. You could also have one intent for editing a picture, which would open an app for editing. Or playing a video. Adding an event to the calendar etc. You can make up your own intents, it can be virtually anything.
If you used android, it works just like android intents. When an android app needs to play a video, it doesn't need to say "open app X", it just needs to say "I wanna play this video" and the OS will show the user with a list of apps which registered to be able to do that.
Web Intents does have a compatibility JS shim, it needs a couple of updates to get it working in FF again after implementing Content Security policy, but after that WI should work fine (but not native).