What Renovate may bump in an Expo app, and what it must never touch
Turning on automated dependency updates in a Rork-generated app also hands Renovate the 123 packages Expo SDK 57 pins. Measured on 2026-07-30, six of them sit a full major version behind npm latest. Here is how to generate the ignore list from the SDK instead of maintaining it by hand.
When to Raise Your Minimum iOS Version — Count Leftover Branches, Not User Percentages
Judging a minimum OS bump by usage share produces the same answer every year, so the decision never happens. Here is the annotation convention, the sweep script that counts how many iOS and Android branches each candidate floor would retire, and what to watch for 30 days after.
Two Weeks of Maintenance After v2.1.0 — Running Crashlytics Triage Through Claude in Chrome
Notes from operating Beautiful 4K/HDR Wallpapers v2.1.0 and Ukiyo-e Wallpapers v1.8.0 through phased rollout. Defensive RecyclerView copies, Glide desugaring, drawable-nodpi placement, and what I now hand off to Claude in Chrome every morning.
Building Your Second Rork App: How Much of the First One Should You Reuse?
Once your first app ships, the temptation is to clone it whole and swap the contents. But what you reuse and what you rebuild quietly decides how heavy your maintenance becomes. A look at where to draw the reuse line, from running several apps in parallel.
Catch Silent Deprecations Before the Next OS Update Breaks Your Rork App
Apple and Google deprecate APIs every year, and your app breaks the morning after. Build the watchdog: a four-layer monitoring setup with concrete CI scripts that catches Required Reason APIs, missing Privacy Manifests, targetSdkVersion shifts, and Expo SDK signals before submission fails.
What Changes After You Launch a Rork App — The Reality of Maintaining What AI Built
Lessons from shipping a Rork-built app on the App Store and watching real users interact with it. Where AI code generation shines, where it falls short, and what you'll need to add yourself.