#Developer raycast saas 15m install#
#Developer raycast saas 15m code#

Inside the command, you can perform “actions” in our central “action panel” that’s everywhere in the app. You can launch commands to run some business logic, often by presenting a user interface to Raycast. An extension became an umbrella term for one or more “commands” Sidenote: if you’ve ever tried to build an extension for a more complex tool such as Atlassian’s Jira, you might feel us 🥲 We wanted to create a community with collective creativity, where people could build cool and useful things that we wouldn’t even think of. This was important for our success because we couldn’t build integrations for the vast tooling landscape all by ourselves. Our goal was for them to have the freedom to customize Raycast and create shareable extensions that other users could install, in a similar way to an app store. Some context from the early days Soon after launching we found our superpower: creating our communityĪfter the public release of Raycast in October 2020, we started exploring how we could create an API for developers.

#Developer raycast saas 15m code#

So users feel at home as soon as they open a command powered by an extension.īut you typically develop native UI in Swift and compile code in Xcode, so how does the entire system work? Instead of diagrams and code, we’ll use “tech storytelling” to dive into our journey here, including our current solution, the decisions and tradeoffs we made and the concrete technology and architecture we’ve been using. To us that means consistently rendering a native user interface with our customizations. Why’s that our philosophy? Well, Raycast is a fully native macOS app and we treat extensions as first-class citizens.

Sorry if that’s disappointing to any webview fans out there! One of our early design goals was that we avoid a second-class mini-app that shows in some frame in Raycast, where developers use technology X and user interface paradigm Y, then ship it.

#Developer raycast saas 15m install#

It’s a great question, if a little knotty, especially because we’ve intentionally tried to hide when users interact with extensions in Raycast.Īlthough users do technically install an “extension” through our store, it should never feel like they are. Since releasing our API, lots of developers have asked how it all works under the hood.