7 posts
AI can ship your React Native MVP fast, but without guardrails each small change can break unrelated flows.
The first stretch of vibe coding feels absurdly productive. Cursor and Claude Code can generate login, dashboard, settings, and push notifications fast enough…
Your app works fine in dev, but users get a blank screen when they return after lunch. Here's the resume status pattern that handles native lifecycle properly.
You built a beautiful Expo app in Cursor. Claude Code generated the auth flow, the dashboard, the settings screen. You shipped it. Users downloaded it. Then…
If optional SDKs initialize like core infrastructure, they can crash your app on launch.
A common launch failure in vibe-coded mobile apps is that analytics, attribution, or crash reporting gets initialized alongside truly critical services. If one…
You shipped an MVP in a weekend with Cursor, but now changing one color breaks 47 files. Here's the styling contract that stops the bleeding.
You opened Cursor, typed a prompt, and watched Claude Code generate a full React Native UI in seconds. Flex layouts, rounded buttons, color themes — all…
AI-generated auth feels fine until a new feature reaches into the wrong service.
One recurring failure mode in vibe-coded React Native apps is that a new feature imports an existing service directly, reaches into state it does not own, and…
Deep links, push payloads, and shared URLs are all untrusted input.
Deep-link bugs in vibe-coded apps usually start with boring input problems: a malformed user ID, an outdated campaign URL, a missing enum value in a push…
Stop writing useEffect subscriptions that leak memory and miss state updates. Here's the React 18 pattern for bulletproof external state.
I used to write network detection hooks the way most vibe coders do: a that subscribes to NetInfo, updates state when connectivity changes, and hopes for the…