iOS Publishing MVC
Problem to solve
Once code signing is set up (#57519), getting TestFlight working is pretty easy. We can make this even easier by potentially offering a composable template or at least in-product guidance on how to get this up and running quickly with FastLane. Once working this can be used to do cool things like edit a iOS app on your iPad, then automatically get a TestFlight delivered app back to your same iPad and test it right there. Then, you can promote this to a release. Let's make this workflow easy and obvious for our iOS developers.
- Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha /label Persona: Software developer
This should require minimal code changes. This could be as simple as "We notice you are building an iOS app. Would you like to read the docs on setting up TestFlight/App Store Updates?" but can also be more. Needs UX analysis.
What does success look like, and how can we measure that?
More users publishing with iOS