Does this OPFS solution help with us having to store all gneeration information in json instead of hosting a new DB?
Yes. OPFS lets us ship the MVP without hosting a DB by storing all generation metadata as JSON alongside the assets. It’s a perfectly viable pattern if we design it cleanly and plan an easy migration path.
Yes—that’s exactly the right mental model: SpriteDX = local-first product (writes/read files locally, fully usable offline), and cloud sync = QoL add-on you can ship later without touching the core UX.
Sprited Dev
Does this OPFS solution help with us having to store all gneeration information in json instead of hosting a new DB?