Arch Components - Navigation

Transcript

1. NAVIGATION ARCHITECTURE COMPONENTS
2. NAVIGATION ABOUT ME ▸ Android Developer for about 5 year ▸ Works at Homesnap ▸ Just moved back from DC ▸ Work remote now
3. NAVIGATION NAVIGATION COMPONENT ▸ Simplifies navigation ▸ Introduced in I/O 18 ▸ Single activity ▸ Still in alpha
4. NAVIGATION PRINCIPLES OF NAVIGATION ▸ fixed starting destination ▸ navigation state is a stack ▸ up button never exits app ▸ up and back should be the same ▸ deep linking or navigation = same stack
5. SETUP NAVIGATION
6. NAVIGATION Check this ENABLE EDITOR
7. NAVIGATION ADD DEPENDENCIES dependencies { def nav_version = "1.0.0-alpha05" implementation "android.arch.navigation:navigation-fragment:$nav_version" implementation "android.arch.navigation:navigation-ui:$nav_version" // Add -ktx for kotlin implementation "android.arch.navigation:navigation-fragment-ktx:$nav_version" implementation "android.arch.navigation:navigation-ui-ktx:$nav_version" }
8. NAVIGATION ADD NAVIGATION RESOURCE
9. NAVIGATION ADD NAVIGATION RESOURCE
10. NAVIGATION ADD NAVIGATION RESOURCE ▸ Right-click on navigation resource directory ▸ New > Android Resource File ▸ Input name <?xml version="1.0" encoding="utf-8"?> <navigation xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto" android:id="@+id/main_navigation"> </navigation>
11. NAVIGATION NAVIGATION LAYOUT <?xml version="1.0" encoding="utf-8"?> <androidx.coordinatorlayout.widget.CoordinatorLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto" android:layout_width="match_parent" android:layout_height="match_parent"> <com.google.android.material.appbar.AppBarLayout android:layout_width="match_parent" android:layout_height="wrap_content"> <androidx.appcompat.widget.Toolbar android:id="@+id/toolbar" android:layout_width="match_parent" android:layout_height="?attr/actionBarSize"/> </com.google.android.material.appbar.AppBarLayout> <fragment app:layout_behavior="@string/appbar_scrolling_view_behavior" android:layout_width="match_parent" android:layout_height="match_parent" android:id="@+id/nav_host_fragment" android:name="androidx.navigation.fragment.NavHostFragment" app:navGraph="@navigation/main_navigation" app:defaultNavHost="true"/> </androidx.coordinatorlayout.widget.CoordinatorLayout> Handles the navigation
12. NAVIGATION PROGRAMMATICALLY val finalHost = NavHostFragment.create(R.navigation.main_navigation) supportFragmentManager.beginTransaction() .replace(R.id.nav_host_fragment, finalHost) .setPrimaryNavigationFragment(finalHost) .commit()
13. NAVIGATION HOOK UP NAVIGATION class MainActivity : AppCompatActivity() { override fun onCreate(savedInstanceState: Bundle?) { super.onCreate(savedInstanceState) setContentView(R.layout.navigation_acitivty_layout) setSupportActionBar(toolbar) // From -ktx setupActionBarWithNavController(findNavController(R.id.nav_host_fragment)) // Otherwise need to call // NavigationUI.setupActionBarWithNavController(this, // Navigation.findNavController(this, R.id.nav_host_fragment)) } override fun onSupportNavigateUp(): Boolean { return findNavController(R.id.nav_host_fragment).navigateUp() } }
14. THAT’S ALL!
15. TIPS!
16. NAVIGATION ▸ Pass data between fragment using ViewModel (or Room) ▸ Single activity for single flow (not necessarily for the whole app) ▸ Don’t have to use fragments (custom navigators) ▸ ActivityNavigator can help with migrating ▸ Use safeArgs (if possible)
17. NAVIGATION EXAMPLE APP (EXERCISE LOGGER) ▸ Let’s you create a new exercise entry ▸ View log of exercises ▸ Update user info ▸ Update exercise from log
18. NAVIGATION COMPONENTS USED ▸ Kotlin ▸ Room ▸ LiveData ▸ Coroutines ▸ and of course Navigation
19. LET’S LOOK AT SOME CODE
20. CONDITIONAL
21. NAVIGATION ISSUES ▸ app:type renamed to app:argType but not in editor