Hi HN! I created Unforget out of years of frustration with Google Keep and the lack of alternative that met all my needs. I hope you find it useful too!
Features include:
- import from Google Keep
- offline first including search
- sync when online
- own your data and fully encrypted
- Desktop, mobile, web
- lightweight, progressive web app without Electron.js
- markdown support
- programmable with public APIs
- open source [1]
While I still use org mode for long-form notes with lots of code, Unforget has become my go-to for quickly jotting down ideas and to-do lists after migrating the thousands of notes I had on Google Keep.
In addition, I'm thrilled to announce the opening of our software agency, Computing Den [2]. We specialize in helping businesses transition from legacy software, manual workflows, and Excel spreadsheets to modern, automated systems. Please get it touch to discuss how we can help you or if you wish to join our team.
[1] https://github.com/computing-den/unforget
[2] https://computing-den.com
There's an appeal to it, basically using the web purely as distribution, and the browser as the runtime. But I'm concerned with the fiddly-ness of local storage and such like that. The "out of site, out of mind" nature of it. The data not being in a "~/.app/app.dat" file, etc. The idea of it potentially just up and vanishing with a browser update. And, heck, just the complexity of dealing with the schema versioning in the native web model.
As well as the portability of data (say when you copy over to a new computer).
The idea of simple web distribution is compelling. Now you need nothing more than a github account, and off you go. No server, no nothing.
But I still feel (perhaps ignorantly) that the data situation is still on shaky ground. (Discounting the whole lack of something like SQLite, etc.)
And, the idea of bundling something like SQLite as a webassembly blob just makes me itch.
Just curious how that's worked out.