Replace Google Cloud Print in a business application
CloudPrint replaces the former Google Cloud Print model with an architecture for business applications: your backend creates an API job and a customer-controlled local agent delivers it to a specific printer.
The architectural difference
There is no global printer service tied to a Google account and browser. Each CloudPrint customer connects their own agent, and your application stores the printer_id assigned to a location or workstation.
Move printing logic to the backend
Document generation, printer selection, authentication and job creation belong on the backend. The frontend sends user intent and presents status; it never keeps the client secret or communicates with the agent.
Plan printer selection
During onboarding, list available printers with their agent and online state, then persist the chosen printer_id. Provide a settings screen to replace that choice because hardware and operating-system queues change over time.
Handle the result, not only submission
Persist print_job_id and read status until printed or failed. Waiting for an offline agent, a format error and an intentional reprint are different operator situations and should look different in the UI.
Roll out one workflow at a time
Start with one document type such as invoices or labels. Verify format, media, permissions and failure behavior, then expand. Remove old download-and-print workarounds only after the pilot is stable.
Production checklist
- Map the previous provider's devices, printers and statuses to CloudPrint identifiers.
- Create jobs from the backend instead of depending on the browser print dialog.
- Run both paths during a controlled cutover and keep a rollback window.
- Record job identifiers and failure reasons for support and monitoring.