There has recently been an increase in the number of feature request posts. I think it’s great and it’s a sign that a lot Defold users are actively using Defold to create games and while doing so they come across things that are missing or could be improved. This is really one of the major reasons for releasing Defold to the public. We need and we want your feedback to make Defold an even greater product than it already is. The potentially negative thing about this increase in feature requests is one of quality and bandwidth:
For any area of the Defold engine you can probably come up with a hundred different improvements, small and big, critical and unimportant, and it is highly unlikely that all of them would ever be implemented. Not only would it bloat the engine and the APIs (which is something we take very seriously) but it would also require a huge team of developers. And to be honest, that is a team which we don’t have and which we don’t want either. We have a fairly small team of hugely skilled and motivated engine and editor developers and I am constantly amazed by the amount of things and the quality of what we deliver!
Additionally I think it is important to know a little bit about how the engine team is working. The team is working in two week iterations (or sprints as we call them) and plan their work in these two week chunks. Before the beginning of each sprint we have a planning and estimation meeting where new things in the backlog are given a priority and an estimate (and as you might already know, things are added to the backlog as a result of feature request made here on the forum, by teams within King and through meetings that @Oleg_The_Evangelist and others have with our users at game jams and conferences). Bugs and missing features without reasonable workarounds that block teams from delivering great games will be given a higher priority than issues and features with workarounds or things that are only “nice to have”. Based on the estimates and the given priorities of the things in the backlog a certain number of tasks are planned for the coming two weeks. We also keep a list of smaller tasks and “quick wins” that team members can pick up in-between the planned tasks if time permits. This ensures that smaller and perhaps minor things get done as well. Finally, at the end of each sprint we do a new release of the engine and the whole process begins again.
So why am I writing all of this? What I’m trying to convey is some kind of expectation management. I can promise you that we will consider each and every feature request that is posted here on the forum and we will assign those that make sense a ticket in our backlog. What I cannot promise you is that we will be able to deliver all of the requested features at once (or ever), for reasons described above. I hope this makes sense to you and that it gives you a little bit more information about the process involved when making a feature request here on the forum.