Succeed by Failing – A Game Dev’s Journey Into a Mobile Dev Ops Tool Chain
summary
Covers a real mobile devops pipeline: Backtrace ingests SDK crashes, fingerprints 2,180 identical occurrences and claims up to a 70% cut in mean time to detection and resolution. Shows integrations to Jira and Slack, video recordings of user sessions, and a Unity/Unreal-friendly attribute payload (300+ fields) that stays queryable for 90 days. Practical tips include capping frame rate (60 FPS), preferring SVG/vector UI, using Gauntlet automation and CI/CD, and a free dev tier with 25,000 errors free.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:04Who is the speaker and what to expect
- 2:27Sauce Labs vision
- 3:30From banking to games
- 4:55Learning from failure
- 6:17Common mobile game failures
- 7:41Poor UX impact
- 8:23Failing right with DevOps
- 10:06Backtrace features
- 11:30Advanced data capture
- 13:15Pro tips for efficiency
- 15:04Failing often and gracefully
- 16:30Unreal upgrades
- 17:32Indie marketing
- 18:14DevOps future
- 19:39Success in game dev
- 20:43Closing and showcase
related talks
23mMobile App Crashes in Production: Lessons Learned from a Tester’s Viewpoint
50mDeveloper Experience in Mobile GameDev: How We Rebuilt a Plane in Flight
38mA Game of Testing
24mMastering the mobile testing pyramid
23mWhy testing is also a developer's problem
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
30mTesting Mobile Web Apps on Real Devices: How Fortune 100 companies do it
45mBuilding Tools to Free up Exploratory Testers