RORK LABJP
PLAY — Google Play's target API level 36 requirement took effect yesterday, August 31. From today, new apps and updates must target Android 16VISIBILITY — Apps still on API 35 stay listed but disappear for users on newer Android versions. No error is raised; new installs simply fade, which makes the change easy to missEXTENSION — If you missed the deadline, an extension through November 1, 2026 can be requested in Play Console — best filed alongside a concrete migration planAPPLE — On the Apple side, the event lands September 9 and iOS 27 is reported to ship September 14. Testing generated apps on iOS 27 hardware before release week is time well spentEXPO — Expo released expo-paste-input on August 28, a native module that brings image, GIF, and sticker paste to React Native TextInputEAS — EAS Observe reached general availability on August 20, putting crash and performance monitoring on the same EAS platform as builds and updatesPLAY — Google Play's target API level 36 requirement took effect yesterday, August 31. From today, new apps and updates must target Android 16VISIBILITY — Apps still on API 35 stay listed but disappear for users on newer Android versions. No error is raised; new installs simply fade, which makes the change easy to missEXTENSION — If you missed the deadline, an extension through November 1, 2026 can be requested in Play Console — best filed alongside a concrete migration planAPPLE — On the Apple side, the event lands September 9 and iOS 27 is reported to ship September 14. Testing generated apps on iOS 27 hardware before release week is time well spentEXPO — Expo released expo-paste-input on August 28, a native module that brings image, GIF, and sticker paste to React Native TextInputEAS — EAS Observe reached general availability on August 20, putting crash and performance monitoring on the same EAS platform as builds and updates
TAG

analytics

6 articles
Back to all tags
Related:
Rork3LTV3onboarding2retention2monetization2indie dev2Amplitude1React Native1event design1data quality1Expo1funnel analysis1
Rork Dev/2026-07-09Advanced

When Amplitude's Funnel Improved Overnight — Field Notes on Catching Event Schema Drift With a Self-Audit

In a Rork-built app, the Amplitude funnel showed signup-to-purchase conversion jumping from 8% to 19% overnight, yet revenue stayed flat. The cause was a property-name drift that inflated the count. Field notes on measuring the drift with an event contract and a runtime validator, then tightening it in stages.

Rork Dev/2026-06-03Advanced

Guarding Analytics Events With Types Across Six Rork Apps — A Shared Event Layer

After event names drifted across six apps and quietly broke my dashboards, I built a typed event registry and a thin wrapper to centralize tracking, plus a CI check that catches schema drift. Here is the design, with the code I actually use.

Business/2026-04-24Advanced

Maximizing Rork-Built App Revenue with App Store Connect's 100+ Metrics

A practical analytics workflow that narrows App Store Connect's 100+ metrics down to twelve revenue-critical signals, diagnoses funnel weaknesses, and pairs targeted Rork Max changes with Product Page Optimization A/B tests to grow ARPU, LTV, and retention.

Rork Dev/2026-04-24Advanced

Cut First-Day Drop-off by Half — A Data-Driven Onboarding Design Note for Rork Apps

How do you actually lower the 24-hour drop-off on a Rork-built app? This is a working solo developer's notes — measurement funnel, onboarding cuts I made, and the weekly cadence I use to iterate.

Business/2026-04-18Advanced

Why Subscription Apps Fail—and How to Build a Data-Driven Monetization System with Rork, RevenueCat, PostHog, and Superwall

A complete guide to integrating RevenueCat, PostHog, and Superwall into your Rork app to maximize subscription revenue. Includes production-ready code for churn prediction, paywall A/B testing, and personalized retention notifications.

Business/2026-04-11Advanced

Retention and LTV for Rork Apps — Separating the Two Numbers I Kept Confusing

Install retention and subscription retention use different denominators. Starting from the LTV miscalculation that came from mixing them, this walks through reading Day1/Day7/Day30 correctly, costing in generation credits, and catching churn signals early — from an indie developer's desk.