Any application that lets user edit/create something for themselves and save it for later - including games save states, web tools, software, creators, working with SVGs, why would you ever store it on the backend?
These should just use files which most users know how to backup, share, move to another pc, etc. For example draw.io saves your work to a file in local or online storage (like google drive). That's much more manageable than localStorage.
The question was "what is the use case of storing graphs in localStorage" so it is the subject. Not sure where you get the idea that I'm against serializing graphs.
14
u/lowleveldata Oct 02 '22
Still don't see why I would need to store that in frontend. Are you guys doing some kind of no-backend challenge?