Ashley wrote:It's hard for me to respond any more because I feel like a lot of what I say is being ignored.
The same could be said from us about you. A lot of the time you reply with a non-answer. In anycase, all of us share that feeling.
As for the rest of what you said.
How is it that people making basic 2D games with three objects, from what I ready correctly, is getting 1FPS on mobile?
Yet I have games on my phone (Zopo 999) that run full HD 1920x1080 with huge amount of enemies, explosions and soundeffects on screen all at once and I've never had so much as a frame drop.
Either Construct 2 is at fault (which I don't believe), the phone doesn't have good enough hardware (which I don't believe), or the wrappers everyone is depending on are just pure bollocks (which I believe).
Yes NW.js (and therefore chrome) has improved slightly recently, but I still occasionally get massive janks that make my game look like it's running forward then backward, repeat, repeat. And it stops if your player changes directions. It's unstable. And for the love of god, audio never works properly, WHY? :'( We've been doing the whole "wait and see" since I can remember, and probably even more before that.
You don't have to scrap this engine and start over, like that one guy said. Just hire a developer like yourself to help you fix the current engine. It's silly to try and take this entire company alone. As much as you'd like to keep it solely your own forever (or whatever other reason), one day you are going to have
hire someone to help you keep up with the programs.
As for native vs wrapper. I don't think people care which it is, as long as it works. I know I don't care if it's native or wrapper, if it works like it's intended to, then I'm a very happy man. Maybe you should look at other exporters/wrappers/whatever other than chrome. Does FireFox have one? I heard they do, but I could be wrong. In all honesty, it wouldn't hurt to look at things other than chrome, or hire an extra pair of developing hands.