Developer Experience in Mobile GameDev: How We Rebuilt a Plane in Flight
summary
Playrix rebuilds developer experience with a concrete 10‑step plan that creates a green master (100% green target) enforced by nightly bundles and a pessimistic “broken from last success” uptime metric; targets include local builds under one minute and PR bundle checks around one hour. A winsorized mean for build time handles long‑tail noise. A RAG + LLM knowledge pipeline unifies docs into a vector DB with feedback buttons; Copilot is piloted for coding help. Team leads run dashboards, platform team escalates and provides tools.
AI-written summary · about
chapters (15)
- 0:00Introduction to Playrix
- 1:07Engineering at Playrix
- 5:28Defining developer experience
- 6:58Importance of satisfaction
- 9:17Productivity metrics
- 12:49DX framework dimensions
- 17:42Optimizing feedback loops
- 24:00Measuring development progress
- 29:16Choosing the right measure
- 33:58Feedback loop improvements
- 36:15Reducing cognitive load
- 42:02Maintaining flow state
- 43:20Improvement pipeline
- 45:14Metrics frameworks overview
- 48:51Future goals
related talks
21mSucceed by Failing – A Game Dev’s Journey Into a Mobile Dev Ops Tool Chain
27mHow to Make Your RnD Rock!
18mRapid prototyping for mobile games development
34mFrom Developer Experience to Business Value
27mDeveloper Experience: It’s Time to Start Complaining
18mGram Games on iterating your development pipeline as you grow
38mIterative Mobile Development
47mDesigning the Developer Experience