Founder of Raycast here so obviously biased but you’ll be surprised. You get a working app one-shotted pretty much all the time. Sure if it is something more complex you might need a few more prompts. Just to give you some examples on what we’ve seen:
- Our support team runs on Glaze apps to review Raycast extensions. It connects to GitHub, checks out code locally, gets realtime updates and so on.
- The sound agency build a functioning synthesiser for the launch video. It works even with MIDI.
- We’re about to cancel a team-wide subscription and replace it with a Glaze app.
Not everything is possible yet and sure more complex things need more prompts but you’ll be surprised what Glaze is capable of already. It’s day one…
Sales are about distribution, they have a channel. This "moat" thing matters to unestablished start-ups a lot more. We should apply context while copy pasting arguments.
This just means that the existing sales channel would be their moat. Which can be a valid argument, though I don't remember having heard of Raycast before, so it isn't obvious to me. I was interested in hearing what they see as their moat here.
This sounds promising. If I may take advantage of you being here, what language does it write in? Does it build genuine native apps (Cocoa, WinAPI or WinUI, etc) or Electron?
The FAQ was light on technical details. But I am someone keen to read all the technical details :)
I assume there is an extensive set of rails for the agent to tie into. (Compare this to asking Claude to green fields an app. Do you use electron? How are notifications handled? Icons? Permissions?)
It springboard off Raycast’s teams feature so well it actually gives it a real reason to exist. You’re empowering the one systems thinker in the group to export their automations to the rest of the group in a way that’s proven to work: small apps that do one thing. (Big apps get complicated, become full time projects that distract from the task at hand)
Fig tried this but it was just for engineers, the value prop was missing, Glaze seems to get this right.
I feel you! We thought about this and all apps will have a permission model. So you can limit it to specific file disk locations, domains for network requests, and so on.
I don't see how this solves the issue, something bad can happen regardless of permission granularity, no?
Definitely a good initiative though. I like how coding harnesses do it, showing you the exact command that would run, or running it in a sandbox first.
We already have hundreds of extensions to integrate with Notion, GitHub, Slack and many other services. They all work on Windows as well. A whole community builds those extensions. And there is pretty much something new every day.
While we don’t have all features on Windows yet, we see this a nice uplift.
Not everything is possible yet and sure more complex things need more prompts but you’ll be surprised what Glaze is capable of already. It’s day one…
reply