OpenAI's ChatGPT app store has 300+ app integrations six months after launch, but developers say adoption is sluggish and the apps offer limited functionality
Context & Ripple Effects
OpenAI’s move from custom GPTs to in-chat apps was meant to put services such as travel, design, learning, and music tools inside the assistant; the initial partner pilot was framed as a way to invoke third-party services from a ChatGPT conversation. Six months in, the store’s catalog has grown past 300 integrations, but developer reports indicate that supply has outpaced meaningful use.
That echoes earlier GPT Store developer complaints about weak user reach and missing analytics. It also lands while OpenAI has reportedly struggled to broaden in-chat checkout because merchant data is hard to standardize, limiting one obvious route from assistant usage to app-developer revenue.
First-order effects
- App developers and launch partners get less effective distribution from the ChatGPT store than the integration count suggests, making continued investment harder to justify when apps are narrowly capable and discovery is weak.
- OpenAI faces immediate pressure to improve app functionality, user discovery, and developer feedback loops if it wants the store to be a credible extension of ChatGPT rather than a largely passive catalog.
Second-order effects
- Weak engagement reduces the near-term incentive for merchants and service providers to build transaction flows in ChatGPT, reinforcing the friction already visible in efforts to standardize merchant data for in-chat checkout.
- Developers may prioritize direct channels or integrations with clearer workflow adoption until ChatGPT can demonstrate repeat usage and a path to monetization; a larger app count alone becomes a less persuasive platform signal.
Third-order effects
- The result will help determine whether AI assistants become durable third-party application surfaces or remain primarily standalone conversational products with occasional tool calls.
- If this pattern persists, assistant platforms will need to compete on workflow depth, distribution, and developer economics—not merely SDK availability or the size of an app directory.
The trend: This is one data point in the shift from chatbot marketplaces toward workflow-native assistant platforms, where sustained user intent and transaction capability matter more than integration volume.