Live data from Hacker News

Porting a 100% local app to the web

actualbudget.com

51–60 of 81 posts

Re: Porting a 100% local app to the web

#51
post #42

Earlier quoted context omitted.

CUPS admin console, SharePoint admin console for example. Same can be done with web widgets, or a couple of utility daemons. Well, at the end of the day don't complain about Google owning the Web.

... are there any people on earth who prefer to use the CUPS web console rather than their DE's printer settings ?

At least one!

Re: Porting a 100% local app to the web

#52
post #38

Earlier quoted context omitted.

Desktop apps can reach higher quality. Compare e.g. Apple Keynote to Google Slides, the difference is obvious.

Ha. Wanted to counter your argument with: Keynote is older. It is, but just by 3 years, (2003 vs 2006). Depending on the features you use your argument might fall flat though, how do I collaborate on a presentation? How can I easily share a presentation with a set of folks? I like Keynote a lot, but Slides has it’s use cases as well.

> Keynote is older. It is, but just by 3 years, (2003 vs 2006).

Fun fact: 2003 was Keynote's public unveiling. Before that, it was a bespoke NeXTSTEP app created for Steve Jobs. (I'm not sure how old proto-Keynote is, but IIRC he'd used it publicly since the late 90s.)

More here: https://apple.fandom.com/wiki/Keynote

Re: Porting a 100% local app to the web

#54

Your homepage convinced me to download, the software reminds me a lot of Microsoft Money, which was one of my favorite tools due to its simplicity. Only complaint is no dark mode, but really cool!

Awesome, thank you! You are the first person to ever mention dark mode which is super surprising to me! I bet others have had the thought, just haven't said anything. It will come at some point but it's not a super high priority.

Re: Porting a 100% local app to the web

#55

Are you using the quota API? Looks like you can ask how much space is available, so you could warn the user to free space if it is below some threshold. https://web.dev/storage-for-the-web/#check

Not yet! I plan to but it's not fully supported (I think Safari is the only one missing?) and you still have to handle quota exceeded errors anyway. My first step will be handle the quota errors gracefully and warn users that it's not locally saving changes.

Re: Porting a 100% local app to the web

#57

It was interesting to read the stated advantages of each platform: For web: * Easy deployment * Better conversion rates (no installation) * Easier login flow, support, a/b testing For desktop: * Better tech (sqlite3 in this case) * Super fast * User owns the data What struck me is that the advantages of the web are primarily sales and developer advantages and are focused around the novice user experience. Whereas the…

The business case for native apps (whether on desktop or mobile) is that it's not just another tab people can X out of. Installing a native app feels like a commitment. The icon is there. It might be sitting in the tray/taskbar. It commands attention. It can push notifications that most users wouldn't turn off.

Most users do not know what a PWA is and won't install it unless it was done for them. Even then a PWA is at the mercy of the host browser's configuration and addons which can degrade the experience. (And on Apple devices it won't even work.)

Re: Porting a 100% local app to the web

#58

It was interesting to read the stated advantages of each platform: For web: * Easy deployment * Better conversion rates (no installation) * Easier login flow, support, a/b testing For desktop: * Better tech (sqlite3 in this case) * Super fast * User owns the data What struck me is that the advantages of the web are primarily sales and developer advantages and are focused around the novice user experience. Whereas the…

Nothing about the web platform prevents keyboard shortcuts or high levels of customizability. Moving away from these is just a cultural shift in the industry, for better or worse.

Re: Porting a 100% local app to the web

#59
post #57

It was interesting to read the stated advantages of each platform: For web: * Easy deployment * Better conversion rates (no installation) * Easier login flow, support, a/b testing For desktop: * Better tech (sqlite3 in this case) * Super fast * User owns the data What struck me is that the advantages of the web are primarily sales and developer advantages and are focused around the novice user experience. Whereas the…

The business case for native apps (whether on desktop or mobile) is that it's not just another tab people can X out of. Installing a native app feels like a commitment. The icon is there. It might be sitting in the tray/taskbar. It commands attention. It can push notifications that most users wouldn't turn off. Most users do not know what a PWA is and won't install it unless it was done for them. Even then a PWA is a…

This is true, and I'd bet it's one of the main value-adds of Electron

Re: Porting a 100% local app to the web

#60
post #57

Earlier quoted context omitted.

The business case for native apps (whether on desktop or mobile) is that it's not just another tab people can X out of. Installing a native app feels like a commitment. The icon is there. It might be sitting in the tray/taskbar. It commands attention. It can push notifications that most users wouldn't turn off. Most users do not know what a PWA is and won't install it unless it was done for them. Even then a PWA is a…

This is true, and I'd bet it's one of the main value-adds of Electron

I've built a few electron apps lately. That's an advantage, but another important one is that you can use node APIs in what is otherwise basically a webapp. The app I'm working on now is an SSH server monitoring thing, which wouldn't be possible in the browser (maybe with wasm, but /shrug).

I should mention though that desktop apps seem to have an order of magnitude conversion rate than web apps... it's been a slog.

Post reply on HN