Should You Show a Read More Link? Let the Rendered Text Decide in Rork (Expo)
Clamping a product description to three lines and adding a Read more toggle sounds simple, until the toggle also appears under single-line text. This walks through measuring the real line count with onTextLayout so the toggle only shows when text actually overflows, covering iOS vs Android quirks, expand animation, and font scaling.
Adding Home-Screen Quick Actions to a Rork App — dynamic items without cold-launch drops
How to implement the long-press quick actions on a Rork (Expo) app icon. Covers static vs dynamic items, the iOS/Android differences, and the cold-launch problem where the action arrives before the router is ready — solved with a hold-and-replay design.
Previewing Files In-App in Rork — calling Quick Look safely from Expo
How to preview PDFs, images, and Office documents in place without sending users out of your app, using Quick Look (QLPreviewController) from Rork (Expo). Covers pre-downloading remote files, the local-URL requirement, the Android FileProvider alternative, and handling the share button.
Adding App Store Promoted In-App Purchases to a Rork App
How to list purchases on your App Store product page and carry a buyer straight into your in-app purchase flow. Covers receiving deferred purchases that arrive before the app is launched or the user is signed in, with implementation for both react-native-iap and StoreKit 2.
Design On-Device Core ML So Cold Start and Heat Don't Break It
Put on-device Core ML in the native Swift that Rork Max generates and you hit two walls before accuracy: the first inference is slow, and the device heats up and slows down. Here is a design built around cold start and a thermal budget, with working Swift.
Write to NFC Tags with Rork Max: Add a Step Beyond Read-Only
The NFC apps Rork Max generates usually start with reading. But the experience really changes when you add writing. Here is how to write NDEF to a tag with CoreNFC, plus the pitfalls you can only catch on a real device.
Ship EAS Updates to a Few First, and Halt Automatically on Crash Rate
Because OTA updates reach everyone instantly, a bad update reaches everyone instantly too. Here is a three-layer design: ship EAS Update to a small canary, decide expand-or-halt from crash-free rate automatically, and hold a safety net on the device — with working code.
Build Your Settings Screen From One Schema and Reuse It Across Apps
Hand-building a settings screen per app falls apart as your app count grows. Here is a schema-driven design that assembles the screen from declarative data and shares a common base across multiple apps, with working code.
Monetizing a Rork-Built App — Choosing Between Ads, Subscriptions, and Freemium
How to monetize an app built with Rork — from choosing between ads, subscriptions, freemium, and one-time purchase to the implementation details. Phased AdMob formats, treating ad-free as a single source of truth, and price anchoring, written from the indie-developer trenches.
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.
Designing Rork Max Iterations So You Don't Burn Through Credits
Rork Max generates native Swift for you, but regenerating on impulse drains credits astonishingly fast. Estimate how many regenerations each screen will take, separate structural prompts from polish prompts, and draw a clear line for what to hand-edit instead. From an indie developer who ships to the store, here's how to treat credits as a budget.
Retrofitting Offline-First Into a Rork App: Persistent Cache and a Write Queue
Reviews kept saying the app was blank on the subway. Polishing error screens was not enough, so I retrofitted TanStack Query persistence and an offline write queue into a Rork-generated Expo app. Optimistic updates, reconnect flushing, and keeping the layer safe from regeneration are all covered with code.