To be honest, I'd suggest (and this is coming from someone who has worked in the gaming industry) you'd almost be better off working strictly on a good mobile framework with a good UI than a game itself.
If you can create a low code framework, with a nice UI for would be developers, that is a much less crowded space than yet another (sorry) mobile game with 30% off the top just to be put into the IOS or Google Play stores.
It's not as sexy to non developers, but from a problem solvers standpoint, it sounds hard and from a UI developer stand point, it sounds difficult.
Working on a game engine is the ultimate (and very common) game dev trap. It's a recipe for never finishing anything as all your time and energy is eaten up trying to generalise your code to support infinite games.
It could also be argued that adding a generic game to the pile of a million games, built with the same tools that everyone else uses, and that doesn't challenge one in building it and doesn't add anything new to the industry is also a trap.
Make a non generic game then. Players don't care how you coded it.
My point is, if you want to make a game, make a game. Making an engine is the ultimate distraction. You should only be considering an engine after you have a few similar games under your belt and know there's a market for it.
If you can create a low code framework, with a nice UI for would be developers, that is a much less crowded space than yet another (sorry) mobile game with 30% off the top just to be put into the IOS or Google Play stores.
It's not as sexy to non developers, but from a problem solvers standpoint, it sounds hard and from a UI developer stand point, it sounds difficult.