Printing from online and mobile applications, explained.

Yes. Connect a supported USB printer directly to an Android phone or tablet that supports USB host mode. Depending on the connectors, you may need a suitable USB-C cable or USB OTG adapter.

AppClickPrint discovers the connected printer, requests Android’s USB permission and uses the Android device as the site gateway. This is a tidy option for a counter, kiosk or workstation that does not need a dedicated Windows computer. The printer must support a printing path understood by AppClickPrint; the gateway screen shows what was detected.

Yes. The gateway regularly rediscovers network printers. AppClickPrint reconciles a printer using stable details such as its printer UUID, serial number or MAC address, then updates the current connection address while retaining the same AppClickPrint printer identity and alias.

If a printer exposes none of those identifiers, AppClickPrint can safely retain a uniquely identified model on that gateway. For sites with several identical printers that expose no stable identity, a DHCP reservation is still sensible because software cannot safely guess which physically identical printer is which.

Yes. AppClickPrint supports compatible Brother label printers across Android, Windows and Linux using the appropriate direct, SDK, USB or network printing path. It can detect the installed media on supported models and prepare the job for the available label roll.

We recommend flexible models such as the Brother QL-820NWB, which supports wired LAN, Wi-Fi and USB. LAN or Wi-Fi makes the printer available to gateways across the local network. USB also lets you connect it directly to a gateway and bypass network-level client isolation, discovery filters or firewall rules that may prevent local printer discovery. See Brother’s QL-820NWB connection information.

Yes. AppClickPrint is designed to give generated applications a documented HTTPS printing layer without making the AI builder implement Windows drivers, CUPS, Android USB handling or local-network printer discovery.

Tools such as Lovable, Replit, Base44, Bolt.new, v0, Bubble, FlutterFlow and WeWeb can add printing through a trusted backend function. AI coding agents such as ChatGPT Codex, Cursor, Windsurf, Claude Code and GitHub Copilot can also follow the OpenAPI specification and the explicit integration lifecycle.

Keep the management and customer print keys in the trusted backend. The generated customer interface only needs clear actions such as Add Gateway, Manage Gateways, Select printer and Print. See the AI app builder guides for platform-specific instructions.

Gateway platforms: customers can connect printers through Android, Windows or Linux gateways. A customer can use one platform or combine several gateways at the same site.

Application and AI-builder platforms: AppClickPrint works with any platform that provides a trusted backend or server function capable of making HTTPS requests. Popular options include Lovable, Replit, Bubble, FlutterFlow, Base44, Bolt.new, v0 with Vercel, WeWeb and Google AI Studio.

It also works with conventional Node.js, JavaScript, TypeScript, Next.js, Python, PHP, .NET/C#, Java and Ruby backends; React, Vue and Angular web applications; and Android, iOS, Flutter and React Native mobile applications.

AI development tools such as ChatGPT Codex, Cursor, Windsurf, Claude Code and GitHub Copilot can follow the same documented API workflow. Whichever platform you choose, keep the acm_ management key and customer acp_ print keys in the trusted backend rather than frontend or mobile code. See the AI app builder guides for platform-specific instructions.

Yes. AppClickPrint provides gateways for Android, Windows and Linux. By comparison, PrintNode’s current FAQ says its client is available for Windows, macOS and Linux but not Android or iOS, while QZ Tray’s published downloads and system requirements list Windows, macOS and Linux rather than Android.

Android can be especially convenient because AppClickPrint Gateway may run on the same Android phone or tablet as your customer-facing web or mobile application. For example, a reception tablet can display a visitor check-in app while AppClickPrint Gateway runs in the background and routes badges to a supported USB, Bluetooth or network printer. That can remove the cost and clutter of a separate gateway computer or device.

The Android device should remain powered, online and within reach of the printer. Allow background activity and disable battery optimisation for AppClickPrint Gateway so Android does not suspend the connection while the customer uses the other application. See AppClickPrint vs PrintNode and AppClickPrint vs QZ Tray for the broader comparison.

Not necessarily. The Windows and Linux gateways can discover and use supported network printers directly, even when the printer is not installed in Windows or configured in CUPS. Existing Windows queues and CUPS destinations are also discovered as optional printing paths.

Yes. Your application submits the job to the selected printer alias through the AppClickPrint API. The local gateway receives it and prints through the configured path, so the customer does not need to select the printer, paper size and orientation in a browser dialog for every job.

With an online gateway and a ready printer, a job will normally begin within seconds. The gateway maintains an outbound connection so the server can notify it immediately instead of waiting for a long polling interval.

Total time still depends on the source file size, internet and local-network latency, PDF conversion, whether the printer is waking from sleep, and the printer’s own processing and mechanical speed. On Android, allowing background activity and disabling battery optimisation for the gateway helps avoid delayed first prints after a long idle period.

PDF is the usual choice for labels, tickets, badges, receipts and documents because your application can define the physical page size. AppClickPrint also supports native formats such as ZPL and ESC/POS on matching printers, plus additional gateway conversions and printer-specific paths where supported.

For PDF jobs, send the intended widthMm and heightMm and create the PDF page at those same physical dimensions.

Yes. A customer can register multiple Android, Windows and Linux gateways and expose printers in different rooms, counters or buildings. Your application should provide both Add Gateway and Manage Gateways actions so users can add, replace and remove gateway devices later.

Retrieve the current printer list, let the user select the intended printer, and save its alias in your application for future jobs.

The customer can install AppClickPrint Gateway on another Android device, scan a fresh temporary QR code and reconnect the site without waiting for an IT technician. The same customer account can then discover the local printers again. Windows or Linux can also be added as another gateway option.

The gateway makes an outbound encrypted connection, so a customer does not need to expose a printer or open an inbound internet port. Developer management keys and customer print keys belong only in your trusted backend—not in browser JavaScript, a mobile application bundle or a QR code.

Temporary gateway setup codes are short-lived. Printer access remains scoped to the correct customer account and printer alias.

Create the PDF page at the intended physical size and submit matching millimetre dimensions with the job. For example, a 62 × 29 mm label should use a 62 × 29 mm PDF page and matching widthMm and heightMm.

The gateway then fits the job to the detected or configured media using the appropriate printer path. Avoid relying on a browser’s print scaling because browser defaults can introduce margins, rotation or “fit to page” behaviour.

Install a gateway at the customer site and run discovery. The gateway reports the printer identity, connection method, selected driver and supported formats to the customer portal. You can review the detected details and send a test print before using the printer in a live workflow.

Printer capabilities vary by model and connection method, so testing the exact printer, media and output format is the most reliable final check.