Development with technical support from the King team

What the talk is about

O. Prydiuk and A. Hulev talk about working with the Defold engine from two angles: the King technical support side and that of independent developers. The first part covers the process: a new build roughly every two weeks, upgrades meant to be painless, support through an open forum, and engine development driven first of all by the needs of King's games. They also mention cloud-built extensions and custom engine builds without unused libraries. The second part is about shipping a game: King's indie contest, six teams sent to a major San Francisco conference, how those teams fared, and the authors' own paid puzzle game, which got featured but converted poorly into installs. The takeaway: making a game is easier than reaching the market, so listen to feedback and prototype early. Useful for indie teams and anyone choosing an engine.