Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Every example I find of anyone implementing plugins in android seems to use “aexp.intent.action.” as the prefix for their invented intent string.
Is that string special somehow, or is everyone simply copying the My Life with Android blog entry and doing plugins the same way?
I’m just curious here :-).
Um, OK.
No.
No.
Every example that you looked at apparently is “simply copying the My Life with Android blog entry and doing plugins the same way”. And, the authors of those other examples presumably are not using that action string in production — you want your plugins to use unique action strings, so they can be identified as plugins for your host app (as opposed to somebody else’s app).
Production-grade plugins do not necessarily use anything from that blog post, let alone the action string. Not that there’s anything wrong with that blog post, but it is far from the One and Only Way to Implement Plugins in Android.