Which simple tips deliver the biggest value to developers
summary
Says don’t build your own engine: pick Unity or whatever fits the team, plus Photoshop/Adobe XD for art and mockups. Set up source control and CI (Jenkins or TeamCity) so there’s a one-button build to put builds on devices. Use pencil, whiteboards and rapid playtests with real people for feedback, add UX early, and treat qualitative research as data. Outsource only well-scoped tasks. Invest in community-managed localization and negotiation advice; don't build your own engine unless that is the product.
AI-written summary · about
chapters (13)
- 0:00Introduction and panel setup
- 1:25Panelist introductions
- 2:54Starting a studio from scratch
- 7:31Game engine and tool choices
- 9:16Self-publishing vs. working with publishers
- 12:07Expanding to Asian markets
- 15:37Hiring and team structure tips
- 18:10Changes in game development processes
- 23:52Community engagement and player feedback
- 24:35Development process best practices
- 27:27Data-driven development and UX
- 30:59Outsourcing strategies and pitfalls
- 35:11Board governance and hiring models
related talks
14mThere Aren't Problems, Only Solutions
40mWhat Tools Should Game Developers Have at Hand at all Times?
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
01h 05mFive Game Developer Habits That Help Software Engineers
57mHard truths and soft skills: 10 pieces of advice for novice game devs
19mTechnical indie game developer tips for starting your framework early
31mThings I Wish I Knew When I Started Playing 'Developer'
56mPunching Above Your Weight