Live data from Hacker News

Show HN: Sava OS – A desktop interface for your web browser

savaos.com

41–50 of 99 posts

Re: Show HN: Sava OS – A desktop interface for your web browser

#41

I'm not sure why you got so many negative replies. As some other commenter pointed out, it can be a good use case for reusable, copyable desktops. Another use case I though about for some time - if we build an OS (a "traditional one") that consists of just a browser and only necessary stuff for running a browser, your product would be a great fit as well

So a less functional ChromeBook? I'm struggling to find the use case for your use case. Maybe for kids education if you want them to have limited capabilities? But otherwise it is just another OS with way less software support.

Re: Show HN: Sava OS – A desktop interface for your web browser

#42
post #37

I'm going to give my honest opinion. (No, I haven't given you a login email to try it, it's not that compelling) We've known how to put labels and little images together to make icons for decades, we're all familiar with the idea. And some windows, I doubt you've added anything new. And text boxes. Your splash image shows windows, with checkboxes in them. Blatantly useless, so your presentation says, "This is just th…

I ask for nothing else other than honesty. And I thank you for speaking so bluntly about your thoughts. At this point I think you're right, it is indeed a toy and a demo of my hard work. But it's also available for others to try it, and hopefully together we can turn it into something substantial.

This is a really good and mature response. He may not see the killer use case yet, but he wants to share it more broadly in case someone does.

Re: Show HN: Sava OS – A desktop interface for your web browser

#44
post #8

I struggle to understand the use-case. What does this actually offer me over just using a normal web browser with maybe a customised new tab page? I made an account with a throwaway email to play around with it, and I honestly didn't understand why I'd want to use this over whatever workflow I have now.

Coming back to this some time after my original comment, a few more thoughts in no particular order:

> a modern, desktop-like UI that meets today's needs

What are "today's needs"? Why does the standard desktop interaction paradigm not work with them? Why does "move it into the browser" solve the problem?

> it actually has some useful features to help with your browsing management

I can see some potentially-interesting features in the demo GIFs, but they don't make it clear why I'd want them through a desktop-style interface. Why not as just a browser extension or similar? What does the desktop paradigm provide that's a meaningful enhancement for the end user and not just a tech showcase?

> And then a "revolutionary" product comes out that puts our links & tabs collapsed on the side, with some extra features. Magical, right :)?

It's a bit overdone, sure. I won't disagree with that. But why does it keep happening?

imho it happens because the standard tab setup of "put all the tabs at the top of the window" had obvious shortcomings for a meaningful-enough group of users, and moving it to the side -- be that as a list, a tree, ... -- had benefits that those users appreciated, and that the more-average user may also find benefit in. Tabbed browsing had a significant benefit over the traditional windowed browsing, and imho it seems that moving them to the side has enough of a benefit over the "standard" one-row top-only tabs that people are moving to it.

But what does the desktop paradigm then offer over that? From my quick experimentation, I couldn't even figure out how to get value out of the base UI; this discourages me from then wanting to then try to ex. install your browser extension.

---

Who's the intended user? Is it specifically for desktop-heavy power users? Is it for less-technical users to gain a better interface for browser interaction?

Why floating window management? With a surprising amount of people's interactions with the web moving to mobile (smartphones, tablets), I could see the floating window interactions actually being a drawback. Tiling windows might be better, but again that's potentially very user-dependent.

Jumping off of the floating window question, where is the intended use-case? Is this for desktop users? Are tablets a supported use-case? Smartphones? Where's the line drawn? If you intend to support more than the desktop user, how will you handle the lack of precise touch? The current UI has annoyingly-small icons on desktop; if mobile is an intended use-case I could see this very quickly becoming infuriating.

How is accessibility handled? Is keyboard-only interaction possible? What about screen readers? As a disabled person, I'm pretty tired of seeing user interfaces that are incredibly unfriendly to me because they rely on precise click/tap targets that I struggle immensely to properly use at times.

The product might benefit from having an actual tour / demo / etc. It's very unclear what the true use-case for it is. Every major (desktop) OS already has drag-and-drop, multiple workspaces, floating windows, ... Having some kind of walk-through would probably go a long way towards helping people understand.

---

I don't say these things to discourage you, but this just doesn't feel ready for release yet. The sheer number of comments here on HN expressing negativity about this, at least to me, signal that the product's use-case isn't clear and that it's not obvious why this would be wanted. As a tech person, I very well understand the desire to make cool tech and show it off, but cool tech does not a product make. This reads as a tech demo being dressed up as a product, which explains a lot of the negativity here.

Your comment below[0] makes it a lot more clear that this is less "real serious product" and more "toy/tech demo/similar," and if it had been expressed as such from the start, I think the reception would have been better.

Hopefully these thoughts are of use! I do love seeing experimentation outside of the standard ways of interacting with things, and I think that with more refinement and experimentation you might find something interesting with this idea.

[0] https://news.ycombinator.com/item?id=41872816

Re: Show HN: Sava OS – A desktop interface for your web browser

#45

I was thinking about something like this. It would be cool if each app has a discovery service of commands so AI can manage the ecosystem automatically.

Not sure I understand what you mean about "each app has a discovery service of commands"

Re: Show HN: Sava OS – A desktop interface for your web browser

#46
post #44
post #8

I struggle to understand the use-case. What does this actually offer me over just using a normal web browser with maybe a customised new tab page? I made an account with a throwaway email to play around with it, and I honestly didn't understand why I'd want to use this over whatever workflow I have now.

Coming back to this some time after my original comment, a few more thoughts in no particular order: > a modern, desktop-like UI that meets today's needs What are "today's needs"? Why does the standard desktop interaction paradigm not work with them? Why does "move it into the browser" solve the problem? > it actually has some useful features to help with your browsing management I can see some potentially-interestin…

[deleted]

Re: Show HN: Sava OS – A desktop interface for your web browser

#48
post #34
post #15

If you asked me to login with Google and got my email and other info, then don't ask me to also pick a password. Bait & switch and I won't stand for it.

I understand your pain, but this is the best we could do right now to be able to implement the privacy features we mention on the website. Think about it as MFA by default, and Google is a super simple way to pass the first method. Links & tabs contain a lot of personal data, and I'm sick of hearing "Encryption at rest", while not knowing that all the admins can still see everything. It sucks I know, but at least the…

But this is a web app, so the encryption happens in a blob of JavaScript that you can update at any time. Users still need to trust you as much as they would if the data was encrypted server-side. You could maybe claim "application-level" "rock solid" encryption if your app was entirely implemented within the extension, so users could at least pick one version of it to trust, but it doesn't look like that's what you did?

Re: Show HN: Sava OS – A desktop interface for your web browser

#49
post #46
post #44

Earlier quoted context omitted.

Coming back to this some time after my original comment, a few more thoughts in no particular order: > a modern, desktop-like UI that meets today's needs What are "today's needs"? Why does the standard desktop interaction paradigm not work with them? Why does "move it into the browser" solve the problem? > it actually has some useful features to help with your browsing management I can see some potentially-interestin…

[deleted]

I wonder if I should have an LLM to sum it up...
Post reply on HN