I'm unsure this is the right place to post, or if it connects to the right folks. I want to share thoughts on how DnDB homebrew works. This will be a lengthy post.
From a perspective of a career-long developer and heavy in guidance to companies, I want to start with what I see that makes sense:
There is a lot of behind the scenes effort for homebrew. When I look at what works for me, it's at the 80%+ mark. Kudos for this effort!
Companies need to be put out work that isn't perfect. This is true for any endeavor. You get slack from users for having something the usually works. Complaints are signals for areas to improve.
You must balance priorities within a limited budget and staffing. So far, what I as an informed consumer see is that is happening. Companies change and evolve and have internal and external pressures.
Now on to things I'd like to see changed from small to large.
Helping customers appreciate what is happening is heavy on public communication. For example, the phone app provides a terse "what changed" UI feature. It is too sparse, but I respect the effort. Perhaps a link for more details would help those users deeply invested in your product?
The homebrew editing is severely limited to the web UI, and relies on old-school "BBC" style tags such as "[action]". This has sense from a programming perspective. It is odd, however, that using "[i]" (italic) and similar tags do not work, and breaks the expectation of consistency. Even better would be support for standard markdown when editing homebrew (such as "- " for bullet points). You might consider a standard markdown engine extended with additional BBC-style tags.
There is no API for access to DnDB resources created by users. This is contentious, and you might consider this leaking of IP. An alternate thinking is how to monetize you as a platform, and create a common shared way for describing RPG games. And industry standard would be brilliant, and reinforce you as a leader in gaming. This needs bigger thinking than just "D&D".
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm unsure this is the right place to post, or if it connects to the right folks. I want to share thoughts on how DnDB homebrew works. This will be a lengthy post.
From a perspective of a career-long developer and heavy in guidance to companies, I want to start with what I see that makes sense:
Now on to things I'd like to see changed from small to large.