Transparency and trust in working with a publisher
summary
Clear rules on contracts and process matter most for trust: define prototype: levels SDKs visual quality so payment triggers are unambiguous, require evidence a publisher can fund offers and a concrete plan to publish rather than endless prototyping, demand access to data and tools such as must share dashboard KPIs for every test, expect publishers to disclose which internal teams and KPIs will support a project, accept they may withhold UA/creative formulas as competitive IP, and treat silence on major issues or missing documentation as a red flag.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:59Introduction to the topic
- 2:55Transparency in publishing
- 3:52Legal terms
- 5:27Financial Deal
- 7:32Processes
- 10:08Knowledge
- 14:01Force major
- 17:07Summing up
- 18:30How to contribute to trust
related talks
59mThe modern days publishers, building a unique developer/publisher relationship
56mMoney Talks - Publishing and Investment
27mGoing Self-publishing vs with Publisher.
52mDeveloper vs Publisher 3, 2, 1, Go!
59mShaking Up Publishing For Living Games
54mMoney Talks - Publishing and Investment
54mMoney Talks
30mWorking with Independent Developers: Lessons Learned Over the Years