4 ms·
The main problem I suffer from as an Android developer with intents (in Android) is that applications inconsistently implement them. For example, I can send an
by readme 14y ago
The main problem I suffer from as an Android developer with intents (in Android) is that applications inconsistently implement them.
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?
- etherealG 14y agoit seems like some required data with an intent would make sense to resolve this. and firing the intent without that data is the same as not firing the intent at all?
- drivebyacct2 14y agoI've been using Android since the G1 came out. I've never experienced what you're describing and I fail to understand it. If news.yc started click-jacking Facebook/Twitter likes, I'd stop using it. If an app started broadcast bad Intent receivers, I'd stop using it. 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.
- bookwormAT 14y agothis problem is new to me as well, both as a user and a developer. Usually, data that is sent between events is very simple, and if an application registeres for an event that it does not handle well, then it is mostly transparent what application has to be replaced.
- readme 14y agoTry sending some emails to multiple recipients using ACTION_SENDTO and a properly crafted URI. 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.