Android Projects-several common application architectures

Android Two Ways to tab page: Tabactivity and Activitygroup

Http://www.apkbus.com/blog-70574-40942.html

 

1, single activity architecture (recommended)

homepage is activity, inside page is view

• The bottom bar of the head is common, just change the text and patterns.

• Bottom navigation bar is RadioButton

• Middle can slide toggle.

• jump fast, but the homepage 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-using tabactivity

Mainactivity (tabactivity), sub-activity (baseactivty)

• Code and ideas are clear

• Baseactivity has the same back and head bottom bar

3.1 mainactivity (tabactivity), son activity (Activitygroup), grandson activity (baseactivty)

ps: for jumps

that need to implement multiple activity within one tabhost

3.2 RadioButton with tabactivity jump (code very clear)

4, multiple Activity-activitygroup (officially marked as not recommended)

Bottom column with the GridView implementation, the bottom is also used RadioButton.

Forwarded on: http://www.cnblogs.com/TseChiHoi/archive/2012/09/06/2673978.html

Android Projects-several common application architectures