What we are planning to do though is have "Web apps" support, similar to Flotato [1], which will allow the user to achieve the same (or better) effect.
Imagine a menu:
Open in New Tab
Open in New Private Tab
Open in New Container
Open in New Window
Open in New Private Window
Open in New Container Window
+ Tab groups! Oh my...
It is a bit too much, needs to be simplified.
Edit: Hmm, I guess not https://www.macrumors.com/2016/08/01/kagi-shuts-down/
Noticing your name - are you a free diver? If so what are your favourite dive locations?
Don't you fear being held back by WebKit, which is notoriously slow to implement new web platform features? Can you give some insights on how you chose the engine?
Thanks!
To answer the question, we need to go a step back and answer how did we chose the platform first. The decision to go with macOS first was made in 2018 for the simple reason that we thought macOS has a bright future as a consumer OS. This was pre-M1 so we are glad to see macOS adoption grow!
Once we settled on macOS, WebKit was a natural choice as it is the web rendering engine supported by the OS manufacturer. This would enable us to have best performance and OS integration features. The drawback was lack of any browser app frameworks so we basically had to write the browser app from scratch.
I am not that worried about WebKit's slow(er) pace of web platform feature adoption (although I'd love to see something like AVIF support etc.) partly because I know that these decisions are carefully weighted for their impact (what is the right level of hardware/browser/web separation for example). In the future, if Orion becomes success, we hope to be able to have full time contributors to help accelerate its development.
I am the founder behind Orion, bootstrapping the project. Started working on it three years ago with a small team just to see if it would be possible to build something like this from scratch and we just kept going. Orion is today a daily browser for a few dozen beta-testers and it warms my heart to see that we got that far considering the competition.
Few questions about Orion answered that I see pop put in the comments:
- Orion uses native Keychain integration for passwords and will use iCloud Sync to sync between devices. We have full import from Safari, including passwords [1]
- Orion uses a slightly modified WebKit which allows us to run Chrome/Firefox extension support layer on top of it (about 70% of all extensions currently work in Orion - including uBlock Origin). We are planning to complete the support in the upcoming months.
- Orion is currently trying to get to the feature parity of the reference browser (Safari).
- Orion features developer tools from Safari with a few extra ones like the Error indicator in the address bar [2] We just started with this, expect many useful additions in the future.
- Orion is designed as a zero-telemetry browser.
- Orion iOS also features a number of useful innovations like the Data saver mode [3] and multiline URL edit [4]
- The business model for Orion is to have a Pro version for those who want to support its development.
I was the founder of ManageWP [5] which got acquired by GoDaddy in 2016. Moved from Belgrade, Serbia to SF Bay Area as part of the acquisition. Spent a couple of years there as VP of Product and then decided I want to build Orion and Kagi (privacy-respecting alternative to Google search), because one ambitious project was not enough :) Main reason for this is the concern for the future of the internet and the web my children will grow into using.
[1] https://twitter.com/vladquant/status/1431290547877007363
[2] https://twitter.com/vladquant/status/1445301620187693056
[3] https://twitter.com/vladquant/status/1429588837391507458
[4] https://twitter.com/vladquant/status/1441511763631960074
[5] https://managewp.com