We’ve congregated in NYC this week to hack away on open badges with the goal of pushing closer to public beta.
We are aiming for the Open Badge Infrastructure (OBI) to be in a robust public beta state by end of Q1 and we’re utilizing this dev sprint to sort of propel us closer to that goal.
How to prioritize what to do when there’s so much to do?
Over the past month, it’s become evident that being able to demo both badges as well as the OBI to show the world visually what we are building is very important.
We have since outlined some of the must-have features in this demo:
- User comes to openbadges.org and we know its the first time
- User clicks through panel:
- What are badges (informational)
- Earn badge(s) - user choose between several badges to earn (various quizzes)
- Log in via Browser ID
- Push badge(s) to OBI
- Play around in the OBI - click on badges, drag and drop into groups, etc.
- Publish a group to a public, linkable portfolio (Twitter is later)
Utilizing these demo feature must-haves as an outline, we are thinking of prioritizing our development efforts this week, the goal being to make the demo code reusable and contributing to the larger product development path.
The expected results we anticipate are robust issuer API, backpack management utility, and a displayer API development plan.
We are also thinking about how better to utilize the increasing interest coming from the Moco development community and how we can help them, help us.
Lots to think about and much to do.
More to come in the coming days.
