Best Practises for Android Development as a Daily Business
summary
Three- to four‑person team handles many concurrent projects with tight deadlines and reports measurable time saved by eliminating boilerplate: a custom layout annotation removes manual inflation, shared live templates auto-generate view variable names, and a unified Android Square code style plus coding guidelines enforce convention over configuration. Architecture splits UI (MVP + interactors) and a data module with data stores, sources and transformers. Also use overridden toString producing JSON for readable logs and tackled tricky releases like the Citrix mobile store.
AI-written summary · about
chapters (5)
- 0:00Introduction and context
- 3:59Starting with multiple projects
- 5:24Optimizing workflow and process
- 12:10Architecture and coding guidelines
- 14:15Advanced tips and conclusion
related talks
41mWrite once, ship multiple times
40mApp Development - Pragmatic Best Practices
37mTackling Android Development at Scale
47mClean Architecture for Android
43mThe Engineering Playbook for Growing Android Teams
32mBuild a modular Android app architecture
37mWrite once, ship multiple times
40mScaling Android Apps