Pitfalls of developing 2D games on the Unity engine

What the talk is about

Mykola Komarov explains how a team that produces HOP games (linear interactive quests) on a pipeline, with many projects in parallel, moved from its in-house engine to Unity, and why it ended up mostly disappointed. The key idea is that programmers should build tools so designers and artists can quickly change any part of a game at any time. He checks his expectations of Unity — cross-platform support, the animator, documentation, community and support, the Asset Store, editor extensions, C# — against reality: the real gain came mostly from C#. Problems included imprecise documentation, bugs left unfixed for a long time, weak plugins and an awkward way of writing editor GUI. He stresses that for prototypes, indie teams and beginners Unity is a good choice. Useful for developers choosing an engine and shaping a pipeline.