React and React Native - Fifth Edition (Mikhail Sakhniuk, Adam Boduch)（Z-Library）

【One-Line Pitch】 A single, structured tour of the modern React ecosystem that pairs web React fundamentals with React Native's cross-platform mobile workflow, ideal for developers who already know JavaScript and want one book that connects the dots from components to shipped apps. 【Book Arc】 - **Opening (~0%–10%)**: Frames React as a view-layer library rather than a mega-framework, explains declarative UI and re-rendering, and sets up a modern project with bundlers, frameworks, or online editors. - **Early (~10%–36%)**: Builds the web foundation — TypeScript typing for props/state/events/context/refs, routing and route parameters, code splitting with lazy and Suspense, UI framework components, batching and prioritized state updates, data fetching (Fetch, Axios, TanStack Query, GraphQL), global state (Context/useReducer, Redux, MobX), server-side rendering with Next.js and React Server Components, and unit testing with Vitest. - **Middle (~36%–52%)**: Pivots to React Native — why it exists versus mobile web, its architecture and thread communication, CLI/Expo project setup, and Flexbox-based responsive layouts. - **Late (~52%–64%)**: Applies React Native to real app concerns: navigation, item lists with sorting/filtering/lazy loading/pull-to-refresh, geolocation and maps, forms, gestures, progress indicators, modals, animations (Animated API and Reanimated), image handling, and offline detection/sync. - **Ending (~64%)**: Closes with the practical mobile feature set and points readers toward the broader React ecosystem; the excerpts do not cover a distinct concluding chapter beyond this. 【Book Arc】 (progression note) The book deliberately moves fundamentals → advanced web patterns → cross-platform practice, so the React Native half assumes the component, state, and TypeScript habits built earlier. 【Key Takeaways】 - **React is intentionally just the view layer** (Opening): its small API surface (components, data, lifecycle, events, JSX) is a feature, not a limitation — it leaves room for routing, state, and testing tools to be chosen deliberately. - **Declarative UI plus re-rendering is the core mental model** (Opening): JSX describes a snapshot of the UI, and React reconciles changes over time; understanding this explains both React's ergonomics and its performance trade-offs. - **TypeScript is treated as part of the React workflow, not an add-on** (Early): the book types props, state, event handlers, context, and refs, which is where most real-world React bugs surface. - **Modern React performance is about scheduling, not just memoization** (Early): batching, prioritized updates, and async state handling are presented as the levers for high-performing apps. - **State management is a spectrum** (Early): Context with useReducer, Redux, and MobX are compared so readers can match tooling to app scale rather than defaulting to one library. - **Data fetching and rendering strategy belong together** (Early): Fetch/Axios/TanStack Query/GraphQL are covered alongside SSR, static generation, and React Server Components via Next.js — the choice of where data loads shapes the architecture. - **React Native is explained architecturally before it is used** (Middle): the JS/native thread split and module communication clarify why mobile performance and styling differ from the web. - **Mobile chapters follow the shape of a real app** (Late): navigation, lists, maps, forms, gestures, modals, animations, images, and offline handling read as a build order rather than isolated API tours. 【Reading Tips】 - **Deep-read the first third** if you are new to modern React; the TypeScript, state-update, and data-fetching chapters set vocabulary used throughout the native half. - **Skim the React Native architecture chapter on a first pass**, then return to it when animations or native modules behave unexpectedly — it explains the "why" behind later quirks. - **Treat the mobile chapters as a checklist**: implement navigation, lists, and forms in a small Expo project as you read, since these are the highest-reuse patterns. - **Use the testing chapter as a bridge**, not a finale — write a few Vitest tests for components you build in earlier chapters to cement the workflow. - **Don't expect deep dives everywhere**: the book is broad by design; pick one state library and one data-fetching approach to practice rather than sampling all of them. 【Coverage Limits】 This guide is based on stratified excerpts covering the table of contents, preface, and portions of the opening and mobile chapters; detailed code walkthroughs and the final sections are only partially represented, so specific implementation claims are limited to what the excerpts show.