4 ms·
This whole situation highlights another problem, you should never base a business around a third party API or service. Remember when Twitter changed their guide
by DigitalSea 14y ago
This whole situation highlights another problem, you should never base a business around a third party API or service. Remember when Twitter changed their guidelines and API usage rules basically destroying companies that had built a product based around Twitter only for it to be deemed in violation of the new rules? This situation should be a warning to others thinking of putting their eggs in one basket, because if the service you've come to rely on has the final say in the end for how your product should function and if that understanding is based on loose interpretation of company rules, you are at the mercy of that reviewer.
I hope AppGratis sorts this all out, it's a heartbreaking story. I know from experience what it's like to spend months working on something only for it to be rejected.
- duncan_bayne 14y agoNever? There are many cases of highly successful businesses being based upon a 3rd party API. E.g.: every successful software company that sold CP/M, DOS, Windows or UNIX software. Perhaps a better statement would be: understand that there are risks inherent to building for any given API, study those risks, and mitigate them. CP/M seems to be dying off? Hope you've started your DOS port already :)
- DigitalSea 14y agoYou make a valid point, but I was referring more specifically to web based services and more tightly controlled micro-commerce platforms and operating systems. Considering the high market share of Android I can't fathom ever not building both an Android and iOS version of an app, regardless of cost you have one or the other to fallback on. If both fail however, then you have a mega problem.
- JonoW 14y agoThe key difference is that there is no way for Microsoft to revoke an application from a users pc (pre app store I mean)
- jacquesm 14y agoThe existing apps were not revoked and still work.