We will get to everything eventually, the only question is the order we do them in. When deciding the order we have to weigh in a lot of factors, and it's not as simple as it might seem. For example I think a big part of the appeal of Wii U support is proving Construct 2 is a professional, console-grade middleware tool. This could do a lot to shift the perception of "it's just a toy" that we see still see and presumably lose sales from. Not to mention that if you want to publish to Wii U it's a pretty big deal! And everyone who uses Construct 2 is after something different, so even when we do add major new features there will be some people who would have preferred something else. Not much we can do about that. Hopefully multiplayer - which is in the works and should be awesome! - is a big feature that everyone will appreciate.
Don't get hung up on speech recognition, it probably took about an hour in total. Chrome was adding support, and we added a few actions and conditions to expose it to the user media object because it's kind of cool. It's not like we slaved over it for weeks and put off other features because of it.
The real problem is I think our userbase has grown to the point where as a small team we simply can't keep up with what we get asked for. For a long time now we've been getting new feature requests, suggestions and ideas faster than we can actually implement them, not even including our own internal ideas and plans. This is kind of a nice problem for us to have, but we still need to solve it, and we need to do that by growing the team. We've been looking in to hiring for a while now, but it's difficult and involves many new problems and logistical challenges. I am very keen to expand this year. Until then, we're doing our best and will keep the approximately weekly updates coming.