Most self-use apps - note-taking, nutrition logging etc don't need a backend unless for social sharing reasons. But most apps do have a backend because that's necessary (?) for profitability.
Even self-hosted web sites (that people call "applications") are annoying to me because I don't have the time to take care of a personal server, and most applications only use local data.
But... it's written in JS, it's easier to write than a C++/CMake application that you must package, and it's cross-platform by default.
> don't need a backend unless for social sharing reasons
Sync between devices is a compelling reason to have some backend. But I prefer it the way Super Productivity does it: integrating a bunch of third-party storage services like Dropbox. Usually, you already use one anyway
4 comments
[ 2.9 ms ] story [ 20.5 ms ] threadBut... it's written in JS, it's easier to write than a C++/CMake application that you must package, and it's cross-platform by default.
Sync between devices is a compelling reason to have some backend. But I prefer it the way Super Productivity does it: integrating a bunch of third-party storage services like Dropbox. Usually, you already use one anyway