Thanks, Twosdai! My initial hesitation about adding a database wasn't really about technical complexity, but more about keeping the product and design simple. A few questions came to mind:
- Do we need accounts? If so, would that add too much friction? If not, could we identify users anonymously through a browser-generated ID?
- As more trees are generated, will the visualization become difficult to manage? Perhaps we only display a subset of them?
- How should we handle inappropriate or offensive inputs? I imagine we could use a moderation library or filter.
My main goal is to keep the experience lightweight and focused on the generation itself. That said, if a database would make participation easier and lead to a better overall experience, I'm definitely open to it.
What's your take? I'd love to hear what's on your mind.
- Do we need accounts? If so, would that add too much friction? If not, could we identify users anonymously through a browser-generated ID?
- As more trees are generated, will the visualization become difficult to manage? Perhaps we only display a subset of them?
- How should we handle inappropriate or offensive inputs? I imagine we could use a moderation library or filter.
My main goal is to keep the experience lightweight and focused on the generation itself. That said, if a database would make participation easier and lead to a better overall experience, I'm definitely open to it.
What's your take? I'd love to hear what's on your mind.
reply