- LinkedIn collects a ton of user data, and had some idea to monetize it
- clever developer has a different idea about the same data, uses the API to achieve it
- users love developer's app, and they stay on LinkedIn because they love all the ecosystem apps
- maybe LinkedIn gets jealous and implements their own version. This is fine, if they don't break any laws, or cut off the original service for no real reason
Partnership sounds like some Facebook-Zygna type relationship. That seems like a really high barrier to entry. If you look at a service like Wolfram|Alpha, they're doing it right by putting reasonable restrictions on API use, and saying up front "license this commercially, contact us". This is a win-win: WA makes money, you're a real customer with bargaining power. Throwing a half-assed api out there for anyone to use, whinging about not making any money, then revoking bits piecemeal is not good for anyone.
1. Your writing seems to lose a certain quality online, maybe stick to prose? L'etranger was very good.
More broadly, it would be cool for a developer-oriented company to de-risk their API by adding some guarantees that they won't pull this kind of stuff. Right now developer agreements pretty well only restrict what the developer can do; adding conditions to limit how the interface can change would be a big selling point. The problem is, as long as VCs keep throwing money at companies that exist at the mercy of LinkedIn et al, there's no reason for them to. They get to open up the platform, watch for popular apps, then consume or copy them and lock down the API again to prevent competition.