How to Build Android Apps with Kotlin, 2nd Edition (Alex Forrester, Eran Boudjnah etc.)（Z-Library）

【One-Line Pitch】 A hands-on, exercise-driven path from your first Android Studio project to tested, well-structured, publishable Kotlin apps. Best for developers with basic Kotlin who want practical Android skills rather than theory. 【Book Arc】 - **Opening (~0%–10%)**: Sets up Android Studio, project configuration, the manifest, and Material theming — the groundwork that makes every later exercise runnable. - **Early (~10%–32%)**: Builds UI fundamentals — layouts, input fields, intents for navigation, and the fragment lifecycle — solving the "how do screens and data connect" problem. - **Middle (~32%–48%)**: Moves into adaptive and navigational structure: dual-pane layouts for tablets, the Jetpack Navigation component, and navigation patterns like the drawer. - **Late (~48%–70%)**: The excerpts jump to Part 3, covering testing (JUnit, Mockito, Robolectric, Espresso, Compose testing, TDD) and Android Architecture Components — the shift from "it works" to "it's verifiable and maintainable." - **Ending (~70%–100%)**: Excerpts do not cover this range; presumably publishing and release topics, but this guide cannot confirm their content. 【Key Takeaways】 - **Configuration choices shape the whole project** (Opening): package naming, minimum SDK, and save location are decided at project creation and are awkward to change later, so the book treats them as real decisions, not defaults to click through. - **The manifest is the app's contract with the system** (Early): the MAIN action plus LAUNCHER category is what makes an app launchable; removing either breaks startup in specific, instructive ways. - **Material components add polish cheaply** (Early): wrapping EditText in TextInputLayout/TextInputEditText gives labels, hints, and focus animation with minimal code — a recurring theme of using ready-made components over custom views. - **Fragments have their own lifecycle nested inside the activity's** (Early): callbacks fire child-first on teardown, and view work belongs in onViewCreated, not onCreateView — a distinction the book demonstrates via logging and rotation. - **One codebase, two layouts** (Middle): resource qualifiers like sw600dp let phones show list-then-detail while tablets show a dual-pane view, with the activity deciding behavior by checking whether the detail view exists. - **Navigation is about context, not just movement** (Middle): the book frames drawer, top-level, and secondary destinations around always telling users where they are, with the Navigation component encoding flows as graphs. - **Testing is layered, not monolithic** (Late): unit tests with JUnit and Mockito, integration tests with Robolectric, and UI tests with Espresso and Compose testing each cover a different confidence level. - **TDD is taught as a workflow, not a slogan** (Late): exercises walk from a failing test to implementation, including an activity-scale TDD exercise, making the discipline concrete. 【Reading Tips】 - **Do the exercises in order through the early chapters.** The book is exercise-first; reading without typing leaves the manifest, lifecycle, and layout lessons abstract. - **Deep-read the fragment lifecycle and navigation chapters.** These are the densest conceptual spots; the callback ordering and dual-pane logic reward slow reading and logcat experimentation. - **Skim the theming and XML styling sections** if you already know Material Design — treat them as reference for color roles (primary, variant, on-primary) rather than linear reading. - **Treat Part 3 as a separate pass.** Testing and architecture components assume the UI chapters are solid; return to them after building at least one small app end to end. - **Keep Android Studio open beside the book.** Version-specific dialogs and defaults drift, so match the text against your actual IDE. 【Coverage Limits】 The excerpts are heavily weighted toward the opening, UI, fragments, navigation, and testing chapters; the later portion of the book (likely publishing and advanced topics) is not represented, so this guide cannot describe it.