I'm working on TravelTracker, a travel journal that doesn't track you back.
I kept running into the same thing with every travel app I tried: they either wanted background GPS running 24/7, or they quietly turned my trip history into ad-targeting data. I wanted to remember where I'd been without handing that memory to an ad broker. So I built the thing I wanted.
No analytics, no pixels, no third-party tracking. You log trips manually (countries, national parks, UNESCO sites, cities, photos, journal entries), the data lives in one account that syncs across web, iOS, and Android, and the business model is a subscription, not your travel history.
Just shipped iOS today. Android went live last week, and the Web App has been live for a little while now.
Website: https://traveltracker.me
App Store: https://apps.apple.com/us/app/traveltracker-me/id6761914931
Play Store: https://play.google.com/store/apps/details?id=com.traveltrac...
The failure mode here is usually not that the API is down, it is that the shape or behavior changed while still returning valid-looking responses.
I would start with a small set of fixed requests against the dependency, store a known-good baseline, and classify changes separately as schema-level changes versus value-level changes.
The important part is keeping the signal narrow enough that additive noise does not page people, while removals, type changes, and null-vs-absent shifts still get reviewed before they break consumers...