Fragments vs. CustomViews

A quick talk showing the pros of use CustomViews instead Fragments to create our Android apps

Transcript

1. #BADGlightningTalks 2018 Fragments vs CustomViews yet an old but still present war
2. #BADGlightningTalks 2018 Why Fragments instead of CustomViews?
3. #BADGlightningTalks 2018 Manual instantiation MyFragment fragment = MyFragment.newInstance(index); FragmentTransaction ft = getFragmentManager().beginTransaction(); ft.replace(R.id.parent, fragment); ft.commit(); MyCustomView customView = new MyCustomView(context); parentView.removeAllViews(); parentView.add(customView);
4. #BADGlightningTalks 2018 Embedding in xml <fragment android:name="my.package.MyFragment" android:id="@+id/my_fragment" android:layout_width="match_parent" android:layout_height="match_parent" /> <my.package.MyCustomView android:id="@+id/my_view" android:layout_width="match_parent" android:layout_height="match_parent" />
5. #BADGlightningTalks 2018 Lifecyrcle
6. #BADGlightningTalks 2018 Wait… what?
7. #BADGlightningTalks 2018 So you’re using fragments… because? It’s the Google’s way
8. #BADGlightningTalks 2018 Really?
9. #BADGlightningTalks 2018 So you’re using fragments… because? The backStack
10. #BADGlightningTalks 2018 Create your own! Or use a router library like: Kartographer, Cicerone, Naviganto, Mortar, there are many!
11. #BADGlightningTalks 2018 So you’re using fragments… because? The savedInstance
12. #BADGlightningTalks 2018 Use a State class (parcelable or not) and save it using the repository pattern
13. #BADGlightningTalks 2018 DON’T
14. #BADGlightningTalks 2018 JUST Think by your own.
15. #BADGlightningTalks 2018 THANKS! & : @firezenk