What Tools Should Game Developers Have at Hand at all Times?
summary
Panel argues for concrete, cross-platform tools: network debugging with Wireshark, low-latency comms via Agora Spatial Audio, and content pipelines built on Unity plus Spine and Mixamo for animations. Teams automate CI/CD and use ClickUp/Figma mockups to lock scope; some ship monthly. Cautionary specifics: Cocos2d/engine choices yield performance wins but create dependency on vendor fixes, and iOS15 broke WebRTC audio — test platform updates before release. Standardized APIs and lighter 3D-creation tools remain missing.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:30Panel Introductions
- 3:35What Tools Should Game Developers Have
- 9:30Lesser Known Tools
- 14:29Machine Learning
- 15:05Updating Tools
- 16:45Changing Tools
- 17:55Using the Browser
- 19:50Current Toolkit
- 21:56Designing Creative Teams
- 23:46How to Make Creative People Work
- 25:11Everyone is Creative
- 25:55Creative vs Design
- 28:26Assets
- 29:09Other Tools
- 30:52Networking Tools
- 32:18Google Trends
- 33:21Audience Questions
- 34:09Whats Missing
- 35:21Standardization
- 37:15Creative challenge
- 37:52Publishing issue
- 38:56Outro
related talks
41mPanel: What Tools all Game Developers Should Have at Hand at all Times
36mWhich simple tips deliver the biggest value to developers
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
35mSuperstar Panel: Beyond The Code Live
44mDeveloper Tools Game-Changers That Will Save You Hours
45mTop 10 Unity Assets That Every Project Should Use
57mPanel 7: Testing and tooling
04mIntervista a Andy Touch