Android Application Architecture

on YouTube ↗42m

" summary

Demonstrates a concrete architecture that treats sync as a first-class problem: UI is backed by a persistent local model, writes are saved to disk and queued as persistent jobs (uses Job Queue), and the app does optimistic rendering so comments appear immediately and later turn “confirmed.” The demo survives server crashes and process kills, preserves send order by running jobs FIFO, deduplicates with client-generated IDs, and wires DI with Dagger; network and disk use separate network and local queues so UI stays responsive.

AI-written summary · about

" chapters (14)

1. 0:00Intro
2. 0:34Application Architecture
3. 2:13User Experience
4. 11:47Dependency Injection
5. 12:34Networking
6. 16:32Fragments and Views
7. 18:03Memory
8. 20:11Ugly Code
9. 20:38Demo
10. 28:02Global Event Bus
11. 29:22Client ID
12. 30:12Synchronization
13. 33:52Questions
14. 39:42Client Consistency

" related talks

• 40mClean, Easy & Stable Android ArchitectureBritt Barak · Devoxx Belgium 2017
• 36m“Make your app work perfectly offl…” — Connection InterruptedXavier F. Gouchet · Android Makers 2019
• 47mClean Architecture for AndroidJose Manuel Pereira · Codemotion Madrid 2015
• 39mIndemnity in the Data LayerTunji Dahunsi · droidcon New York 2022
• 37mIdemnity in the Data LayerAdetunji Dahunsi · Chicago Roboto 2022
• 06mCreate offline-first appsTJ Dahunsi · Android Dev Summit 2022
• 39mAndroid Architecture Components: fit like a gloveDoug Stevenson · droidCon NYC 2018
• 17mBest Practises for Android Development as a Daily BusinessStefan Neidig · droidcon Berlin 2018