Topic

Shipping without a release

Feature flags, remote config, OTA updates and store rules: the ways to change a live app without a release, and what each one can't do.

6 posts

Start with

Staged releases, flags, remote config, OTA, server-driven UI, a CMS, WebViews and API changes: what each can change, what it can't, and how to pick.

What App Review says about screens from a server
Apple's rules name downloaded code and hidden features, not server-drawn screens. What the text says, what to tell reviewers, and what we'd never do.
The hidden cost of waiting for an app release
Waiting for a release costs more than the days on the calendar. A way to price the wait with your own numbers, and which changes are worth moving.
App Store phased release: what it does and doesn't
Apple's phased release spreads an update over seven days and can be paused. It can't recall installs, cover the web, or change shipped content.
Deploy is not release: split them on purpose
Merging code and showing it to users are two decisions. How splitting them lowers risk, and what it costs in flags to clean up later.
Feature flags vs remote config vs CMS: three questions
A flag decides who sees what, remote config sets a value, a CMS holds content other people edit. How to tell them apart, and how each gets misused.
Ways to change a live app without shipping a release
Staged releases, flags, remote config, OTA, server-driven UI, a CMS, WebViews and API changes: what each can change, what it can't, and how to pick.