I'm sorry to read that. Unfortunately, it isn't an uncommon story.
> if you utilize a third-party API for the core of your app, you are at their whim.
That's the money quote, there. I avoid using third-party APIs like the plague. I have written backend aggregators and facias, to avoid having to use the API.
I Just. Will. Not. embed an opaque codeball into my app. I'm a cranky old bastard, I know, but I sleep well at night.
Open-source libraries aren’t opaque. Third-party web APIs are. The latter should only be used if they are non-critical, easily replaceable, or contractually bound to sufficient assurances.
Amen. Doing the wrong thing is easy. Doing the right thing is hard. These are thermodynamically-mandated rules that cannot ever be circumvented by cleverness or money or hard work.
> if you utilize a third-party API for the core of your app, you are at their whim.
That's the money quote, there. I avoid using third-party APIs like the plague. I have written backend aggregators and facias, to avoid having to use the API.
I Just. Will. Not. embed an opaque codeball into my app. I'm a cranky old bastard, I know, but I sleep well at night.