@theericanderson I agree! We're looking at different parts of the browser, and trying to build those things that make you go "Why isn't this already a thing??" If you use syncing, and you log into SigmaOS on a new computer, you have all your pages and workspaces, all logged in already. Crazy to me that this isn't de-facto yet!
Been using SigmaOS for a few weeks. And in that short time, the amount of subtle improvements / shipping has been impressive. This feature enhancement has been brilliant and is making me a more intuitive user. Congrats to the SigmaOS crew - yβall are tremendous.
The strange thing is a friend just told me yesterday about Sigma and was telling me how envious he is of me, because i'm on MacOS :D Definitely giving it a try now that it has come right on my path again.
This is a game changer!!!! Tipped me over the edge to have Sigma as my default browser after having been playing with the browser for almost half a year now!!
@danny_vojcak Hey Danny!
We're currently just focusing on macOS, but would love to start working on a Windows app in the future! When we do, you'll hear about it first on ProductHunt π
I've tested lots of "productivity browsers" for work in the past and never got to the point where I even considered it to pay for a browser. The productivity boost was never a real difference to make it worth. I'll test yours over the next week but so far I can already see a real value and I like that you use WebKit. What I'm missing are privacy & AdBlock settings as well as the possibility to delete cookies/cache. Also my password manager plugin (Secrets as macOS native) and in general why can't I install Safari extensions? Then the sync option only would make sense if there was a Sigma browser for iPadOS, which would make your product an instant buy for me. Thanks!
@atmos_black Thanks for the feedback Atmos!
For now, we do have a general ad block you can turn on and off, but yes, we need to add more fine-tuned settings! (for a lot of stuff actually, like the cookies and cache :P)
You can't install Safari extensions because it's not part of WebKit. Safari actually built those on top. Since we had to implement our own extensions implementation from scratch, we went ahead and started working on implementing the Chrome extensions API, which is a wayy more complete and versatile set than Safari's. We're still testing it out at the moment, so not all extensions are accessible yet, but that is the final goal!
Junto