Scrappy co-creator here. I fully agree that software longevity is important. We designed Scrappy with a local-first architecture, so we have no traditional backend. Our only cloud dependency is a lightweight sync server. (We hurriedly added an FAQ with some more technical details after we discovered that this blew up on HN.) I believe this is an important point of distinction, both technically and financially, from most low-code/no-code tools which are SaaS'es.
One idea we had early on is the ability to save scrapps as single-page self-contained HTML files. We experimented with this but the functionality isn't currently exposed.
Being able to download a self-contained html file would be great. Not only for longevity, but also for situations where internet access may be questionable.
One idea we had early on is the ability to save scrapps as single-page self-contained HTML files. We experimented with this but the functionality isn't currently exposed.