Fun story, I know some of the engineers who worked on that exact Unity item. They were trying to make a very flexible billing system, so that it could be configured by business/marketing at a more personal level, and built it in a way that hopefully it would make it easier on users of Unity. For engineers here, think a purely config/DB driven way to bill, so if they wanted to say apply discounts or anything it would be a flip of an admin panel. It was a rules engine that you had any number of data points that you could use. From an engineering standpoint, it was a noble goal.

However, they handed it over to business, and yup, you guessed it, the MBAs and marketers saw it and immediately went to worst case scenarios. Engineers had no idea it'd be used that way. Installation was one of many metrics that billing could be tied to but it was never designed to. It didn't matter. The rest of the story is known. Those in charge took something that was meant to ease things for small developers and decided to use it against them. Unity lost all credibility, and my friends, the ones who helped build it, were all laid off.

Moral of the story. If you're an engineer, never go above and beyond. Never build more than what you are required to. You may have the best intentions, but there are people who will only see the worst ways to use what you build.

They will, but they have a lot fewer people and they need to deal with slop PRs now. I do not envy them.