Building Chalkboard with User Feedback
One of the most important parts of building Chalkboard has been learning that the best roadmap doesn't always come from the developer.
As people started using Chalkboard, I began collecting feedback directly from users through bug reports, feature requests, and general product feedback.
That feedback has become an important part of deciding what to build next.
Instead of adding features simply because they seem interesting, I'm using real user experiences to identify what is confusing, what is missing, what could be improved, and what would make Chalkboard more useful for classrooms, meetings, workshops, and collaborative sessions.
I've also started looking at feedback as more than just a list of requests. It helps me understand how people actually use the product and whether the original problems I wanted to solve are being addressed.
The plan going forward is to keep this feedback loop at the center of development:
- Build and release a feature.
- Let users try it in real situations.
- Collect feedback and identify problems.
- Prioritize the most valuable improvements.
- Build, test, and release again.
Chalkboard is still a work in progress, and I want its evolution to be shaped by the people actually using it.
The goal isn't just to keep adding features.
It's to keep making Chalkboard better.
Log in or sign up for Devpost to join the conversation.