i personally believe that the exporter for the Nintendo is a good step forward on the right direction.
why the right direction?
although i understand that only a few people will ever use it because of the high cost, it does give the option to a small company to produce something in a true gaming environment with known hardware ,controller and capabilities and of course the fact that 100% who bought the console are potential buyers.
my biggest concern right now with mobiles is exactly this problem. hundreds variations of speed ,screen ,input,size etc.
although i am not a programmer i believe that creating an exporter for fixed hardware with a lifespan of over 7 years is easier to achieve than mobile operating systems that change every few months.
so if i was head of scirra what i would do?
push for all next gen consoles exporting capabilities so i would give my "serious" customers a fighting chance to make some money in a highly profitable environment with no designing challenges. if it works on your dev kit it works on all consoles!and as a company it would be relevantly easy since the big boys provide everything to make it happen.
then i would focus on a single mobile exporter.either android or ios. not both of them.
one step at a time and when everything is perfect i would move on to the next one.
i love the fact that the average joe can create something and upload it to the app store and brag about it to his friends and family and is really a wonderfully thing.
but right now if someone wants to really invest his time,talent and budget with c2 he will have a hard time to make any money and there are so many ways that his game will not perform well(i am talking about mobile).
that's why consoles are a good way to go with an official mobile exporter later on that it will include all the bells and whistles of that particular platform.