OpenAI Just Turned ChatGPT Into an App Platform: What Designers Must Build Next

At DevDay 2026 on September 29, OpenAI announced something that most headlines treated as just another AI feature dump: ChatGPT can now host full app-like experiences through plugin extensions, with interactive sidebar panels, conversational app discovery, event-triggered automations, and a new "Sign in with ChatGPT" system that lets users bring their AI identity to third-party apps. TechCrunch called it a direct shot at the app store model. They are not wrong, but they barely scratched the design surface.

Image: OpenAI official DevDay press image, used for editorial commentary

Most of the coverage focused on the business question: who controls distribution when 1.2 billion weekly users can discover, connect, and use apps without ever leaving a chat? That is a valid concern, but it is not the one that should keep designers and builders up at night.

Here is what almost everyone missed: the design implications.

When an app lives inside a ChatGPT sidebar panel, the entire playbook for interaction design changes. Your full-screen, multi-tab, hamburger-menu-onboarding-flow app is now a narrow panel that sits next to a conversation. Navigation becomes a chat command, not a tab tap. Onboarding becomes the AI explaining your app, not you walking someone through it with tooltips. Visual hierarchy has to work in a space smaller than half a phone screen.

And then there is the discovery layer. ChatGPT will now proactively suggest your app mid-conversation when it recognizes a task your tool handles. The user does not go looking for your app. The AI decides whether your app shows up. Your app icon, your store screenshots, your carefully crafted listing SEO: all of it becomes background noise.

You earn usage through how useful you are in that conversational moment, not how optimized your listing page is. That is a profound design shift.

My Position: This Is the Biggest New Design Surface in a Decade

This is not a threat. It is an opportunity, and the people who move first will define the patterns everyone else copies.

Think about it this way. When the iPhone launched in 2007, the first wave of app designers were just making web pages that looked okay on a touch screen. The real innovation came from people who understood that mobile was a fundamentally different interaction paradigm, with different gestures, different attention spans, and different input methods. Those early designers set patterns that still define mobile design today.

ChatGPT as an app surface is the same kind of moment. The apps that win will not be the ones trying to cram their full standalone experience into a small panel. They will be the ones that rethink their core interaction for a chat-adjacent context. What does your app do best? Now, how does that one thing work when the user is having a conversation with an AI that can fill in the gaps?

This is also where the MCP Events support gets interesting for builders. Your plugin can now trigger automations based on what happens in connected apps. Your app does not just sit there waiting for input. It proactively shows up when something relevant happens. A project management plugin could surface a task panel the moment a new issue lands in a bug tracker. A design tool could open a review panel when a teammate pushes a new mockup. The interaction model moves from "open my app and do things" to "my app appears when you need it and disappears when you don't."

What Designers and Builders Should Do Right Now

1. Audit your core interaction. What is the ONE thing your app does that someone would want while chatting with an AI? Not your full feature list. The single most valuable action.

2. Prototype for the panel, not the page. Build a version of your app that works in a narrow sidebar context. Use the Newform Studio to mock up what that looks like before investing in development.

3. Learn plugin design patterns. OpenAI published documentation on building plugin extensions. Read it. The constraints are different from what you are used to.

4. Think in events, not screens. With MCP Events, your app can trigger on real-world activity. What is the one event in your users' workflow that should wake up your plugin?

5. If you can build, build now. The ecosystem is wide open. Early plugin extensions get more visibility, more user feedback, and more of a head start on the patterns that stick. If you need to ship quickly, Base44 lets you turn an idea into a deployed app without the months of setup.

The Bottom Line

OpenAI just created a new place where software lives and how it gets discovered. The app did not die, but the app store as the universal front door might be on borrowed time. For designers and builders, the question is not whether to participate. It is whether you will help define what good looks like in this new medium, or whether you will catch up to someone who did.

The chat surface is here. The canvas is wide open. Go build something worth talking to.