◉RORK LABJP
●SDK58 — The Expo SDK 58 beta is open. It ships the React Native 0.88 release candidate, and the beta period is stated as three to four weeks●11/01 — For anyone who requested an extension, Google Play's target API deadline lands on November 1. Forty-four days out●EASENV — A long-open report: secrets handed to a local build arrive as the literal variable name rather than its value, and the damage surfaces much later●NEW — The replacement the table recommended had already shut down. A record of reconciling all 74 rows of the deprecation list●UISCENE — iOS 27 requires the new scene lifecycle. SDK 57 makes it something you opt into; it only becomes the default in 58●CREDIT — What "AI errors don't cost credits" actually covers becomes clear once you record a day of asking for the same fix more than once●SDK58 — The Expo SDK 58 beta is open. It ships the React Native 0.88 release candidate, and the beta period is stated as three to four weeks●11/01 — For anyone who requested an extension, Google Play's target API deadline lands on November 1. Forty-four days out●EASENV — A long-open report: secrets handed to a local build arrive as the literal variable name rather than its value, and the damage surfaces much later●NEW — The replacement the table recommended had already shut down. A record of reconciling all 74 rows of the deprecation list●UISCENE — iOS 27 requires the new scene lifecycle. SDK 57 makes it something you opt into; it only becomes the default in 58●CREDIT — What "AI errors don't cost credits" actually covers becomes clear once you record a day of asking for the same fix more than once
TAG

Solo Dev

4 articles
← Back to all tags
Related:
Rork4Push Notifications1Expo1Retention1App Store1App Operations1Monetization1UX Design1Networking1Error Handling1Long-term operations1Maintenance design1
⬡ Rork Dev/2026-06-14Intermediate

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.

⟐ Business/2026-04-27Advanced

Taking a Rork App From 'Working' to 'Ready to Sell on the Store'

The finishing workflow that takes a Rork-generated app from 'it runs' to 'it actually sells on the store'. Ten checkpoints I learned the hard way running solo apps for over a decade.

⬡ Rork Dev/2026-04-23Advanced

Designing Rork Apps That Don't Let Users Down on Bad-Signal Days — UX Patterns for Unstable Networks

After shipping a Rork app, the #1 reason I was losing review stars wasn't a crash — it was 'the screen just stays blank.' Here's how I redesign loading, empty, and error states so the experience gracefully degrades on flaky connections.

⬡ Rork Dev/2026-04-22Advanced

Keeping a Rork-Built Solo App Alive Past Year Three — A Maintenance Design Against Silent App Aging

When you run a Rork-built app over the long haul, a kind of 'aging' starts creeping in that wasn't visible at launch — OS updates, breaking library changes, shifting device landscapes. After more than a decade of independent app development and two years of running Rork apps, here are the maintenance design principles I rely on to keep apps stable past year three.