Aphrodite ahh I see, I understood it like you were talking about all "buyers" from the initial release .
In that case I see no reasons to not agree with you.
Expectations for native comes from scirra.com main page itself - "Build Once. Publish Everywhere. True multiplatform support. Build your game in Construct 2 and publish it to all these platforms." statement.
Don't know why but people these days forgot how to read and use their logic. Instead of finding out more info about the product their will go ahead and download/buy it. And only after that they realize that this is not exactly what they thought it is. Free user have a bit better situation because they can only export to the web, so all is fine here. How game will work will mostly depend only on the browsers. But people who bought it before reading/thinking will hit the wall right away. So yeah scirra should really figure it out.
Also i noticed some part of my previous post did not show so I'll put it here again.
Web export. Yes. For me It's like an Image Editor. Add it, if it work leave it, make some occasional fixes and small additions, forget about it. There's so much stuff missing I don't even know where to start...
And just like Construct was Construct 2 will never be called a finished product. Complete product have some kind of a road map that goes from A to B and either as a developer you can make and release a full product - like most people used to do in the past. Or release it as a very popular these days "early access" scheme . Which is not bad (well not in every case) because it lets you play with it while devs have time and money to finish it up. But it still means there is a point B somewhere. Unfortunately there was only point A with C2 (and CC) there is no point B and will never be. And i don't really like it cause I don't know what to expect in the future.
With some sort of a to do list we could tell what and when to expect from it, What was done, what is in development and what are the plans for next months. But not here. It's all just one big experiment. If Ashley is in good mood he may fix some issues, if he is not then he will say "it's not compatible with our UI library"
C2 will end up just like CC did. One day they will announce "This is C3. We will no longer support C2 from this day. Buy C3 or stick with old unfinished C2"
To be honest I will not fall into that trap again. I will get C3 only if I see some sort of a road map or to do list with time tables, that will let me know what and when to expect from it. I will not spend my money on something I was told I will get just to read many months later "yeah, sorry but no" again