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…
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.
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.
Co-founder of Raycast here. We've been using Linear since the beginning when it was only two of us. We're 16, and the app has become integral to our workflows. In a small company, it's crucial to be aligned. We use Linear to spec out our work and build up momentum. We ship an update of Raycast every two weeks and use cycles and projects to ensure we keep the release schedule.
I love the speed of the app. The real-time sync and keyboard shortcuts guarantee fast interactions. We surround ourselves with the best tools to raise the bar of what everybody expects from software. It helps us to build better software, and Linear is an app (and website) that pushes our understanding of quality forward.
We aren‘t two engineers anymore, we are seven. We still apply the same processes. I‘ve worked with huge codebases where you often you can’t know the entire system. Focus on what to build and do it well. If you touch something new, collaborate with others who know the part of the codebase. Either through PRs, pair programming or anything else that gives you confidence.
Most codebases that I‘ve worked on are too big to know everything. Often it isn‘t even required to build a feature. I think it‘s unavoidable to touch new parts of a growing codebase and you are probably not a good reviewer in the first place if you don‘t know the part of the codebase.
We wanted to achieve some native looking windows therefore the three dots. Though, it's very macOS specific. We want to keep the configurations to a minimum to get quickly good looking results. Maybe some minimal theme could work where we strip away most of the stuff. Just thinking out loud...
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…