PANEL: RELEASES
A one-line bug fix in a published app used to mean a new store build and days of review. This panel publishes the current state as an update instead: installed phones pick it up on their next launch. It needs an Expo account and one EAS build to land on.
UPDATE VS BUILDAn update carries JavaScript — screens, texts, logic. It cannot carry a change to the app’s native side (a new permission, a new native module). The panel checks this before you press the button and says which of the two you are looking at, because publishing an update that can never arrive looks exactly like success.
CHANNELWhich group of installed apps an update goes to — a production channel and a test channel are different audiences. Each channel shows what is live on it right now.
MANDATORYAn update is normally offered; a mandatory one is applied on the next launch without asking. Keep it for something people cannot wait for, like a data-losing bug.
BRING BACKA published update that turned out bad is undone by republishing an earlier release from the list — no store round trip.
SEND TO TESTERSEvery build in the list carries the way to get it onto someone else’s phone: a direct install link, or the TestFlight / Play internal-test route for store-signed builds.
Both stores allow updates like this, but not ones that change what the app is for. Keep the purpose the same.