BigBlueButton is an open source web conferencing system for online learning. Our goal is to provide remote students with a high-quality online learning experience.

    To achieve this goal, we are always looking at ways to improve the teacher and learning experience within our product. The user interface (UI) for BigBlueButton is a major component of that experience.

    Since the project’s inception in 2008, BigBlueButton has evolved and improved with each product iteration (over 14 releases since the initial version). While there have been significant architectural changes over the years, the UI has remained largely consistent with the first release.

    Recently, we’ve been working on developing an HTML5 mobile client for BigBlueButton that has an updated user experience for participating in BigBlueButton sessions. While there are many architectural changes needed to support an HTML5 client, and while we wanted to create a consistent user experience across platforms, we took this opportunity to ask ourselves “How could we improve the user experience to better reach our goal?”.

    This document will give you an overview of our motivation and design decisions consistent with the BigBlueButton user interface in HTML5 that is intended to span across platforms (mobile, tablet, and desktop).

    Cross platform capability

    There are many technical challenges to creating a cross-platform HTML5 product that implements similar functionality on all devices. Today, platforms provide by the browsers – especially those that support web real-time communications (WebRTC) frameworks – are nothing short of amazing. If you are a busy student, commuting into campus, or a business professional conducting a collaborative online training session, we would like to provide you multiple options (phone, tablet, and desktop) to join a BigBlueButton session.

    User expectations

    With the increased adoption of mobile applications, new standards, new user expectations, and new best practices have evolved; such as CSS frameworks, grid systems, layouts, placement and sizing of elements, that are creating a fairly consistent means of interaction with mobile devices.

    For example, if you have used Slack, Facebook, Twitter, or GMail mobile applications, you would notice they all share similar UI conventions that have evolved over the past few years.

    When updating the BigBlueButton user interface, we didn’t feel the need to create any radically new ways of interaction; rather, we wanted to provide users with a modern, consistent, modular and accessible interface that would be familiar to users based on their experience with other applications.

    Consistent across platforms

    In the beginning when designing the BigBlueButton HTML5 client, we initially focused on the mobile experience, which had a very different experience from the the current Flash-based web client. After all, they are different forms of interaction: touch vs. mouse, handheld vs. screen, tap vs. keyboard.

    As we developed designs for the mobile interface – starting from a very small set of design goals – we knew that while it didn’t need to work exactly the same on all platforms we wanted to create a design language that was consistent across all platforms.

    Design Goals

    Mobile first approach

    Designing for mobile first allows us to take a step back from the current user experience and think about the minimal set of features required for a participant to engage in a session (you will see lots of examples of this in the designs below).

    The current Flash-based user experience has a series of windows and layouts to accommodate different users. However; mobile applications don’t have windows, instead they have a core set of elements that intelligently overlay as the user needs to access them.

    We have a similar set of elements in BigBlueButton

    • The presentation area
    • Group or private chat
    • Participants list
    • Video (webcam and desktop sharing)
    • Preferences

    Unified experience

    Providing a unified experience will allow our users to quickly become familiar with the product and reduce the overall learning curve. If you are using the web, tablet or mobile client, our goal is to have consistent styles and placement of elements. This will also make the experience of contributing or building on top of BigBlueButton a lot easier for developers.


    Accessibility is very important to our target market of online learning. We wanted to make sure the designs would allow us to provide our users with a variety of accessibility best practises, such as Aria landmarks, Aria labels, Aria polite. While Flash has very good support for accessibility within the web browser, we wanted to be sure the HTML5 client was equally accessible as well.

    Extensible UI design

    BigBlueButton is not only a solution, but a platform that other companies build upon. In creating a new design one of our goals is to provide our community with a modular design so that new features or components can be created with ease. If a developer wanted to add a shared notes module in the UI, for example, or additional volume controls, we want to make sure the look and feel are consistent with the existing user interface.

    Client Designs

    The following are the latest user interface designs for the web, tablet and mobile client. To view all designs, please visit our InVision project.


    Participants View


    Participants View


    Presenter Views

    Presenter's first time experience

    Populated presentation

    Multiple opened components

    Whiteboard tools

    Desktop sharing

    User settings

    Participants Views

    Participants first time experience

    Populated presentation

    User action buttons

    Alert message

    Session notifications

    Style Guide

    Modular Design Example

    The HTML5 client consists of three main areas

    1. Presentation
      • PDF presentation
      • Webcams
      • Deskshare
      • Polling
    2. Participants
      • Presenter
      • Audio user
      • List only users
    3. Conversations
      • Group
      • Private

    By grouping features and content into their own blocks, it enabled us to associate content and their actions together. For example; providing presentation actions within the presentation area vs. in the top right left corner.

    Also, this design provides our development community with a framework for building on top of the existing client. If they are adding a new action for the presentation they will know exactly where to place this button. Or if they are looking to build a new module they will know that modules are their own block.

    Below we’ll outline two examples of building on top of the HTML5 client.

    Shared Notes

    The ability of collaborating together on notes for the session.

    Presentation - Uploaded a presentation

    Exploded View - Webcam, users list and public chat are turned on

    Presentation Actions - The presenter would like provide their participants with the ability of contributing to a set of shared notes. To do so, the presenter will need to select “Public Notes” from the action button.

    In the new client, we’ve decided to group all our presentation actions into a single button. This allows us to scale the presentation to multiple actions without cluttering the interface.

    If you’re looking to add a new actions to presentation, this is where you’ll place the button to activate it.

    Since the action is to activate a new module, it will appear to the right of the presentation block.

    Introducing new modules to the right of the presentation will provide developers with a dedicated area and real estate to build a variety of different features. Also, by dedicating a specific areas, will limit the interference to BigBlueButton’s core interface.

    Multiple Presentation Windows

    Multiple presenters sharing content.

    In the screenshot above, you’ll see an implementation of the BigBlueButton client with multiple presentation screens.

    Multiple presentation view

    A general rule we’d like to establish for adding to the BigBlueButton core interface, is to make sure any new item is contained within their appropriate block.

    Below you’ll see a series of layouts that following this rule. We are introducing multiple presentation windows to the interface and they are grouped within the presentation block.

    If you have any questions or feedback, please join the BigBlueButton community and post them to the bigbluebutton-dev mailing list. We look forward to hearing from you.