I do agree they should consider a third C2 programmer, as the backlog keeps stacking. But they are doing more than the best they can. So the problem is C2 is entirely html 5 based, and that is built on internet browsing. If their was a way to export to a better framework for mobile like lua or c++, but that seems intensely complicated. I wander how unity handles it so well...
Unity, if I recall correctly, has 1000+ employees, along with major game industry agreements and joint ventures. It's a completely different world.
While C2 is the single greatest 2D html5 gamemaking software, it would of course be nice to turn that title into "the single greatest 2D gamemaking [and application .. 
] software." While it may already be enroute to holding that title, and perhaps already does in terms of ease of use and accessibility (and perhaps developer enjoyment), I agree that an additional C2 developer would be a tremendous resource. Actually, I think that Ashley, Tom, and Paulo would benefit most with the addition of 2 developers; one to help with general development, and another to focus on native exporters. Ashley already wrote a blog entry detailing how C2's design allows for new exporters to be built in without having to touch the editor. Unfortunately, he also has already made clear that the financial resources simply aren't there, for now, to bring new members on board.
There are two important aspects to keep in mind when considering this perspective. One, adding new members to the Scirra team could drastically change both the atmosphere enjoyed by Tom and Ashley, as well as the relatively intimate relationship that we customers enjoy. They are two brothers working together on a software that they love. Adding new developers could really change their business environment.
Two, to some extent, there are already many developers working with Tom and Ashley to build new exporters for C2, as well as a community that is uncannily apt towards expanding the software themselves. This is something I feel is special about Scirra and C2, and I'm not sure that risking a change for the sake of more rapid expansion is really the right answer.
That being said, it would be really awesome to have additional native exporters built for C2. But my guess is that this won't occur until the software is fully matured, such that such a tool wouldn't require constant modification with each new release. A shame for us and them, perhaps, but with so much already here for us, and new things coming out each week, its probably still much more than what you hoped for, but not yet what you dream of.