Convert App to PWA/Downloadable

[BradKML]

Nullboards does look better than Focalboard, but it is only browser only, is it possible to convert this into an app with a browser-stored DB?

[apankrat]

Sure, why not? But I personally have no need for or interest in doing this.

If someone makes a fork and maintains it in sync with the master branch, I'd be happy to link it from the readme.

I'll leave this open for now as a place for discussing this further.

[ohitsdylan]

If you're on a Debian-based Linux distro, you can use this program to do something similar. I run this myself and it works quite well, keeping the DB separate from my daily-driver browser.

[BradKML]

Currently reading this https://web.dev/progressive-web-apps/

[sotvokun]

I did this work. It just adds some files and a simple javascript code into HTML. I test manually with live-server on local, it is working offline correctly. sotvokun/nullboard

If the owner does not merge the PWA edition into this repo and deploys it on their server, then you should deploy it on your own (It can work with GitHub Pages: https://sotvokun.github.io/nullboard/index.html). Most browsers to install PWA need to download necessary files from the server and store them on the local.

It's no difference between the current edition and the PWA edition, except the latter can be integrated into OS, e.g. drawing into a window without the address bar, showing on the Start menu on Windows. But if you clean the browser data, your content in nullboard will be lost, as the current edition. Besides, you may need to connect to the Internet to download the PWA again.

[TCB13]

I like what @sotvokun did already without it you can always create a PWA from Google Chrome by following this steps:

As you can see the result is the same, but a bit less polished. Can you create a PR @sotvokun so it might get merged?

Thank you.

[BradKML]

Weirdly enough before this note, the application resets so I lost all my cards, I wonder if this is fixed yet?

[almereyda]

Since you mention yet, it suggests this has been discussed before. Eventually there is already an issue about that case, that might be retrievable through search and can hold an additional note about this error? Or could you file a separate issue for the new error that you see? This will make it easier to triage your situation, which appears different than the subject of the conversation here.