All Articles
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.
Shipping Wallpaper Packs Without an App Review — Versioning and Delta Delivery for Remote Assets Across Six Apps
Re-submitting your app every time you add ten wallpapers grinds operations to a halt. Here is a manifest-based versioning scheme with delta downloads, cache invalidation, and rollback — with the implementation and measured transfer savings from running six apps in parallel.
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.
Keeping a Rork-Built Expo App Ready for Kotlin Migration — Design Notes After Android Studio's Migration Agent Announcement
Android Studio's new agent can migrate React Native apps to native Kotlin. Here is how I restructured a Rork-built Expo app to stay migration-ready: a native dependency audit script, a portable core layer pattern, and a readiness checklist.
When and How to Remove Features Nobody Uses — Auditing and Safely Retiring Functionality in Rork-Built Apps
Unused features quietly make an app harder to maintain. A field-tested playbook from running six wallpaper apps in parallel — how to measure feature usage, decide what to retire, and remove functionality in three safe stages with Remote Config.
When Hiragana Doesn't Match Katakana — Japanese-Aware In-App Search for Rork Apps
A hiragana query silently missing katakana titles is a UX failure users never report. How I fixed Japanese search in my wallpaper app with NFKC normalization, kana folding, and precomputed search keys.
A Three-Layer AI Cost Design for Rork Apps After Apple Opened Foundation Models to Small Developers
Apple now offers Foundation Models on Private Cloud Compute at no charge for developers under two million first downloads. Here is a three-layer cost architecture for Rork apps, with a simulation script and working bridge code.
Keeping Manual Fixes Alive Across Rork Regenerations — Boundary Design for AI-Owned Code
A tiny copy-change request quietly reverted my week-old ATT fix. Here is the boundary architecture I use now: a guarded directory, one-line adapters, patch assets, and scoped prompts — with measured blast-radius numbers.