We finished our 8th developer summit last week in which developers around the world collaborated together on advancing the BigBlueButton project.
In particular, there were three presentations we made on the current and future plans for BigBlueButton.
We'd like to get input from the members of bigbluebutton-dev on these plans.
We are finishing up this release.
You can expect to see a final release soon (barring any unforeseen issues). BigBlueButton 1.0 has undergone extensive testing and we are looking forward to it's release.
1. Breakout Rooms
2. Closed Captioning
3. Faster desktop sharing (via Java Web Start)
4. Ubuntu 16.04 packaging
We are working on two mobile clients
- AIR client for iOS/Android
- HTML5 client (Android)
which are currently under active development, in parallel to the 1.0 and 1.1 release cycles, and built upon the BigBlueButton core.
# UI
The mobile clients will have the new UI (see above links for more details on the new UI under development).
The new UI will also appear in BigBlueButton core subsequent to release 1.1 (this way we can get 1.1 out sooner, which we think will benefit everyone).
As you can see from the above, we are improving the product in 1.0 and 1.1 to ensure the functionality evolves to meet the need of our target market (on-line learning) and to give other developers a solid platform to build upon.
At the same time, in parallel, we are working hard on an HTML5 client and mobile client that builds upon the *same* core -- this way, if you build upon BigBlueButton today, you will have increasing options for users to access your service.
While we focus on online learning (with its needs for accessibility for students), we are also happy to see other companies build upon BigBlueButton for offering new products and services to their customers while we focus on improving the core and providing an installation that gets everything running quickly for you on a single server.
All this leads to growing a healthy ecosystem around the project.
With all that said, what features do you want to see in future versions of BigBlueButton (and why)?
Whether it's a large or small feature, we're interested in your feedback. If you like our plans outlined above, let us know. If you would like something different, let us know too (and the reasoning behind it).
We obviously can't do everything in each release, but we do try to plan each release for maximum benefit to the project.
We look forward to hearing your feedback.
Regards,.. Fred
--
BigBlueButton Developer
@bigbluebutton