Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Activities Vs. Fragments

Bryan Herbst
December 11, 2014

Activities Vs. Fragments

An exploration of when to use Activities and when to use Fragments

Bryan Herbst

December 11, 2014

More Decks by Bryan Herbst

Other Decks in Programming


  1. Activity “An activity is a single, focused thing that the

    user can do.” - Android API documentation
  2. Fragment “A Fragment represents a behavior or a portion of

    user interface in an Activity.” “[…] You can think of a fragment as a modular section of an activity.” -Android API documentation
  3. IO

  4. Activity- What it is  Entry point to the application

     Set of Fragments with related purpose  Easy to manage navigation
  5. Fragment- What it is  A specific piece of functionality

     Reusable  Relatively lightweight
  6. Fragment- What it isn’t  The only option for displaying

    content in an application  Easy to manage navigation
  7. Where to start?  Create a navigation map of app

     Focus on hierarchy  Clearly identify sibling screens (e.g. top level nav items) and descendant screens  Determine entry points to the application
  8. Choose your weapon  Is this screen a potential entry

    point?  Yes: Activity  No: Maybe Fragment  Is this screen a hierarchical child of another screen (or: should it provide up navigation)?  Yes: Probably Activity  No: Maybe Fragment  Will this UI component be used elsewhere?  Yes: Fragment
  9. Case study: Cartwheel  Deep linking  All links route

    through MainActivity  Should have let the framework do the work  Scoreboard  Re-used throughout the app  Event bus for updating
  10. The Navigation Drawer Navigation hub vs. replacement for tabs =>

    Activity vs Fragment “Use navigation drawers if:  You don't want to give up the vertical screen real estate for a dedicated tab bar. “ -- Android documentation- App Structure