From 19 August building in Grok works on all plans, on the web and in the apps for iOS and Android. Until now it was an early beta for the most expensive subscription only. The interesting part is the address the finished thing comes out at.
- Grok Build becomes available on all plans, on the web and on iOS and Android.
- A published app gets an address on grok.me with control over who opens it, plus a preview for sharing and an option for your own domain.
- New since the July beta: remixing other people's apps, export to GitHub, secrets for external services and access to SpaceXAI's models without manual keys.
The first thing I checked was not how the app gets built. It was where it goes after you have built it.
From 19 August Grok Build works on all plans, on the web and in the mobile apps for iOS and Android. You describe an app, a game, a site or a dashboard in the chat and you get a working version on the spot. In July the same thing was an early beta, locked to the most expensive subscription.
So far that is the usual. An app from a chat is made today by anybody with a model and a text field. The difference is what happens to the thing afterwards.
Who holds the address
You publish and the thing gets an address on grok.me. You decide who opens it. You can put your own domain on it, if you have one.
It sounds like a small setting. The weight, though, sits exactly there: the platform that built the app also holds the place it lives in and the picture it travels with. That is why they tied publishing to the X feed. The link comes with a banner, with your name and with a play button, and the person meets the app right in the feed, before they have left it.
The remix
The remix is the most interesting piece on the list for me. You publish an app, somebody opens it, presses a button and carries on from your work under an address of their own.
As someone who builds sites, the deal is familiar. A theme, a template, somebody else's layout: you take the ready thing and pull it towards you. What is new is the speed, and that the copy sits on the same platform, next to the original.
If you put something out publicly there, accept that tomorrow there may be three versions of it. Just know it before you upload work that puts bread on your table.
The door out
The export to GitHub is exactly that door, and it is good that it is there. You pull the project into a repository and carry on in an editor. The secrets are in place by the same logic: the key for the external service sits outside the code.
Their own APIs pull in the opposite direction. The app calls Grok for chat, images and voice without you touching keys, and that is convenient exactly as far as you do not ask what is left of the app if one day you change the provider.
The test is cheap. Describe something small, publish it for yourself only and see what comes out on the other side. Then decide whether you want it on a domain of your own.