The ART of organizing resources
summary
Proposes a single naming rule—what_where_description with optional size—that aims to make resources discoverable, logically grouped, and less error prone; cites Facebook’s scale (about 3,200 layouts, 8,000 strings, 5,000 drawables ≈ 28,000 resources) to justify it. Shows concrete file-name patterns for layouts, ids, drawables and dimensions, supplies a printable cheat sheet and a demo project, and recommends enforcing rules via lint or IntelliJ inspections though no official tool exists yet; leverages Android Studio autocomplete to make the scheme practical.
AI-written summary · about
chapters (4)
related talks
33mBust the Android Fragmentation Myth
20mBreaking Down Modularization
42mIngredients for a healthy codebase (en)
38mStyleguide-Driven Development
27mCommon Poor Coding Patterns and How to Avoid Them
20mDo’s and don’ts: Mindset for optimizing apps for larger screens
28mHow Android Uses Data Structures Behind the Scenes
01h 05mStyleguide-Driven Development