October 2026 Summaries

No summary generated yet.

Mike Khristo argues that sustainable app growth comes from interconnected feedback loops rather than isolated funnel stages, where outputs such as retention, reviews, user-generated content, and installs improve the inputs for future growth. He identifies three practical loops for most apps: store visibility driven by installs and quality signals, content production guided by successful posts, and social proof created through product usage and reviews. The effectiveness of these loops depends on rapid cycle times and minimizing manual handoffs between disconnected tools, since delays can cause opportunities and platform trends to expire. Drawing a parallel with how Expo’s EAS simplified cross-platform app deployment, Khristo presents Layers as an effort to reduce growth-stack handoffs by using richer context from an app’s codebase, store listing, and usage data. He advises developers to map their existing loops, measure the duration of each stage, eliminate inefficient copy-paste tasks, and reuse fresh materials such as changelogs and support conversations for marketing and store optimization.

Live Activities can provide real-time, glanceable progress for background tasks such as receipt processing by showing stages like received, processing, completed, or failed on the iPhone Lock Screen and Dynamic Island without reopening the app. The implementation described uses Expo and expo-widgets to define a fixed ActivityKit content-state schema and render native SwiftUI widget views from TSX, while supporting remote push-to-start on iOS 17.2 or later and graceful fallback on unsupported devices. Because Live Activity push tokens are per activity, can rotate, and differ from ordinary device tokens, the client must register them with the backend through both existing activity handles and a module-level listener for remotely started activities while the app remains backgrounded. The backend stores start and update tokens, maps changing domain events to the widget’s schema, sends APNs pushes to start and update activities across a user’s devices, recomputes state from the database to avoid race-condition errors, and removes invalid tokens. Important APNs details include required Live Activity headers, correctly wrapped and serialized content state, mandatory start-event attributes and alert data, matching the APNs environment to app entitlements, and preserving terminal states with update events rather than immediately ending the activity.