Hacker News Reader

Which is a good indication that the organization actually has no idea what the heck is going into the update.

Assuming there are good rollout and incident review processes in place, this isn't much of a problem in practice.

If you're shipping a mobile app with client side code (so, nearly all of them), there is no good rollout process.

You can't ship a quick update with Apple, because review isn't quick. Users who upgraded soon after release will be stuck with something broken until the new version is available.

You can usually ship quickly with Google, but users are slow to upgrade, but may have caught your first one, and not get your second one for some time.

I'm talking about feature flag based rollouts, which don't involve going through Apple or Google.

Hope you didn't mess up your flag system. Or your feature flagged feature doesn't corrupt your locally stored state.

Yeah it happens sometimes. It sucks. It's where incident reviews come in, and feature flags are still better on balance for many apps.

Reply on news.ycombinator.com