A&H’s support is of course legendary, but with custom apps there’s a perpetual fear among users that there will come a time when the app will stop being maintained and eventually become unusable due to a host-platform (iOS, Windows) incompatibility.
An HTML5 browser-based UI will go a long way towards addressing this, because browsers usually maintain backwards-compatibility for decades. Most apps these days are designed as thin wrappers around HTML5 code anyway, so if this is true of the CQ MixPad app, then it shouldn’t be too much trouble to expose it through a vanilla browser.
This will automatically address other feature requests (such as Linux support), and concerns (different users having incompatible app versions) I’ve seen on these forums.
One potential thorn is that the CQ firmware itself is packaged with the app download today. A solution could be to strip the app down to just a firmware delivery vehicle, after which the actual control would be through HTML5. The great thing about this is that once some device – any device – delivers a new firmware version to the CQ, all other devices automagically get “upgraded”.
Are there any other problems with this approach?