Google Chrome OS will move from Google Cloud Print to native printing using CUPS
A lot of noise has been made about Google’s announced end of life for Google Cloud Print, its cloud-based printing solution. They recommend systems using Chrome OS to use native printing (CUPS), which leverages, among others, the Internet Printing Protocol (IPP) as the basis for managing print jobs and queues.
Y SOFT HAS ALWAYS INVESTED IN OPEN STANDARDS AND FULLY SUPPORTS THIS DECISION
Y Soft believes that using printing standards, such as IPP(s), eases compatibility for users across different types of devices and improves the user experience. It also improves the total cost of ownership for customers using Chrome OS-enabled devices.
YSOFT SAFEQ SUPPORTS NATIVE PRINTING ON CHROME OS VIA IPP/IPPS
Current YSoft SafeQ customers only need to configure the YSoft SafeQ Mobile Integration Gateway to receive IPPS print jobs and change the Google Admin policy to include user account and file name in the IPP header of print jobs submitted over a secure IPPS connection. The Mobile Integration Gateway is a standard feature of YSoft SafeQ that, besides handling the IPP print stream from ChromeOS, enables Airprint and Mopria functionality to accommodate printing from all major software platforms. Mobile Integration Gateway can be easily deployed in SMB and Enterprise environments and takes advantage of our patented Platform for Growth SafeQ architecture.
Many YSoft SafeQ customers use a SafeQ extension (customization) to enable Google Cloud Print within YSoft SafeQ. Y Soft will continue to support the extension up until such time that Google no longer supports Google Cloud Print.
Wouter is responsible for existing and new product direction ensuring that product delivery is smooth while keeping Y Soft in the forefront of new innovations. He is directly responsible for the product management teams. When not on a plane he loves playing with new technology including drones and Kickstarter projects.
SOURCE Y Soft