The InfoBurst user interface (UI) developers are hard at work developing a brand new, HTML5 UI to replace the current Flex (Flash) interface. Follow this forum topic to receive updates from the developers on UI concepts, insights, and development progress.
UI Update Time, Stages
Hey everyone, we're hard at work building out the skeleton of what will be the new HTML 5 UI. We have come up with some potential concepts which will be apart of the new UI. The first one is "Stages".
When users come into InfoBurst they will have a certain task in mind. Things ranging from building new bursts and XDCs down to checking in on why something didn't get delivered.
The very first stage will be product setup. This will be like a wizard for when the admin first logs in. There are various things that should be done before you can catalog a document to start their first Burst. Things like...
Development work has begun on the Burst user interface. The Burst UI is the most complex aspect of InfoBurst and our developers are focused on providing a clean, modern, easy-to-use interface. Here are some of the Burst UI concepts:
The development team are hard at work on the Burst user interface which is the most complex interface in InfoBurst. Here are a few mocks of the new Burst interface.
HTML5 development continues. Working on the main object tile view today.
Here are some sneak peak videos for the Settings and Platforms interfaces. At this point we're still building the structure. Styling will come later.
Responsive UI with Platforms
HTML5 UI development continues apace. Here are a few more previews.
User management on a mobile device:
User management via desktop browser:
Got a short but sweet update for the new InfoBurst UI. Oddly enough this isn't an update on the UI itself, but rather the API that will support the UI. I've spend a bit of time working on the API which will drive the future user interface (UI). I've been working on this not only with the view of our UI team using it, but also with the view of others using it as well. Others using this API, who wish to have InfoBurst integrate more deeply into their business workflows.
So, we've adopted an API documentation technique where we use it in house, and we expose that same documentation to anyone who wanted to use it. This documentation process is now ingrained into how I expose new API endpoints to be used by our UI dev team. This means anyone who wants to use our API will get the same developer experience as our own internal dev team. This is to continue to keep InfoBurst as the level of being a platform and not just a server based application solution.
This documentation will grow and continue to be unit tested as we add new features into the product!
Cheers and look forward to more information on how the UI side of things have been progressing. Stay tuned :D