Release management for app developers

Usability sessions first, then a redesign built around versions

March to July 2026

  • Handed off
  • Full version is private
Role
Design lead for app release management
What it is
A redesign of how developers release new versions of their apps
Result
Four sessions gave one critical and four high findings, and the redesign was built from them.
App versionsVersion 3BetaVersion 2ReleasedVersion 1ReleasedOptional beta pathRelease as a betaRelease to everyone!Clear warning onthe risky routeApp versionsVersion 3BetaVersion 2ReleasedVersion 1ReleasedOptional beta pathRelease as a betaRelease to everyone!Clear warning onthe risky route
Redrawn as generic boxes, not the real screens. The list starts from the version and its state. From the newest version, a beta is a choice, and the risky route carries a clear warning.

I led design for how developers release new versions of their apps, with a product manager and engineers. I ran usability sessions first. Four sessions gave one critical and four high findings, and the redesign was built from them.

Four usabilitysessionsOne critical andfour high findingsVersioned betasVersion-first viewOptional beta pathFour usability sessionsOne critical and four high findingsVersioned betasVersion-first viewOptional beta path
The order of the work: sessions first, then findings, then the redesign. Each step is one box.

What changed

  • Versioned betas. A beta belongs to a version of the app.
  • A version-first view. The screen starts from the version, for people who don’t think of themselves as developers.
  • An optional beta path. A developer can release through a beta, and the risky route carries a clear warning.

My part

I owned or contributed to the Figma frames that engineering built from. I also wrote a short note on what “release” should mean when an agent, not a person, ships the update. I handed the work off in July when I changed teams.

The full version is on a private page. Ask me for access.