My point is nobody appears to have noticed a change in the rate of development in the work already done. You can't now turn around and say that's a problem when nobody ever said anything at the time. In fact we've had really positive feedback on the last few C3 releases.
Throughout the life of Construct, people often describe features as mandatory and try to frame the product as unusable without it. We know many people are passionate about what they want to see in Construct. But not everyone needs everything. Even simple and limited products have success on the market. It's even the case that C3 has long lists of major features that other products lack - and yet those other products still have large userbases. Remember that if you personally really need something, it does not necessarily mean the majority of other people using the product will also need the same. There's space on the market for a variety of different tools with different capabilities.
I think it's also worth bearing in mind that if you list 10 years worth of feature requests (which pretty much happened with the old feature request platform), it's not reasonable to expect quick action on that. Making quality software takes time. It's best to focus on a small number of things that are the highest priority, and then move on to the next highest priority things after those are done. Some feature requests are also literally never-ending. Things like "Make commercial-quality games in Construct" is both arguably already possible for certain types of games, and if expanded further probably amounts to "Make Construct as capable as Unity". That will be an ever-present request that can keep being repeated right up until Construct exceeds the capabilities of Unity, which as much as it's a nice dream will probably never happen. We all have to be realistic, and feature requests need to be framed in an achievable way otherwise there's no point even considering them.
As ever feature requests are a balancing act of trying to use limited resources to best effect. In the case of Construct Animate I think there is a chance we could see a much more significant return on investment than with any other work we could have done in that time. It is a bit of an experiment too, but I think there is very little chance it will either ruin the company or significantly impact C3 in any way. I'm still keen to hear actionable feedback on Construct Animate, so if you have any more, let us know!