Taking Advantage of Android Platform Features
summary
Gmail’s Android team explains concrete patterns: modular UI with fragments that store parcelable state via Fragment arguments and use empty constructors, register/deregister delegates in onActivityCreated/onDestroy to avoid stale pointers, push via GCM + IntentService and sync only changed timestamps, notifications with expandable big text and actionable buttons and mark as seen on dismiss, use CursorLoaders and object-cursors to build models off the UI thread, prefer DownloadManager one-line request for large files, and back up prefs with BackupAgentHelper.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:48Modularization
- 5:17Fragments
- 7:00Fragment Construction
- 8:00Sample App
- 9:22Coupling Pattern
- 13:00Gmail
- 16:06Notifications
- 19:14Customization
- 20:36Loaders
- 25:29Object Cursors
- 28:41Download Manager
- 31:52Backup Restore
- 34:50Support Library
- 36:51Source Code
- 38:26Google Play Services
related talks
28mHow Android Uses Data Structures Behind the Scenes
40mProtips: A fresh look at advanced topics for Android experts
48mFramework Fireside Chat
33mBust the Android Fragmentation Myth
17mBest Practises for Android Development as a Daily Business
01h 45mAndroid Essentials
46mModern Android: How to ditch Activities and Fragments
27mCommon Poor Coding Patterns and How to Avoid Them