Last week, Unity rolled out a new look version of its controversial Runtime Fee in the wake of a seismic backlash from developers who felt the original policy represented an egregious act of betrayal for a myriad of reasons.
While plenty of fury was aimed at how the fee might impact developers’ finances, some of that anger stemmed from Unity’s inability to effectively communicate its new policy and provide clear answers to pertinent questions.
The dust is now supposedly settled, but here’s one more thing: why doesn’t Unity’s explanation for its shifting answers about the Runtime Fee in relation to subscription services hold up to scrutiny?
Comments are closed.