HTML5 UI Development

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...

  • Changing the default admin password
  • Configure platforms
  • Configure email server that InfoBurst will use
  • Configure network shares

Once that wizard is complete then it will not be run again as InfoBurst has been initially setup.

Next the user will be presented with various "Stages" to choose from.  This will be the initial landing screen when users login, but it doesn't have to be. More on that in a sec.  These are the possible "Stages" that a user can go into. Choosing a "Stage" just drops you in the that place of the UI. Users can still navigate to do the other tasks.  Think of this as a "quick jump" to the right place based on what you want to do.

  • Define "work" for InfoBurst
  • Debug burst and xdc failures
  • System Status
  • Post installation administration

Define "work" for InfoBurst

Here users will be able to browse for various objects in the system like they do right now.  They can build various objects including Bursts and XDCs.

Debug burst and xdc failures

Here users will get a interface that will aggregate errors that happen in InfoBurst.  Instead of users seeing that a schedule failed and have to find the runtime log for the burst that failed, the errors will be surfaced first. Then users can dig into the burst or xdc in question that failed.  Also we are entertaining the idea of surfacing up and aggregating platform errors and even repository connection issues.  This way the admin can possibly identify a timing pattern for when InfoBurst is having issues accessing the various resources it needs to run the Burst or refresh the XDC.  The goal of this stage is to make it easy to identify issues and gather the information needed to log a support ticket if it's needed.

System Status

This is similar to the previous stage, but the main idea goal here is to check how InfoBurst is performing overall. This would be similar to the system management screen that we currently have.

Post installation administration

This would be the place admins would go to setup more platforms, maybe change the authentication type, etc.

Now again theses "Stages" are just quick links that will jump you to the right place in the UI.  Users can opt to choose a "default location" to land in each time they login.  These defaults could be saved for each device that a user uses to access InfoBurst.  So a user can decide to always land in the System Status page if accessing from their mobile browser, but always access the "Define work"  stage say if they logged in from their desktop browser.

That's pretty much it for "Stages".  The goal with them is to get the user in the right place faster based on their intent.  We have admins as well as report writers using InfoBurst, each with their own goal when logging into the UI.

That's it for this update.  Next time i'll show you some concepts for the UI designs

2 people like this

Hey everyone!

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


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

Settings UI

UI Form

HTML5 UI development continues apace. Here are a few more previews.

User management on a mobile device:


User management via desktop browser:


HTML5 development continues. Working on the main object tile view today.



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.



Login or Signup to post a comment