Since the date of Java shutdown in Chrome is approaching, I would like to write a review of Java uploader vs. its HTML5 counterpart. What features you will lose if you switch from Java to HTML5? Are they critical? Let's try to figure out.
About one year ago Google announced that they want to clean up Chrome from 90es legacy and remove NPAPI support (and, therefore, get rid of Java plugin). The transitional period is about to finish. What it means for Aurigma's Java uploader?
The Aurigma Up 1.10 update was the largest one since its birth date and as many people experienced firsthand, it did not go well. A lot of end users complained that the app crashes on the launch while we could not reproduce the problem locally. We spend more than a week to figure out what is wrong. The app is on the way to the Apple's approval and meanwhile I am going to share what we learned from this incident.
While preparing the next Upload Suite update, we had some support requests regarding the problems with Internet Explorer when it runs in so-called EPM (Enhanced Protection Mode). So we had to figure out what is EPM and how our uploader should live with it.
Aurigma is a software company specialized in creating products for web developers: