AIWatch.

RT Olivia Moore<br>I spent most of my weekend on ChatGPT Sites. <br><br>Here is why I think it’s the biggest unlock yet in the mainstream consumer being able to build with AI:<br><br>- Aesthetics. Almost everything I have tried to build on Claude has a similar format, similar font, similar overall (recognizable) feel. IMO, it’s great at putting things into a template - less good at creative choices. I got very different and more opinionated styles on Sites even with very little prompting. <br><br>- Hosting. If you’re a non-technical person who has tried to deploy a vibe-coded website, it’s pretty much a nightmare. Figuring out what you need to do to buy a site, handling security, setting up auth if needed, etc are all big obstacles. This is even trickier with API keys that need to be stored properly. Publishing on Sites is literally one click. <br><br>- Sophistication / interactivity. I was shocked by what 5.6 could one-shot within Sites. It built fairly complex real time game mechanics (ex swipe on cards, move around in Google Street View on a real map) with extremely simple text prompts. It would also make good choices towards making those interactive experiences work - ex. a “Bonus” page in a game should pop up with a different color and UI <br><br>- Identity / Auth. Sites utilize “Sign in with ChatGPT” - this is the first step in making “bring your own token budget” or “bring your own context” a reality. And yet, as the host the deepest analytics I could see was aggregate number of users and what they engaged with (no identifying info on anyone). Right now, you can set a Site to private or public - I foresee more to come with org-level controls, password protected access, etc.