> Unity making 2 games would not upset the developers
See Epic v. Apple.
Making games is a huge liability if you’re a game engine. Making a game store even more so.
Unity has made plenty of “demos” as you’re suggesting.
See Epic v. Apple.
Making games is a huge liability if you’re a game engine. Making a game store even more so.
Unity has made plenty of “demos” as you’re suggesting.
See id, valve, unreal, crytek.
As a result, these marketplaces will try and favor some other engine, such as Unity.
I think it's tough for the average techie on here to really grasp the nuances of business (mostly due to lack of direct XP), so I'm not going to belabor the point.
Direct product flaws in Unity are more likely to push customers away to a competitor compared to nebulous business relations conflicts.
A different solution I think works is to have the developers do support , you have your regular support handle the first contact but then have support forward non trivial stuff to developers and have them respond to customers. After a dev has to tackle same weird issue over and over again with support he will have the idea on how to make the thing more intuitive or less buggy.