That is one of several use case scenarios.
If you look at my comment above, that is why I mentioned a static blog. It is self contained.
If you have a dynamic app that needs a DB, then it depends on details:
- in some cases you will be able to store data on SAFE, download both the DB and data (data partially or fully) and store changes back once you close the app.
- in other cases it won’t be possible, so yes, you could not have data on the SAFE network
But for static and single user DB apps, it’s quite likely that it will be possible to download the DB and upload it back once you’re done. If your app crashes or drops Internet connection before it’s done uploading changed DB, you may lose updates or partially upload the DB or data and end up with corrupt data. Cool, now that I know that, I won’t run such apps that way until there’s a better way (e.g. save 2 or 3 versions, and delete the oldest version only when the newest is opened without and error, possibly keep transaction log locally, etc.)
I also won’t run it on other people’s hardware and when I’m traveling.
Several months after the launch the behavior of popular apps will be well understood and new versions will have smarter ways to deal with problems.