Print management: Why did directprint.io decide to write a new print stack for the Web?
In a word: Control
From page formatting to low-level communications protocols, the directprint.io stack allows a high degree of printer configuration management.
We use technology such as Web Workers and ArrayBuffers to max-out the performance and keep the user experience glitch-free.
New for Old
By having full control of the web stack, users are able to use support printers that may have previously been deployed but are now considered ‘elderly’. For example, directprint.io Print Management System supports ten-year-old HP printers that implement an unusual page description language.
When a print stack is delivered as an application on Chrome, updates to the print system are not tied to the operating system release cycle. This means that directprint.io can add printer support, fix bugs or respond to specific customer requirements faster and more efficiently than using a solution which relies on operating system level support. Unlike Chrome which is updated approximately once every 6 weeks, directprint.io can be updated as often as required without interruption.
Release number? What’s that?
The same rapid-deploy ethos extends to our printer management back-end. A Cloud Service is frequently updated according to new feature availability and direct customer feedback.
As directprint.io is a Cloud Service, you’ll never hear us talk about server release version numbers or any other legacy terms associated to on-premise print management.
Do you know the current version number of Google Docs? Nope, me either, and I don’t care. Print management software should be the same. You need to know you have the latest, greatest version, which you do, by default – no upgrades required.