Publishing, Partnership & Problems
summary
Claim: early small UA tests are often misleading — one prototype showed great KPIs then collapsed at scale, another tested well until a slower, cautious publisher lost the deal to a rival. Practical tools: run many small tests across publishers, push for repeat tests after reworks, and demand technical checks (SDKs, adapters, QA). Surprising numbers: first-stage KPIs frequently don’t predict large-scale CPI or retention. Contract realities: the deal includes partners (localisation, ops) and producers — ask for producer meeting and share test results up front.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:43Publishing Problems
- 2:19First Impression
- 3:24Imperfect Communication
- 4:08Naive Optimism
- 5:10Recommendations
- 6:31Testing
- 10:32Communication
- 11:20Personal Affection
- 12:36Shared Vision
- 13:56Routine
- 15:19Mistakes
- 16:36Partnership
- 19:39Priorities
- 21:25Success
- 22:51Failure
- 23:35Conclusion
related talks
52mGetting a Publisher vs. Self-publishing
41mBest practices in testing with new partners
16mPublishing 101: A crash course in navigating today’s mobile marketplace
30mSuperstar Session: Publishing Isn’t ‘One Size Fits All’ - What Does Your Game Need?
45mPanel: What Are Publishers For? Getting the Most Out of Your Publishing Deals.
21mWhen a platform isn’t enough: Building an experimentation culture
20mFrom Prototype to Stardom Early Stage UA Tactics for New Game Prototypes
17mShow impact on Company's topline by testing using KPI they understand