All Articles
Reading Steps and Sleep into Your Rork Max Native App — HealthKit for Calm, Number-Light Wellness Apps
A walkthrough of adding HealthKit to the native Swift app Rork Max generates: reading steps, sleep, and heart rate, writing mindful sessions, and handling background delivery — including the App Store review wording and the production-only 'permission granted but zero data' trap.
Updating Live Activities Remotely: Putting Live Lock Screen Info on a Rork App
A practical design for updating Live Activities remotely through APNs so the Lock Screen and Dynamic Island stay current even when your app is closed. Covers push-to-start vs update tokens, the content-state payload, stale-date and the update budget, and bridging from Expo, with working code and the issues I hit in production.
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.
Getting to the Real Revenue Number — A Pipeline that Reconciles AdMob, App Store, Google Play, and Stripe
Dashboard revenue and the money that actually lands in your account do not match. Here is an aggregation pipeline that absorbs currency, timezone, and the gap between estimated and finalized figures across four revenue sources — with the implementation and operating judgment from running six apps.
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.
Before Your Feature Flags Turn Into a Junkyard — Governing Naming, Staged Rollout, and Kill Switches Across Six Apps
Keep adding remote-config flags and within six months you have keys nobody remembers the meaning of. Here is a governance system — naming conventions, safe defaults, staged rollout, kill switches, and monthly cleanup — with the implementation from running six apps in parallel.
Choose Native Features by Retention Impact, Not by Checklist
Rork Max can generate widgets, Live Activities, and Core ML alike. But 'can build' and 'should build' are different things. Here is how to decide native-feature adoption by its effect on retention.
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.