The team behind Tramline has spent a decade working on: 1/ some of the biggest mobile apps in India and SE Asia, and 2/ backend and API systems to support many of those same apps. It is clear to us that the status quo of release engineering for mobile apps is nowhere close to what backend and frontend web engineers are used to. Mobile teams work within the constraints of not just mobile devices, but also the rules of App Store and Play Store and the kind of release engineering they enable.
For mobile teams at scale, workflows on a CI server simply aren't enough to release updates to the stores with confidence. Teams need to coordinate across multiple kinds of systems (app stores, CI servers, internal/external build distribution systems, observability platforms) which means that a mobile app's release cycle touches all these systems. Elite mobile teams at places like Facebook [1] and Shopify [2] have been working on these areas for years.
With Tramline, teams can codify their mobile release cycle across different systems, and rely on a central dashboard to manage their releases. Check out our 4-minute overview video! [3]
Excited to get some feedback and answer any questions! Or if you prefer email, we're at hello at tramline.app.
-- Pratul (me!) and Akshay and Nivedita
[1]: https://research.facebook.com/publications/continuous-deploy...
[2]: https://shopify.engineering/mobile-release-engineering-scale...
[3]: https://www.loom.com/share/d30cc0e0ec8e42cfb0f7d7c88443fc41
No comments yet.
