EAS Update · Channel versus Branch

EAS Update · Channel versus Branch A data-flow diagram generated by Archify. 01 / Who has the app? 02 / Permanent address in build 03 / Movable update history 04 / Newest matching release Customer app · App Store / Play · 01 / Who has the app? · channel: production Customer app App Store / Play channel: production Tester app · internal preview · 01 / Who has the app? · channel: preview Tester app internal preview channel: preview production · CHANNEL · 02 / Permanent address in build · durable address production CHANNEL durable address preview · CHANNEL · 02 / Permanent address in build · durable address preview CHANNEL durable address stable-v1 · BRANCH · 03 / Movable update history · current history stable-v1 BRANCH current history candidate-v1 · BRANCH · 03 / Movable update history · tested history candidate-v1 BRANCH tested history Update #41 · Fix login copy · 04 / Newest matching release · iOS + Android Update #41 Fix login copy iOS + Android Update #42 · New trip filter · 04 / Newest matching release · iOS + Android Update #42 New trip filter iOS + Android asks for production channel baked into build asks for preview channel baked into build points here today server-side pointer points here for QA server-side pointer newest match platform + runtime match newest match platform + runtime match Legend primary data data flow

Channel = audience address

  • • production identifies customer builds
  • • preview identifies tester builds

Branch = update history

  • • stable-v1 and candidate-v1 each hold ordered releases
  • • A channel can be redirected to another branch

Platform is a compatibility filter

  • • The branch can hold an update group for iOS and Android
  • • Each device receives only its matching platform and runtime