3 ms·

Agreed. The alternative would have us creating accounts, server-side storage, and supporting all this. No way this could be free, without ads.

blurker 5y ago
Yes, exactly. Having to have the backend infrastructure adds a lot of costs. For some of my apps that I've been building with local storage, I've considered adding a paid sync feature in the future if I ever launch anything that gets a lot of usage and there is the demand for it. I really want to build apps that don't trap users. I'd like to have users stick with me because I provide value, not because I "own" their data. I also want to build free apps. And finally, I want to decrease the environmental footprint of my apps. Local storage is perfect for these goals, at least for some apps that don't absolutely need centralised storage.
- Dylan16807 5y ago
  > Having to have the backend infrastructure adds a lot of costs. I don't know how much I believe "a lot" for something at this complexity level. Wordle would need a server that stores 60 bytes of data for each user that has enabled sync, and would need to send and receive that data about 10 times a day.
  - ZetaZero 5y ago
    But you also need: * Account creation * Password recovery * Backups * Privacy policy This creates more friction, both to end users and for the dev. I likely would have never tried Wordle if I had to create an account first.
    - Dylan16807 5y ago
      Well, I was specifically replying to infrastructure costs. But I can address non-infrastructure costs too. Most important is that there is no need at all to make an account first. You can stick a "make account" link under settings for the people that want it. It definitely is some amount of dev work, but it's the kind of thing where you could make an acceptable version in a day or two. Especially if it just spits a secret code at you and you input that code into a different device. Password recovery isn't necessary. Privacy policy can be two sentences. Backups can be a daily rsync.

blurker 5y ago

Yes, exactly. Having to have the backend infrastructure adds a lot of costs. For some of my apps that I've been building with local storage, I've considered adding a paid sync feature in the future if I ever launch anything that gets a lot of usage and there is the demand for it. I really want to build apps that don't trap users. I'd like to have users stick with me because I provide value, not because I "own" their data. I also want to build free apps. And finally, I want to decrease the environmental footprint of my apps. Local storage is perfect for these goals, at least for some apps that don't absolutely need centralised storage.

Dylan16807 5y ago
> Having to have the backend infrastructure adds a lot of costs. I don't know how much I believe "a lot" for something at this complexity level. Wordle would need a server that stores 60 bytes of data for each user that has enabled sync, and would need to send and receive that data about 10 times a day.
- ZetaZero 5y ago
  But you also need: * Account creation * Password recovery * Backups * Privacy policy This creates more friction, both to end users and for the dev. I likely would have never tried Wordle if I had to create an account first.
  - Dylan16807 5y ago
    Well, I was specifically replying to infrastructure costs. But I can address non-infrastructure costs too. Most important is that there is no need at all to make an account first. You can stick a "make account" link under settings for the people that want it. It definitely is some amount of dev work, but it's the kind of thing where you could make an acceptable version in a day or two. Especially if it just spits a secret code at you and you input that code into a different device. Password recovery isn't necessary. Privacy policy can be two sentences. Backups can be a daily rsync.