I'll hedge a bit (I don't know much about OpenNI), but I'd posit you're interpreting Apple's moves entirely wrong, mixed in with a bit of entrenched anti-Apple

I'll hedge a bit (I don't know much about OpenNI), but I'd posit you're interpreting Apple's moves entirely wrong, mixed in with a bit of entrenched anti-Apple fandom (based solely on you advising folks on how to defeat them). At the very least, you're definitely interpreting the situation based solely on Apple's role in owning the app store, and not of the company as a whole. While I don't know about the OP open source project, as a iOS dev I know quite a bit about using Testflight. The feudal analogy really breaks down there; this has nothing to do with ruling the app world, it's a technical decision based on code-signing and app distribution. Apple came up with the system that does that, and TestFlight made it about 100x better, so Apple acquired them (and are now working on making the 1st party system infinitely better). Historically, Apple has most all their projects in-house in order to focus solely on the product and the way technology integrates. So when they close on an acquisition, it's very common for Cupertino to EOL other efforts at make the new hires and technology part of the company. When that's your approach to design, there's very little reason to support open source libraries and other projects other than your own.