Ok I am designing an app which has a very simple layout of 62 Content Screens, accessed via 27 Menu Screens. In total this is 89 activities.
At the moment I have each Content Screen to be an Activity that just calls an XML layout (some text, buttons and image) and adds some onClick functionality.
Each Menu Screen is a ListActivity and pressing each item in the list opens that item's Activity (be it another Menu Screen or a Content Screen).
At the moment I am testing it with 3 Menu Screens and a Content Screen. It is fine scrolling through them all, however I am concerned that when I finish the app it will have too many activities and make the app slow and slugish. In an average use of the app I imagine the user would use no more than 10 activities but I am not sure if Android would be anticipating creating the other unused Activities or what.
So another way to implement this would be to have just a few Activities (maybe 1 for a MainMenu, 1 for a subMenu and 1 for a ContentScreen) that just work out which layout to display. However I feel this would mean that each Activity has a hell of a lot more work to do and also I lose the functionality of pressing the Back button taking the user back up through the menu hierarchy (and coding a replacement Back button onto each Screen would involve a massive Case for the onClick involving every single possible layout, all 89 of them!).
What would be the best way to go about this app?
Any help is very much appreciated