I cannot bring myself to trust unreviewed software enough to install it on my own machine with arbitrary permissions. I understand the push for AI-generated websites, because the code running in my browser's sandbox is gonna have very limited permissions to do anything evil, but desktop apps are a completely different story
So, another wrapper around claude 4.6 for +xx% higher price? Using just claude code, one can do what glazeapp seems to aim for, no? "Beautiful by default" seems to be a system prompt akin to:
Design Philosophy Create apps that feel premium, polished, and worthy of being featured on Dribbble's most popular shots. Every pixel matters. White space is your friend. Less is more, but what remains must be perfect.
Visual Design Principles
Color & Theming
• Use sophisticated, limited color palettes (2-3 primary colors maximum) ...
Claude Code is pretty good at Swift + Swift UI. I created and have been iterating on a menubar app for myself that I plan to share with a small team. I'd prefer to do this native than go through a 3rd party solution.
I do have prior experience developing for iOS but that was pre-swift.
I'm also just working on my first iOS Swift app (Mostly for myself, don't know yet if I'll make it public as it's just a clone of Swarm / Gowalla but based on OpenStreetMap data) and it works really well with Claude Code.
I'm not using the Xcode integration and so there's still some rough parts where build errors show up in Xcode and I then have to paste them into my Terminal.
When you are used to backend work...it's kinda fun to see an app come to life and run on your phone though.
Someone please exfiltrate their prompts/skills so i can use these on Codex. I've have relative success building my own apps for mac using Codex but they're uglier than sin and dont seem to understand well how permissions work.
Having antigravity is useful because Gemini 3.1 is pretty good at generating UI sugar. Claude 4.6 Opus provides nothing to write home about. Their shadcn looksmaxxing hasn't generalized to writing good desktop UIs.
Raycast's only edge here seems to be the fact that they are obviously very good at Mac app development and probably have impeccable skills/documentation for building them.
Taking a step back, it's pretty clear that Raycast is angling for an Apple acquisition here with this play. If I'm Apple, the reason to buy a product/team like this is a no-brainer.
My first thought was, "So, Replit and ilk?", seems they expected that comparison:
> How is Glaze different from Lovable, Replit, or v0?
> Those tools build for the browser. Glaze builds for your desktop. That means your apps can access your file system, your camera, keyboard shortcuts, menu bar integration, and background processes. Things a web app can’t do. It’s a different category entirely.
Pretty sure modern web apps can do all of those (sans menu bar). (If anything they do background processes better since you can send a very long task off to a server and shut off your computer, come back later and pick up where you left off.)
Also, as others mentioned, this just seems like Claude Code with extra steps, unless they managed to nail some sort of design standard enforcement they feel is better than what most people can get out of it.
The quick publishing is kind of nice, but it immediately made me think it would be more interesting to have a way to quickly remix other people's creations, similar to the Figma Community tab: you can take someone else's work, break it apart to see how it works, then tweak it how you want it.
1. macOS and Windows require installation of Xcode and Visual Studio respectively, and if in Apple's case you kinda can install these tools headlessly and choose to install only the "build tools" package, Microsoft's creature is gonna daze and confuse you with a crap-ton of checkboxes and no easy "just install whatever is minimally needed to compile my code" button, and I don't recall if there is way to install build tools on Windows through terminal.
2. what is going to be distributed? source code itself or actual binaries? and what will the security model of Glaze store be? same as extensions, "everything is open-source and undergoes Raycast's and community review"?
3. Glaze is going to come to Windows and Linux, if we trust the Q&A section at the end. what will Glaze build upon? separate frameworks and languages for each platform or something multi-platform [1] like Tauri or Kotlin Multiplatform? or are you going to copy the Raycast extension model - just run Node, expose some platform integration, and parse React render trees through "Glaze Runtime"? I've been working on a bug in Vicinae [2][3], and I've seen this model in action. it's very hard to make it perform well, but all it takes to achieve native look and feel is to just map React render trees to whatever system component OS offers. (in Vicinae's case, it's Qt. bet that it's done with SwiftUI on macOS and WinUI 3 on Windows.)
[1]: there is a difference between "cross-platform" and "multi-platform". "cross-platform" means "I behave equally across platforms and have no awareness of native look and feel" (e.g. Electron, Unity, Flutter), while "multi-platform" means "I can adapt across platforms to the degree you need" (e.g. C/C++, Rust, KMP)
I think we can make assumptions for all of these. Raycast extensions aren't compiled code, and run within the Raycast runtime/engine. I'd bet that this is exactly the same.
In many ways that's the same as Chrome apps, they have no code, they're just the Chrome binary, so there aren't any code signing issues.
Impressive feat. Definitely not for me though, and for sure I won't be there to debug one of these when my parents will call me because it broke their computers.
I thought this must be a joke at first. "Glaze" is in pretty heavy use as recent slang for "when someone excessively praises another person in a way that feels over-the-top." https://creativesimiles.com/glaze-meaning-slang/
Looking forward to trying this out and see how this differs from more manual approaches. One thing that stands out is an included store for public/private distribution — that’s super convenient given the cumbersome (and maybe, horrific) process that is the app store submission.
Just what absolutely no one needed: another locked down and non web platform with horrific security that tries to digitally enslave people just the tiniest level above what they can accept now. I don’t see any future where raycast can survive and i would say its a good thing.
So it looks like they’re creating their own App Store within the app? At least it’s kept separate from official apps. But also how is that not a security nightmare Apple won’t allow?
I love Raycast. I would probably be called a "power user" - I use it all day long and have a fairly sophisticated and customized configuration and set of workflows. Raycast is actually one of the primary things keeping me on MacOS these days (please release a Linux version!).
I am worried this is the start of them trying to diversify their product offering because revenue has stalled in the core Raycast product and VC demands more returns. I don't want to be jaded, but history teaches me to be. Here's hoping that Raycast itself is still a focus for the company.
65 comments
[ 2.5 ms ] story [ 76.4 ms ] threadI wonder what it is actually building. Tauri apps, maybe?
I do have prior experience developing for iOS but that was pre-swift.
We need more of you. Not more electron slop.
I'm not using the Xcode integration and so there's still some rough parts where build errors show up in Xcode and I then have to paste them into my Terminal.
When you are used to backend work...it's kinda fun to see an app come to life and run on your phone though.
I imagine that would help the process a lot
Having antigravity is useful because Gemini 3.1 is pretty good at generating UI sugar. Claude 4.6 Opus provides nothing to write home about. Their shadcn looksmaxxing hasn't generalized to writing good desktop UIs.
Raycast's only edge here seems to be the fact that they are obviously very good at Mac app development and probably have impeccable skills/documentation for building them.
Taking a step back, it's pretty clear that Raycast is angling for an Apple acquisition here with this play. If I'm Apple, the reason to buy a product/team like this is a no-brainer.
My first thought was, "So, Replit and ilk?", seems they expected that comparison:
> How is Glaze different from Lovable, Replit, or v0?
> Those tools build for the browser. Glaze builds for your desktop. That means your apps can access your file system, your camera, keyboard shortcuts, menu bar integration, and background processes. Things a web app can’t do. It’s a different category entirely.
Pretty sure modern web apps can do all of those (sans menu bar). (If anything they do background processes better since you can send a very long task off to a server and shut off your computer, come back later and pick up where you left off.)
Also, as others mentioned, this just seems like Claude Code with extra steps, unless they managed to nail some sort of design standard enforcement they feel is better than what most people can get out of it.
The quick publishing is kind of nice, but it immediately made me think it would be more interesting to have a way to quickly remix other people's creations, similar to the Figma Community tab: you can take someone else's work, break it apart to see how it works, then tweak it how you want it.
that's would be Electron app, but without unneeded bloat
1. macOS and Windows require installation of Xcode and Visual Studio respectively, and if in Apple's case you kinda can install these tools headlessly and choose to install only the "build tools" package, Microsoft's creature is gonna daze and confuse you with a crap-ton of checkboxes and no easy "just install whatever is minimally needed to compile my code" button, and I don't recall if there is way to install build tools on Windows through terminal.
2. what is going to be distributed? source code itself or actual binaries? and what will the security model of Glaze store be? same as extensions, "everything is open-source and undergoes Raycast's and community review"?
3. Glaze is going to come to Windows and Linux, if we trust the Q&A section at the end. what will Glaze build upon? separate frameworks and languages for each platform or something multi-platform [1] like Tauri or Kotlin Multiplatform? or are you going to copy the Raycast extension model - just run Node, expose some platform integration, and parse React render trees through "Glaze Runtime"? I've been working on a bug in Vicinae [2][3], and I've seen this model in action. it's very hard to make it perform well, but all it takes to achieve native look and feel is to just map React render trees to whatever system component OS offers. (in Vicinae's case, it's Qt. bet that it's done with SwiftUI on macOS and WinUI 3 on Windows.)
[1]: there is a difference between "cross-platform" and "multi-platform". "cross-platform" means "I behave equally across platforms and have no awareness of native look and feel" (e.g. Electron, Unity, Flutter), while "multi-platform" means "I can adapt across platforms to the degree you need" (e.g. C/C++, Rust, KMP)
[2]: https://github.com/vicinaehq/vicinae
[3]: https://github.com/vicinaehq/vicinae/pull/1158
In many ways that's the same as Chrome apps, they have no code, they're just the Chrome binary, so there aren't any code signing issues.
ie the annoying way that LLMs interact with users
I am worried this is the start of them trying to diversify their product offering because revenue has stalled in the core Raycast product and VC demands more returns. I don't want to be jaded, but history teaches me to be. Here's hoping that Raycast itself is still a focus for the company.