Development Skill
Angular Migration
Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and…
$15
Native
Cross-platform mobile development patterns with Expo, React Native, iOS, and Android
Cross-platform mobile development patterns for Expo and React Native that get you to a real, shippable app instead of a demo. It bakes in Expo Router navigation, NativeWind styling, secure token storage, offline-first data sync, and the mandatory four-state rendering: loading, error, empty, success, so every screen handles reality, not just the happy path.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category Development
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Tokens live in the Keychain, never AsyncStorage, and every data screen ships all four states. Those are the non-negotiables this cross-platform build enforces from scaffold to handoff.
- Scaffolds with create-expo-app and installs every native package via npx expo install, never npm install, because version mismatches against the Expo SDK surface as runtime crashes. expo-doctor verifies compatibility.
- Lays the navigation tree with Expo Router file conventions: a root layout wiring QueryClient and AuthProvider, (tabs) and (auth) groups, dynamic [id] routes and a +not-found screen.
- Wires auth by the secure storage hierarchy: the Supabase client persists sessions through an expo-secure-store adapter (native Keychain/Keystore), never AsyncStorage for tokens, with an AuthProvider listening to onAuthStateChange.
- Builds data access as TanStack Query hooks over Supabase: useQuery for lists, useMutation with invalidateQueries on success, cached data shown first while a background refetch runs.
- Renders every data screen in all four states as a hard checklist: loading skeleton (not a spinner), error state with a retry button, empty state with a suggested action, and a virtualized FlatList with RefreshControl for success.
- Closes on the completion checklist before any handoff: real API integration, secure token storage, zero TypeScript errors, NativeWind instead of inline styles, and the app exercised on both iOS and Android.
One power source. 6 lines out.
native · core
core active · 6 lines
- ✓ scaffolding a new expo app
Scaffolding a new Expo app with file-based routing
- ✓ wiring supabase auth with
Wiring Supabase auth with secure session persistence
- ✓ building list screens with
Building list screens with pull-to-refresh and all four states
- ✓ storing tokens safely in
Storing tokens safely in the device keychain, not plain storage
- ✓ shipping hotfixes over the
Shipping hotfixes over the air without a full app-store review
- ✓ styling components with
Styling components with NativeWind instead of inline styles
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Ship screens that never show a blank page on error or empty data
license: perpetual -
Keep auth tokens in encrypted native storage by default
license: perpetual -
Deliver platform-native feel on both iOS and Android
license: perpetual -
Push fixes instantly via over-the-air updates
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Expo Router file structure with tab and auth groups
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
For developers building production React Native apps with Expo who want secure storage, offline-aware data, and complete state handling from day one.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
I run a bare React Native app without Expo. How much of this applies?
The architectural patterns travel: four-state screens, TanStack Query hooks, and the layered auth thinking are toolchain-neutral. But the file-based routing, secure-store adapter, and over-the-air update flow are Expo-specific, so a bare workflow keeps the concepts and swaps the implementations.
-
What does the mandatory four-state pattern actually change in my screens?
Every screen explicitly renders loading, error, empty, and success: a skeleton while fetching, a retry path on failure, and a designed empty state instead of a blank list. It removes the class of bugs where a screen silently shows nothing because only the happy path was built.
-
Do over-the-air updates mean I never face app store review again?
No. OTA covers the JavaScript layer, so logic and UI hotfixes ship instantly, but anything touching native modules, permissions, or the binary still requires a store build and review. It shrinks how often you queue for review, it doesn't abolish the queue.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.