I ran into this design issue when developing an app and it seemed to make more sense, at least usability-wise, to just use one Activity class with multiple tabs versus dividing the app into many smaller activities.
Here are some things to consider when deciding the best approach for your app
- Android can get rid of unused activities in order to reclaim RAM.
- It’s easier to introduce memory leaks by trying to have a single activity stick around for a long period of time rather than having lighter activities that come and go
- State management for dealing with eviction from memory (e.g. orientation change, RAM reclamation) can become more challenging or more inefficient
- You may find many features of Android, like notification and app widgets, become progressively more challenging to use when you cannot simple launch an appropriate activity
- Java does not support multiple hinheritance, so if you have features that requrie separate Android base classes (e.g. preferences and maps) it’s imposible to implement them all in one activity???
Rererences:
http://groups.google.com/group/android-developers/browse_thread/thread/079ead52980f7b66?pli=1