One crashing screen should not kill the app: error boundaries that hold

UpdatedSeptember 8, 2026

AI coding assistants write screens fast and break them faster. One undefined field from a changed API, one date parse on a null value, one image with a missing URI, and the whole app goes white. The user did nothing wrong. The crash was a rendering mistake in a corner they never touched.

React Native has exactly one built-in answer for render failures: the error boundary. It is a class component that catches JavaScript errors during rendering, logs them, and shows fallback UI instead of unmounting everything. Most AI-generated codebases ship without a single one. The default export is the screen, the error propagates to the root, and the app blanks.

This is an excerpt. Read the full post at otf-kit.dev/blog/react-error-boundaries-crash-isolation — full-stack kits your AI coding agent can actually ship to production. Browse the kits →

#react-native #architecture #cross-platform

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

Cursor rules that keep mobile repos shippable under production pressure

Every team using Cursor on a mobile repo hits the same moment. The agent scaffolds a screen beautifully, then imports a web-only library, breaks the Expo Router layout, or rewrites your auth guard wit

Sep 8, 20261 min read

Cursor rules that keep mobile repos shippable under production pressure

Vercel cron jobs that keep mobile backends fast and reliable

Mobile apps rarely fail at noon on a quiet Tuesday. They fail at 2 a.m. when a token refresh breaks, when a stale cache poisons the home feed, or when an abandoned cart sequence never fires because no

Sep 8, 20261 min read

Vercel cron jobs that keep mobile backends fast and reliable

Expo config plugins in production: the guide that prevents native drift

Every Expo developer meets the config plugin moment eventually. You need a native SDK — push notifications, Sign in with Apple, a Bluetooth library — and the managed workflow suddenly asks you to edit

Sep 8, 20261 min read

Expo config plugins in production: the guide that prevents native drift

Supabase realtime keeps mobile presence honest without polling your database dead

Polling is the default sin of mobile realtime. A timer fires every five seconds, hits your API, returns nothing new, and drains battery while your Postgres connection pool quietly fills with identical

Sep 8, 20261 min read

Supabase realtime keeps mobile presence honest without polling your database dead

Defend your AI features against prompt injection: production patterns that hold

Features powered by language models — support copilots, document question-answering, triage assistants — are genuinely delightful when they work. They read messy human input and produce useful structu

Sep 8, 20261 min read

Defend your AI features against prompt injection: production patterns that hold

OTF — kits your AI coding agent can ship to production

534 posts

Engineering notes on shipping production apps with AI coding tools — Claude Code, Cursor, Codex, Lovable, Bolt — and the stack underneath: React Native, Expo, Next.js, Supabase. Honest takes on what works, what breaks, and the full-stack kits that get you to production faster. By OTF.

Command Palette

Comments

More from this blog