173 posts tagged with "React Native"

An Expo SDK upgrade is not just a package update. It can change the React Native version, native build tools, configuration plugins, Expo Go support, and the behavior of the iOS and Android projects generated by prebuild.

The safest decision is not always "upgrade immediately." It is the option that keeps your app buildable, testable, and recoverable. This guide gives you a repeatable way to choose between upgrading now, testing in a separate branch, or waiting for a specific blocker to be resolved.

A React Native app can connect to Supabase in minutes. Production readiness takes more work: every exposed table needs an authorization model, mobile auth links must return to the right build, database changes need a repeatable release process, and the team needs a way to detect and recover from failures.

This checklist starts after the basic integration works. Use it before the first public release and repeat the relevant sections before major launches.

Turning a WooCommerce store into a mobile app starts with an architecture decision, not a code generator. A WebView wrapper, a hosted app builder, and a source-owned React Native app can all put a store on a phone, but they offer very different levels of user experience, control, security, and long-term cost.

This guide helps you choose the right path and understand the work that remains after the first product screen appears.

Android 17 is API level 37. Preparing a React Native or Expo app for it is not one switch: running the existing app on an Android 17 device, compiling against SDK 37, and targeting API 37 are three different decisions.

This guide keeps those layers separate so a team can find compatibility issues before opting into a new target SDK.

React Native 0.87 is now the active stable release. It makes the Strict TypeScript API the default, updates the Android build baseline, raises the minimum Node.js version, and introduces changes that can expose assumptions in older projects.

This is a practical pre-upgrade check. You can run it in about ten minutes and decide whether your project is ready, needs a small preparation pass, or should stay on its current version until a dependency catches up.

AI app development changed quickly again this summer. Frontier models became less expensive, coding agents became more capable, and the mobile platforms moved serious AI workloads closer to the device.

If you have been away from mobile development for a few months, this is the short version of what changed, what is real today, and what is worth testing in your next app.

Compare React Native and Flutter by team skills, UI requirements, native integration, upgrade cost, and long-term ownership rather than benchmark headlines. This revised guide emphasizes supported APIs, production tradeoffs, and an upgrade-friendly path without tying the advice to a calendar year.

Learn React Native from a production-oriented baseline that includes TypeScript, framework selection, native boundaries, and release builds. This revised guide emphasizes supported APIs, production tradeoffs, and an upgrade-friendly path without tying the advice to a calendar year.

Optimize React Native from measurements, separating JavaScript work, rendering, native work, network latency, and image cost. This revised guide emphasizes supported APIs, production tradeoffs, and an upgrade-friendly path without tying the advice to a calendar year.

Build a threat model for React Native that covers secrets, local storage, network traffic, authentication, native permissions, and supply-chain risk. This revised guide emphasizes supported APIs, production tradeoffs, and an upgrade-friendly path without tying the advice to a calendar year.

Use Zustand for shared client state while keeping server state, navigation state, forms, and ephemeral component state in their proper owners. This revised guide emphasizes supported APIs, production tradeoffs, and an upgrade-friendly path without tying the advice to a calendar year.

Test React Native behavior through accessible queries and realistic user actions, with native boundaries mocked only where necessary. This revised guide emphasizes supported APIs, production tradeoffs, and an upgrade-friendly path without tying the advice to a calendar year.