What we did last week:
- We defined the first stage of our Rise Player communication improvements project and it will begin with picking 2 different messaging infrastructures, prototyping them and then load testing them with tens of thousands of simulated Displays to help us choose which platform to use.
- Ready, set, go! This week 10 people from across three teams met up in Toronto where we have kicked off our first ever Design Sprint. Our goal was to simplify the process for creating presentations and adding images/video to them. Just when tensions were heightening and a solution seemed impossible, we have found one! And our sprint team has decided to build it using code, creating an almost fully-functional mock-up. We have 5 willing Rise Vision users who will be coming in to test our mock-up and their interviews will test of our sprint’s success. Spirits are high and fingers are crossed!
- Researched support for Ubuntu Core and determined that we will wait for full support of the Pi 3 before we go further. Hopefully it won’t take too long. We are quite excited about the possibilities.
- More improvements to test coverage and automated deployments for Rise Player.
- Latest Windows Rise Player now supports multiple display configurations. See this community post for details.
- We spent a fair bit of time with Chromium 50 and 51 and decided we weren’t happy with either version. Staying at 49 for now.
- We have had problems on interactive Presentations with Users being able to pinch to zoom the screen and it messes up the look of everything. This is now disabled by default.
- Corrected an issue where we would erase browser cache which would delete saved login credentials for authenticated for web pages that were being shown on screen.
- You can now install the Rise Player on any operating system, but we still only recommend and support Windows 7 or Ubuntu 14.04 or higher. See this community post for details.
- We didn’t win the zero defect war this week going from 9 to 14 open across all of our 60 active projects on GitHub.
There are no replies.