|
|
|
|
|
|
by jauntywundrkind
690 days ago
|
|
|
> When it comes to a non-hosted web app most non-technical users would have no concept or ability to run a local web server whereas “install this app” is something they’re familiar with. Clearly not true. Sonarr and Radarr for example installs like a normal app. Then sits in the system tray. If click the system tray, most options inside launch a web browser that brings you to the localhost webapp.
https://sonarr.tv/ People seem to assume this would be a hard to handle thing, but you can easily applicationize your local web services. And your local web service daemon can expose things like a system tray, to afford some classic manageability. |
|
|
Explicitly removing the browser capabilities/tools is a feature imo. i.e to hide the moving parts.
Within a browser, the average low tech users may:
- ...install extensions(ad blockers? dark reader?) that interfere with the app in some way.
- ...mess with the back/forward buttons ,corrupting the router/ui state, or just get very curious why the back button kicks them back to the last page instead of closing a fullscreen modal.
- ...bookmark SPA js-driven pages where the ui state is not fully saved in the address bar(via query params, hashes, etc) and surprisingly find them broken/not working as intended when accessing the bookmark again.
- ...try to copy and send the "localhost" link to their friends and complain.(Hold on to your papers - I've seen this behavior at my workplace!)
All of those will generate complains, useless bug reports and sometimes negative reviews. While some (if not most) of the problems can be solved with great software design and extra care, I think solving these problems comes at a cost that can be very well avoided by simply removing these capabilities.