Stop Burning Your One Push-Permission Shot on App Launch — Pre-Prompt Priming for Rork Apps
If your Rork (Expo) app fires the OS push-permission dialog at launch, every 'Don't Allow' tap closes that channel forever — iOS won't let you ask again. Here's how a self-built pre-permission screen lifts your opt-in rate, with the Expo code to do it.
Actually Delivering 'It Updates Without Opening' in Expo — A Realistic Background Task Design
Building 'content refreshes every morning' into a Rork-generated Expo app runs into iOS background execution being far less dutiful than you expect. Here is a minimal expo-background-task setup plus a design that doesn't break when the task never runs.
Calling Apple Foundation Models from a Rork (Expo) App: Bridging On-Device AI Through a Native Module
Rork generates Expo (React Native) apps, but Apple Foundation Models ships as a Swift framework you can't touch from JavaScript. Here's how to write an Expo Modules API bridge, gate it by availability, and fall back to the cloud on unsupported devices.
Building Rork Subscriptions Around RevenueCat Entitlements — Access Checks, Offering-Driven Paywalls, and Restore
Implementation notes for adding subscriptions to a Rork (Expo) app with RevenueCat. Make Entitlements the single source of truth for access, drive the paywall from Offerings so you can change prices remotely, wire up restore and the customer-info listener, and avoid the sandbox traps — all with working code.
When Your Rork App Gets ITMS-91053 — A Practical Guide to Privacy Manifests and Required Reason APIs
Submitting a Rork-generated Expo app to the App Store can trigger Privacy Manifest warnings even when you never wrote the offending code. Here is how to clear both Required Reason API and SDK manifest issues before you submit.
Win Back Lapsed Users with App Store In-App Events — Deep Link Implementation for Rork (Expo) Apps
An implementation memo on bringing lapsed users back to a Rork (Expo) app using App Store in-app events. Covers event card design, universal link routing, and measurement, from a solo developer's operational view.
After WWDC26, Reselecting What an Indie Should Build Right Now
Now that on-device AI is free for small developers, the premises of app planning have quietly shifted. Here are five questions to choose what to build with Rork at the concept stage.
Routing inference on-device first and escaping to the cloud only when it's worth it, in a Rork app
Build a tiered, fallback-based inference router in a Rork (Expo) app: cache to on-device to Private Cloud Compute to a remote API (Claude/Gemini). Working TypeScript covering budgets, timeouts, caching, and image routing.
Designing Empty States Properly in Your Rork App — First Run, After Deletion, and Network Errors in One Component
When you build an app from a prompt in Rork, only the data-filled screens tend to look polished. Here is how to build the first-run, post-deletion, and network-error empty states into one reusable component, with retry logic, screen-reader support, and effectiveness measurement.
You Only Get to Ask Once — Implementing a Notification Soft-Ask in Your Rork App to Lift Opt-In
On iOS, once a user denies the notification prompt you can never show it again. In a Rork (Expo) app, instead of firing the system prompt on launch, we add our own soft-ask screen and only request permission once the value has landed. Built with expo-notifications, covering Android 13 POST_NOTIFICATIONS, a recovery path after denial, and opt-in measurement.
Design the Exit Before You Commit to a No-Code Mobile Platform
When you build an app business on a no-code tool, the first thing to plan is not the features but whether you can ever leave. Here is how to weigh lock-in risk for Rork and Rork Max from a portability standpoint.
Raising Your Subscription Price: How to Handle Existing Subscribers on the App Store and Google Play
Raise your subscription price without losing existing subscribers: break-even churn math, store consent flows, PRICE_INCREASE and EXPIRED handling, and cohort tracking.