1. Single Activity architecture
Home is activity, inside page for view
- The bottom bar of the head is common, just changing the text and pattern.
- Bottom navigation bar is RadioButton
- Middle can slide to toggle
- Jump quickly, but the home page is not smooth.
The benefits of this architecture are clear thinking and low system operating overhead. The downside is poor control, code clutter, and poor lifecycle management.
2. Multiple activity-use baseactivity to provide commonality
3, multiple activity-use tabactivity
Sub Mainactivity (tabactivity)->activity (baseactivty)
- Code and ideas are clear
- Baseactivity has the same back and head bottom bar
3.1 Sun Mainactivity (tabactivity)--Child Activity (Activitygroup)->activity (baseactivty)
PS: For jumps that need to implement multiple activity within a tabhost
3.2 RadioButton with tabactivity jump (code very clear)
4, multiple Activity-activitygroup (official has been marked as not recommended)
The bottom bar is implemented with the GridView, and the bottom is used RadioButton
Android Project-several common Android application architectures