5 ms·
I have created a number of small tools in the last and I generally have kept them stateless because I didn't want to manage (or pay for) storage of user data. I
by kevincox 8y ago
I have created a number of small tools in the last and I generally have kept them stateless because I didn't want to manage (or pay for) storage of user data. If something like this was widespread I could trivially allow the user to save their data without needing to manage that myself.
For complex applications you might want a richer API but I think that for now making it easy to adopt is a key feature and I generally just want to stick a serialized state in a small number of "files" anyways.
I really hope this takes off at some point.
- flanbiscuit 8y agoI've been thinking about building a simple todo app with some features I haven't seen available in existing ones and i want to release it out in the wild as a PWA/site and Hybrid app. I don't want to deal with storing user data and a central database but it would be nice if they could sync their data so they are not limited to one device. This is a perfect solution for a hobby app I want to create.
- vackosar 8y agowill that work with gdpr? it sounds ok but i am not sure
- kevincox 8y agoI'm not a lawyer but I think it should be because you aren't storing the users data. The one concern might be explaining that the user is sending their data to a third party (of the users choice) in a nice way.
- fiatjaf 8y agoHey, if you want this to become widespread you can just add optional support for it in your stateless apps, like I did with https://templates.alhur.es/ https://templates.alhur.es/, for example (you won't find anything simpler and more stateless than this).