CloudPrint is a Google Cloud Print alternative for business applications that still need centrally controlled printing to remote offices, shops and warehouses. Your backend creates the job through Public API, and the customer's local agent sends it to a specific printer.
## Decide whether a cloud-printing service is needed If every user can select a local printer and confirm each job, the operating-system or browser dialog may be enough. CloudPrint fits applications that need saved printer assignments, unattended or remote workflows, server-side auditability and explicit job statuses. ## 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. ## Map the old workflow Replace account-linked printer discovery with CloudPrint agent onboarding and `GET /api/v1/printers`. Replace client-side submission with a backend document upload and print-job creation. Replace implicit success with polling of the saved `print_job_id` until `printed`, `failed` or `cancelled`. ## 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`, `failed` or `cancelled`. Waiting for an offline agent, a format error, a cancelled job 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. ## Next steps