This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Why do you want to do that? What is missing from the installation mechanism built into Android that makes you want to do something else? Also, why do you want to tick off your users by presenting them with an installation mechanism that they are not used to, and that is completely different from the normal Android app installation?
No no, you get me wrong.
I want to make such screens because there are few screen layouts which gives intial information to the users like how to use the app etc.
That's it. I dont want to tick off the user or dont want to play with phone's mechanism.
Why not used Shared Preferences to keep a property that indicates whether the app has been previously run, and if not present an alternate Activity that contains usage information. Or perhaps simply have the main Activity display a toast that tells the user to go to Menu | Help for instructions on using the app? If you think about it you can possibly come up with several other variations.