business documents on office table with smart phone and digital tablet and graph financial diagram and man working in the background.jpeg

OS updates incoming: Will they affect your solution?

By Jeppe Melchior Mikkelsen | Sep 04 2017 | Insights | Technology

Approximately once a year, Apple and Google release a new version of iOS and Android. Although some upgrades are more comprehensive than others, they all inevitably affect our customers' ePaper and eMagazine solutions to some extent.

For this reason specifically, Visiolink has a Quality Assurance team. Their role is to troubleshoot and test our solutions to ensure that potential bugs are identified. Before they cause problems for our customers.

Google recently released the Android Oreo operating system (OS), and Apple will release iOS 11 during the autumn – most likely in September. Our Quality Assurance team are already fully engaged in troubleshooting our solutions on a beta version of iOS 11. Just like they were before the release of Android Oreo. This way, our customers will always know if it's necessary to update their solution.

Updates are inevitable
As a third party software developer, you never know what tomorrow will bring. Google and Apple can make new guidelines all of a sudden and that's why a proactive Quality Assurance team is immensely important.  

OS updates can't be ignored if you want your ePaper solution to run smoothly. There's nothing we would want more than for our solutions to be unbreakable, but it's inevitable that they'll need to be updated every once in a while. Our job is to do everything we can to discover any irregularities caused by OS updates so you know what actions need to be taken.

The past couple of OS updates haven't caused any major catastrophies and we don't expect iOS 11 to do so either - but we have found some minor issues that need to be fixed. We will reach out to affected customers directly in the near future, so the readers won’t be affected when they update their device’s OS.

Past, present and the future
Before the Quality Assurance team was created three years ago, troubleshooting on new projects was more of a joint venture between supplier and customer. Today
we take the full responsibility, and you can be sure that our solutions are thoroughly tested before release. 

Troubleshooting is done manually by the Quality Assurance team. They systematically replicate typical user sessions, and as they need to be accurate and careful to catch any glitches, it's quite time consuming. 

Enter technology.

Our aim is to automatise the troubleshooting procedure. By coding typical user patterns, we'll be able to run automatic simulations. Taking troubleshooting to even greater heights. But until then, your solution is in safe hands with our Quality Assurance team. 


Jeppe Melchior Mikkelsen

Author

Jeppe Melchior Mikkelsen