16 posts tagged with "Expo"

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.

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.

Expo Router API routes give React Native teams a practical middle ground between "everything is client-side" and "we need a separate backend project before we can ship." With EAS Hosting, those routes can be deployed alongside an Expo Router web app and used for server-side work such as secrets, validation, webhooks, AI calls, and small backend endpoints.

We have completed a major update across the current Instamobile React Native templates. The new baseline is TypeScript-first, aligned with the latest React Native and Expo ecosystem direction, and documented with a cleaner path from setup to production verification.

The September 2026 mobile-development baseline is clearer than it was earlier this year. React Native 0.87 advances native build requirements and makes the Strict TypeScript API the default. Expo SDK 57 provides a separate, slightly earlier React Native baseline. Google Play's target API deadline now affects new app submissions and updates.

This briefing separates those facts so production teams can plan upgrades without treating every ecosystem release as one migration.

AI app builders can turn a product description into screens, navigation, and a React Native or Expo project quickly. That makes them useful for exploring an idea. It does not make every generated project production-ready.

This guide explains how to evaluate the generated result: what to inspect, which claims to verify, and where engineering work still begins after the first prompt.

Galio is a UI toolkit and component framework for React Native that provides a consistent set of ready-made, themeable building blocks (buttons, cards, text, inputs, nav bars, etc.) so you can prototype and ship mobile UIs faster. The galio repository includes the core components and a lightweight theme system in src/theme (see colors.tsx, sizes.tsx, index.tsx) plus components under src/ such as Block, Button, Text, Input, Card, Avatar, NavBar and more.

Learn more on the official site: galio.io and browse the source and examples on GitHub: github.com/galio-org/galio.

Network bugs in React Native usually fall into a few categories: the request never leaves the device, the server rejects it, the response shape is different from what the app expects, or the UI keeps using stale data. The fastest way to debug them is to inspect the request, log safely, reproduce on the platform that fails, and verify the server-side trace.

Older Android phones expose every expensive choice in a React Native app: heavy startup work, oversized images, slow lists, chatty network calls, JS-thread animations, and debug-only assumptions. The goal is not to chase one magic setting. The goal is to measure on real hardware, reduce work on the critical path, and ship a release build that keeps memory, CPU, and frame time under control.

React Native upgrades are safest when you treat them as a controlled migration, not a package bump. The work spans JavaScript dependencies, native iOS and Android project files, Expo modules, build tooling, runtime versions, and QA. This guide gives you an evergreen upgrade path that works for bare React Native apps, Expo apps, and production templates.

Most production React Native apps talk to at least one REST API: auth, profiles, feeds, search, orders, payments, media, notifications, analytics, or admin workflows. The important decision is not whether you use Fetch or Axios. The important decision is whether every request goes through a typed, observable, cancellable, and secure API layer.

Memory leaks in React Native usually come from resources that outlive the screen that created them: timers, subscriptions, unresolved requests, sockets, navigation listeners, heavy lists, image caches, and native module handles. The fix is not a single package. It is a repeatable loop: reproduce the leak, profile it in a realistic build, remove the retained reference, and verify that memory returns to a stable baseline.