Platform Dependency

Your product might work. The platform can still break it.

Platform dependency risk shows up when the product's core value depends on someone else's API, marketplace, payment system, ranking algorithm, data access, or enforcement tolerance.

What to check before building

Do not read this pattern as “never build on platforms.” Most software depends on platforms. The practical question is whether the platform is a convenience layer or the product's kill switch.

Name the one platform, API, marketplace, payment provider, ranking system, or data source that would break the core workflow if it changed.

Read the terms for commercial use, automation, scraping, payouts, account behavior, and resale before writing production code.

Build the smallest test around the fragile dependency first, not around the easiest UI.

Ask what happens if pricing increases, access is revoked, review rules change, or the platform launches the same feature.

Create a fallback plan: alternate data source, manual workflow, owned audience, export path, or narrower use case.

Treat platform permission as part of product-market fit, not as an implementation detail.

Representative cases

These cases are not the same story. Some had users, revenue, launch attention, or working software. The shared lesson is that demand validation did not remove dependency validation.

CaseCore dependencySignal

HeadReachGoogle Site Search and third-party lead dataThe product had real early traction, but its lead-discovery workflow became hard to sustain after a core search/data dependency changed.GummySearchReddit Data API commercial licensingA useful Reddit-research product could not continue commercially after failing to reach a durable upstream data-license agreement.Unfollow EverythingFacebook workflow access and enforcement toleranceThe tool gave users control over their feeds, but public evidence shows enforcement pressure from the platform owner.Hashtag PirateInstagram hashtag-search API accessSEO traction could not save the product after Instagram API changes removed the core multi-hashtag search workflow.FlurlyStripe payout and marketplace complianceA small creator marketplace became exposed to payment-platform suspension and seller payout disruption.GrwthAppInstagram account safety and growth workflowEarly interest and paid validation were not enough when the growth mechanism depended on platform activity that could be penalized.TokiTikTok trend and influencer data accessLaunch attention and free users did not become a durable business while TikTok data access remained unstable and paid conversion stayed weak.

Common wrong conclusions

The API works today

A working response in development does not prove commercial access, stable pricing, long-term permission, or data coverage.

Users liked the demo

Interest does not answer whether the platform will allow the workflow after the product gets real usage.

We can switch later

Fallbacks are easier to claim than to execute when the data model, buyer promise, and workflow are built around one platform.

Before you build

Validate permission, fallback paths, and paid demand before treating a platform integration as the business core. If the product stops working when one API, payment provider, social account, or marketplace changes the rules, that dependency is not just technical risk.