All Articles
What to Decide Before Spreading One Idea Across Every Apple Platform
Rork Max can generate native Swift for iPhone, iPad, Apple Watch, Apple TV, and Vision Pro from a single idea. But 'can ship to all of them' and 'should ship to all of them' are different things. From an indie developer running several apps, here's a framework for choosing which devices to add and which to skip, reasoned backward from operating cost and usage context.
Why Your Rork List Starts Duplicating and Dropping Rows as It Grows — Cursor Pagination and Resilient Refetch State
The naive offset pagination Rork scaffolds for you quietly breaks the moment your list changes underneath the user. Here is how to move to a cursor contract, fold every fetch state into one usePaginatedList hook, and recover failed page loads with exponential backoff — implementation first.
Bugs Rork Can Fix vs. Bugs You Should Fix Yourself: A Triage Workflow for Exported Code
A practical triage workflow for telling apart the bugs Rork resolves on its own from the ones you should hand-fix in exported React Native/Expo code, with working examples.
Hardening API Calls in Rork Apps: Token Refresh, Retry, and Idempotency
The fetch Rork generates is left fragile against expired tokens, flaky signal, and double sends. Here is a design that consolidates token refresh, retry with backoff, and idempotency keys into a single client layer, with implementation code and operational numbers.
Rebuilding Rork's Generated Form Screens for Real Use: react-hook-form and zod
Rork's generated forms look fine on screen but fall apart on a real device: the whole screen re-renders on every keystroke, the keyboard hides the submit button, and slow networks invite double submits. Here is how I rebuild them with react-hook-form and zod, from an indie developer's point of view.
Logging Design for Rork Apps: What to Keep and How to Redact PII
Rork-generated apps tend to scatter console.log everywhere, and when a bug appears you cannot read the part that matters. This designs structured logging, log levels, automatic PII masking, and production send control — all with code you can use as-is.
When Rork-Built Lists Stutter: Designing Image Caching and Prefetch
A FlatList from Rork starts stuttering once the images pile up. Here is how I restore smoothness with expo-image caching, recyclingKey, prefetch, and a move to FlashList, with the device numbers I measured.
Adding a Minimal Test Safety Net to Rork-Generated Screens
You add one new screen to a Rork app, and a completely unrelated paywall check quietly breaks. This is how to bolt a minimal automated test safety net onto generated code with Jest and React Native Testing Library — protecting only the three places that hurt when they break.
Make ITMS-91053 Stop Catching Your Rork Max App — A Release-Proof Privacy Manifest Workflow
Fixing ITMS-91053 once doesn't keep it away — every new dependency can bring it back. Here's a field-tested workflow to audit your dependency tree, generate declarations, and catch the rejection locally before you upload.
Trimming App Size for Rork Max Apps: App Thinning and On-Demand Resources
Rork Max ships images and fonts straight into the bundle, so a generated SwiftUI app quietly grows heavy. Here is how I use App Thinning and On-Demand Resources to shrink the first download, with the device numbers I measured and a size budget you can run.
Before You Burn Out Hand-Testing Every Release: Automate Your Rork App's Critical Flows with Maestro
With Rork, a prompt that fixes one screen can quietly break another. Here is how I automate the revenue-critical path from launch to paywall using Maestro and run it in CI, including the spots where I got stuck as an indie developer.
A Custom Screen Appears When You Long-Press a Notification in a Rork Max App — Implementing a Notification Content Extension
How to add a Notification Content Extension to a Swift app generated by Rork Max so a custom UI is drawn only when the notification expands. Covers the split with the Service Extension, updating the in-notification UI from a button, sharing state via an App Group, and the order to check when nothing shows — all with working code.