I typed a reply, but there is no point , so I deleted it.
Original post asked about limitations people may have encountered with version 3. Let's stick to that and hopefully give him some specific answers, not general meaningless ones.
I hope that is not the case, because if that is the problem the whole thing falls apart. What good is the editor if your final export has problems?
Well, your answer contributions are the real meaningless. Just assumptions, useless comments and questions.
That was the answer to your stupid question. But since you didn't understand, I'll make it blunt.
Of course, if you don't know how to pick an engine for a specific purpose in the first place, then it will of course fall apart when you export. That's a no-brainer.
The exporter problems which I answered means that, it depends on what export option you choose. If you make light-weight apps or web apps, use Construct 2 or Construct 3. If you are targeting high performance games or consoles. Use other game engines for that.
— Back to you, yes HTML5 and the Exporter. Because, for example, XBox is advertised by Construct Team as Construct 2 or Construct 3 is capable to run ID@Xbox.
But in actuality, it is not recommended for ID@XBox, it should only be used for hobbyists at the moment, but not for professional games. Based on collected real life tests.
But that doesn't mean it still isn't good for other fields of development mentioned previously.
For more information :: discord.gg/G3N57fG
You can also ask on the biggest Construct Community on Discord that armaldio hosted. It has 1000+ members. We discuss there things that might be useful for information like these. And lots more.