I'm not sure if it makes things better. One of the problems is the maintenance load for 10-20 year horizon. One of niche app that you dont write yourself usually don't have that kind of support timeline, especially if the data storage mechanism based on something other than plain text (and possibly sqlite). This means that you'll more likely have to service it during that time frame. Best to keep it simple and reuse something more basic/universal rather than deploy an app that gives you a fancier UI imo.

Something like sandstorm adds even more complexity and dependencies for other applications, which brings up the maintenance burden for the long term. I don't know if I can trust it to exist in 10 years, so it's probably best not to use it for now unless I can patch it myself, which I'm not committed to do given that I can accomplish most of what it does with standard linux utilities that I'm already familiar with.