> I'm not going to keep making the same points about native engines, I wrote a whole blog about it already.
> You should probably come up with a different name to talk about exporters - I equate "native exporters" with "native engines". I think you mean built-in exporters or something like that?
Yes, sorry for the terminology. As a Designer I speak a different language Built in exporter Is probably more in line what people mean when they talk about native export here.... Completely agree with the case against native, as I've read the blog post several time trying to wrap my hand around it. I could care less what codebase is used if performance is similar.
So let me rephrase that.... How big of an hassle is it to have a "built in exporter" for mobile development? As a designer I'm jost looking for workflow improvements, less hiccups, and hassle.
Optimal workflow... Create game. Hit export, upload to Store...
Current workflow... Create game, hit export, import to 3rd party wrapper, build, get plugins working, .... it's not working... try again.... contact support... if you're lucky. Upload to store.
I'm only looking for workflow improvements. How you guys solves it it's up to you. I trust you completely... native or non native, i could care less, as long as my game is downloadable from app store without having to use XDK and such.
Couldn't have put it better!
I think what the majority of sensible users are asking for is a built in exporter and wrapper all in one, that then spits out an apk/ipa.
This will definitely cushion the blow of subscription fee disappointment and convince users that the fee is worth it.
If they can do this then I'm definitely sold!