part12studios
Thanks for the input. I'm a total noob at Unity but I'm already expecting it to be a lot harder to use compared to Construct. I've developed native Android apps in Java and have tinkered with C# in the past, so I don't really mind spending unholy amount of hours coding and tinkering under the hood. But yeah, I admit that the ease in creating games with Construct is a huge selling point. But publishing a game is just as important as creating it. What's the point in creating a game if I can't sell it? I believe that a game developer should be able to concentrate and spend most of his/her time in creating a game and not to worry about whether his game will run smooth on some devices and not on others. There are thousands of different unique Android devices out there and I'm not expecting a game to run smoothly on all of them because I know that it's not possible. But if a tool will allow me to publish a game that will run smoothly on most devices or even half and has a descent monetization tool, than I'll take it.
I am not ditching Construct 3 entirely. I have fallen in love with it (pardon the drama), but the love and hate relationship that I have with it is driving me nuts. How can my game run smoothly on older devices but lags on newer ones (at least on some of the phones I've tested)?
I'm learning Unity right now, so I'm prepared if or when I decide to make the switch.