Practical React Native Build Two Full Projects and One Full Game using React Native (Frank Zammetti)（Z-Library）

【One-Line Pitch】 A hands-on guide that teaches React Native by having you build two complete apps and a full game, so you learn the framework the way working developers actually do—by shipping something. Best for developers with some JavaScript/React background who want a practical, project-driven path into cross-platform mobile development. 【Book Arc】 - **Opening (~0%–10%)**: Frames the mobile cross-platform problem (native vs. web-tech trade-offs), explains where React Native came from and what it offers, then walks through prerequisites, installation, and a first "Hello World" app. - **Early (~10%–30%)**: Establishes the core mental model—Virtual DOM, the bridge to native, JSX, components, render lifecycle, props/state, and styling—then surveys the component and API catalog you'll draw on throughout the projects. - **Middle (~30%–55%)**: Begins the first full project (a Restaurant Chooser), covering app structure, configuration, custom components, and screen-by-screen construction; also introduces supporting tooling like Node.js and the create-react-native-app workflow. - **Late (~55%–85%)**: Builds out the remaining project work and the game, including game logic such as matrix generation and solvability, control menus, win screens, and app layout—showing React Native from a very different angle than a typical form-and-list app. - **Ending (~85%–100%)**: Closes with debugging and performance guidance—Chrome DevTools, custom debuggers, React Developer Tools, console logging, ListView performance, main-thread work, animation/FPS pitfalls, and platform-specific gotchas. 【Book Arc note】 The excerpts do not fully cover the middle-to-late chapter boundaries, so the exact split between the second app and the game is approximate. 【Key Takeaways】 - **React Native is a real native option, not a WebView wrapper** (Early): The book stresses that it delivers native look, feel, and performance while letting you write one codebase for iOS and Android—this is the core reason to choose it. - **Know the trade-offs before committing** (Early): The author is candid about cons—lag behind new OS APIs, harder debugging due to abstraction layers, the need to learn JSX, and the possibility you'll still write native code for missing features. - **Core concepts come first, projects second** (Early): Virtual DOM, the bridge, JSX, components, lifecycle, props/state, and styling are presented as the foundation you must internalize before the builds make sense. - **Learning happens through three real builds** (Middle): Two full apps and one game are the spine of the book; each feature is introduced in the context of something you can actually install and use, not contrived snippets. - **The ecosystem matters as much as the core** (Middle): Expo, NativeBase, React Navigation, Redux, and Lodash appear alongside React Native, reflecting how real apps are assembled from supporting libraries. - **Mobile apps often need a backend** (Middle): A Node.js and Socket.io server is built so the app has something real to talk to, giving a holistic client-plus-server view beyond React Native itself. - **Games expose a different side of the framework** (Late): Building a game forces you to grapple with logic, layout, and interaction patterns that ordinary apps don't surface, broadening your sense of what React Native can do. - **Debugging and performance are first-class skills** (Ending): The book closes with concrete pitfalls—main-thread work, ListView performance, animation FPS drops, touchable responsiveness, and an iOS image-animation quirk—plus the tools to diagnose them. 【Reading Tips】 - **Skim the opening history and pros/cons quickly** if you already know why you want React Native; slow down at the core concepts (Virtual DOM, bridge, JSX, props/state), since everything later depends on them. - **Build alongside the book with the source code bundle** from the publisher/GitHub rather than typing everything; the author explicitly recommends running and modifying the code as you read. - **Treat the projects as the main event**: read the conceptual chapters once, then work through the apps and game actively, pausing to change behavior and see what breaks. - **Don't skip the debugging/performance chapter** even though it comes last—the gotchas listed there are the kind of thing that costs hours in real projects. - **Watch for version sensitivity**: the author developed against specific Node/tooling versions, so if setup fails, matching the stated versions is a reasonable first move. 【Coverage Limits】 This guide is based on stratified excerpts that cover the introduction, core concepts, project setup, and the closing debugging/performance material; the detailed content of the second app and much of the game's implementation is only partially represented, so specifics there are inferred at a high level.