Page 3 - React Native

React Native Skia brings Google's Skia graphics engine, the same one powering Chrome, Android, and Flutter, directly into React Native through JSI. Instead of building shapes out of native views or SVG elements, Skia draws onto a single native surface, which makes custom graphics like signature pads, custom charts, or image filters noticeably faster than classic view-based approaches.

The app size of a React Native app determines install rates, store warnings, and reach in markets with slow connections. Android App Bundle with R8 shrinking, iOS App Thinning, WebP images, and continuous size monitoring in the CI pipeline shrink app size measurably, without sacrificing functionality.

Any React Native app that needs to make larger amounts of data available offline eventually needs a real relational database. SQLite, through expo-sqlite, delivers fast, native local data storage without ORM overhead: hand written SQL, versioned migrations and parameterized queries that give full control over schema and performance.

Push notifications are not a single, uniform feature but an interplay of APNs, Firebase Cloud Messaging, operating system permissions and app state. Anyone who wires up FCM in React Native without a clean setup for foreground, background and quit state loses notifications exactly when users need them most. This article shows how the Firebase project, the FCM SDK, permissions, payloads, deep linking and token management fit together reliably in React Native.

A bottom tab navigation with five or six tabs will, without deliberate configuration, sometimes render every included screen right at the very first app launch, even though the user initially only ever sees the first tab. Lazy loading pushes rendering a tab to the moment it actually becomes active for the first time, and can noticeably shorten the perceived startup time of a tab based app. That effect comes at a price though, when a previously visited tab loses its internal state on switch. This article covers the practical configuration, the concrete trade off, and how the effect can actually be measured.

Performance profiling in React Native means measuring jank, unnecessary re-renders, memory leaks and slow network calls instead of diagnosing them by gut feeling. React Native DevTools, the React Profiler, and native tools like Xcode Instruments and Android Studio Profiler together give a complete picture of why an app feels slow and how to fix it in a targeted way.

A network outage should never mean a dead app. With cache persistence, a mutation queue for pending changes, and thoughtful conflict resolution, a GraphQL application can be built so users keep reading, keep working, and keep making changes while the connection is waited on in the background.

A React Native monorepo with Turborepo bundles multiple apps, shared packages, and build caching into a single repository. This article walks through the setup with pnpm workspaces, the Turborepo pipeline configuration, and the Metro adjustments a stable monorepo needs.

Subscription commerce in React Native means far more than adding a buy button. Entitlements, paywall design, server-side validation and how you handle failed renewals decide whether a subscription model reliably generates revenue or quietly leaks it. This article walks through the full path from the first product definition to a synchronized entitlement status.

Automated accessibility checks reliably catch missing labels, undersized touch targets, and contrast errors, and can be wired directly into the CI pipeline so a regression surfaces before it reaches the user. What they cannot catch is whether a screen reader announcement actually makes sense, or whether a navigation order is logical for a blind user. This article covers which problems can be detected automatically in React Native, how to integrate accessibility checks into the CI pipeline, and where the line to manual screen reader testing needs to be deliberately drawn.