Tabs as views or Activity?
<p>I'm developing an app which requires nested tabs (tabs within tabs). Say for example one of my tabs is a message tab into which I have four tabs- inbox, compose, sent, trash. I have around 3-4 of such nested tabs in my app. I'm looking for a few suggestions whether to make these tabs separate activities or just views. I've read about this issue and I'm aware that this problem is very much specific to the need of an application. But as a beginner I'm skeptical about my approach. Initially I wasn't sure if I should have so many activities in my code as it would hamper the performance. As of now I've created the main tabs as separate activities and the nested tabs as views. For most of the inner tabs I only want a user to select from a list of options, though there are a couple of tabs which involve more user interaction. Can everything that can be achieved by an activity approach is possible via view approach? If so, then How? Any suggestions would be helpful.  </p>
