Unit 02 of 02
Project Structure and Tools
The manifest file that declares components and permissions, qualified resources and configuration changes, build scripts, dependencies and build types, product flavors and build variants, the development environment with the emulator, device and profiling tools, and install-time and runtime permissions.
Published Updated
Lessons
- 01 The Manifest File The manifest file's role in introducing the app to the platform, and a model of merging that asks, for each element, whether what was wanted is preserved. 13 min read
- 02 The Resource System A model of selecting a resource ID from qualified directories by configuration, covering exact match, falling back to the default, and qualifier precedence. 13 min read
- 03 The Build System A model of how the build system reads dependencies and the version catalog, how the highest version is selected for a transitive dependency, and how a strict version constraint behaves. 12 min read
- 04 Product Flavors A model of the build variants that arise from the product of product flavors and build types, the variant filter, and source set precedence. 13 min read
- 05 The Development Environment A model of the request to install an app on a device, measured against the API level, the debugging authorization and the processor architecture. 11 min read
- 06 The Permission Model A fulfillment model of install-time and runtime permissions, normal and dangerous permissions, precise and approximate location, denial and the do-not-ask-again state, with the closing table of the course. 13 min read