Is including a application package prefix while defining a custom action string is convention or mandatory?
Is including a application package prefix while defining a custom action string is convention
Share
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.
Is including a application package prefix while defining a custom action string is convention or mandatory?
The documentation for the
<action>element in the Manifest says:So it is only a convention, in that there’s no technical requirement to put the package name, but it’s convention that will help you. For example, if you created an action with the name
REFRESHit’s quite possible another app might create an action with exactly the same name which could cause you problems. If you prepend your package to the action name then you can sure your names are unique and only your app will intercept them.There’s an attempt to registry of common actions at openintents.org but it doesn’t have that many entries.