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.
I am making an application where I am using some base activities that I inherit things from. I tried running the application without adding these activities to the manifest file, and it works. But should I add them or leave them out? Is it only the activities visible to the user that I need to add?
There’s nothing wrong with having some activities that are not defined in the AndroidManifest file, as long as you do not attempt to start them.
So, the answer would be no, you do’t have to add the activities that are there just for the sake of some sort of abstraction.
On the other hand, why would you want some classes with the application lifecycle functionality (and other Activity stuff) in place? It seems like a bad design and I’d really advise you to review the code.