Dots on Mobile: The Confused Rollout Nobody at OpenAI Explained

Three weeks after dots launched, one of the most basic questions about the product — can you create one from your phone — doesn't have a clean answer. Not because the feature is complicated, but because the two most-cited descriptions of it contradict each other, and neither one is OpenAI's own release notes.

An October 1-dated guide described dot creation as desktop-only, with mobile support characterized as coming at some later point. A separate, October 13-dated piece reported the opposite for part of the experience: that the ChatGPT mobile app could already create a dot, even though mobile web still couldn't. Both pieces are secondary sources — third-party guides describing the product, not OpenAI's own changelog or help-center documentation. They don't agree, and this article isn't going to pick a side for them. The honest state of the record, as of this writing, is: unresolved.

Why this is worth an article instead of a footnote

It would be tempting to wave this off as a minor rollout detail that'll sort itself out. But "can I create the thing from my phone" sits right at the edge of the product's basic usability, not some advanced configuration option, and the fact that it's being reported inconsistently two weeks apart says something about how OpenAI has handled all of dots' mobile rollout communication: quietly, incrementally, and without a single canonical source a user can check against.

Compare that to the handful of items that OpenAI has put in its own official ChatGPT release notes during the same window — Locked Chats rolling out to Free, Go, Plus, and Pro on web, iOS, and Android on October 20; "Finances in ChatGPT" expanding to Free and Go users in the US on October 2; mobile camera multi-page PDF scanning on iOS, and virtual try-on and Favorites on mobile and web, both dated October 1. Those are confirmed, dated, official entries. None of them mention dots by name. That's a real split in OpenAI's communication: consumer ChatGPT features get a changelog entry; dots' mobile behavior, so far, gets described by other people.

How two careful writers end up disagreeing

It's worth walking through how a contradiction like this actually happens, because the instinct to assume one side is simply mistaken misunderstands how staged rollouts get covered. A guide published October 1 reflects what its author could verify on October 1 — tested against a specific account, a specific region, a specific build of the app. A guide published October 13 reflects the same exercise, two weeks later, potentially against a different build that had already picked up a server-side flag change nobody announced. Feature flags and staged rollouts are common practice for large consumer products precisely because they let a company test a change against a subset of users before committing to it everywhere — which means two accurate, careful write-ups, two weeks apart, can describe genuinely different experiences of the same product without either one being wrong at the time it was written.

That mechanic is largely invisible from the outside. A reader comparing the two guides side by side has no way to know whether the October 1 guide was simply overtaken by a later rollout stage, or whether the October 13 guide caught an early A/B test that hasn't reached general availability yet. Only OpenAI knows which, and OpenAI's own channels haven't addressed the mobile-creation question directly in the sources checked for this piece.

What this tells you about where dots sits in OpenAI's priorities

It would be an overreach to say OpenAI is deprioritizing dots based on a documentation gap alone — a month-old product with a staged rollout is allowed to have rough edges. But the pattern is consistent with something we flagged when dots first shipped: access on day one was already narrower than the marketing suggested, gated by subscription tier and region. A mobile rollout that's inconsistent enough to produce contradictory third-party reports fits that same shape — a product being rolled out in pieces, to different surfaces, on a timeline OpenAI hasn't fully narrated in public.

It's also a reminder of something easy to forget when reading any single guide about a fast-moving product: a guide dated two weeks ago is not automatically wrong, but it is not automatically current either. Dots changed enough between October 1 and October 13 that two conscientious writers, working a couple of weeks apart, describe a materially different mobile experience. Neither guide is likely lying; the ground almost certainly moved under both of them.

When two independent guides disagree about whether a basic feature works on mobile, the reasonable conclusion isn't "one of them is wrong." It's "the company hasn't said, and the feature is still moving."

This also means a question like "does mobile dot creation support the same plugin ecosystem as desktop" is currently unanswerable from the public record at all — if the base question of whether you can create a dot from a phone doesn't have a settled answer, any downstream question about what that mobile-created dot can actually do is several layers further from confirmed.

The practical takeaway

If you're trying to create a dot from your phone and it isn't working the way a guide told you it would, don't treat that as a bug report against the guide. Treat it as confirmation of exactly the uncertainty described here: OpenAI's mobile dots experience, as of late October 2026, does not have a single authoritative, dated, official description anywhere you can point to. Until that changes, the only safe assumption is that mobile support for dots is a moving target, not a settled feature, and the right move is to check your own device's actual behavior rather than take either guide's dated snapshot as current.

Part 32 of 47 in the ChatGPT Dots series. Previously: The Grace Period Ends: What Happens When Dots Usage Starts Counting. Next: GPT-Live-1.1: Six New Voices and What They Mean for Talking to Your Dot. Browse more builder insights or explore AI skills at aiskill.market.