For IT

A modern web app.
A straightforward conversation.

Here is how TurnQ is put together, where the newer capture tools process information, and what to review before a pilot.

01 / Architecture

Web-first.
Firebase-backed.

TurnQ is a progressive web app served through Firebase Hosting. Firebase Authentication handles identity, Firestore stores application records, and Cloud Functions support server-side operations such as document recognition.

  • Use a supported browser on a phone, tablet, or desktop.
  • Add the app to the home screen where the browser supports installation.
  • Share operational updates through the connected backend.

Application structure

  1. 01
    Browser / installed PWA

    The interface, device permissions, and local QR decoding.

  2. 02
    Firebase Hosting & Authentication

    Application delivery and sign-in.

  3. 03
    Firestore & Cloud Functions

    Application records, authorization rules, and server-side operations.

  4. 04
    Google Cloud Vision

    Text recognition for the document-scanning workflow.

02 / Identity & access

Access follows
the configured role.

Signed-in users receive operational access through their configured role and company/location scope. Department assignments shape the daily workspace. Backend authorization remains a separate control from what the interface shows.

Review it against your deployment.

Confirm the intended role permissions, staff onboarding and offboarding, company/location boundaries, and administrative ownership before bringing in a pilot team.

If your organization requires SSO, MFA, or other identity policies, review the actual authentication configuration with IT. Do not assume those requirements are satisfied by a web-app install.

03 / The capture tools

Know what goes where.

Document scanning, product QR capture, and customer check-in serve different purposes. Their data paths are different too.

Current implementation overview
WorkflowWhat happensWhat to review
Document scanA receipt or order photo is sent through a server-side function to Google Cloud Vision for text recognition. TurnQ does not save the original image as part of this workflow.Suggested fields require review before saving to a client record. Review provider processing terms and your organization’s policy for customer documents.
Product QRThe QR code is decoded in the browser. The user confirms a product name and saves the link and optional notes with the client.This is link capture, not a general product-page import. Check the destination and avoid saving sensitive information in URLs or notes.
Customer check-inA public check-in page submits a name, party size, and department choice to the waitlist. Phone details are optional.Review customer-facing wording, phone consent, and the department routing used at the location.
Calls & messagesContact actions hand off to the device’s calling or messaging app. Staff review and send messages.Confirm the organization’s device and customer-contact policy. This is not an unattended SMS campaign service.

04 / Devices & connectivity

Installable convenience.
Connected operations.

TurnQ supports a responsive web workflow and home-screen installation on compatible devices. The shared floor view depends on a network connection; cached app files are not a promise of full offline operation.

  • Verify supported browsers and managed-device policies with the actual pilot devices.
  • Camera-based capture requires browser/device permission. Photo selection and link entry offer alternative paths.
  • Include small screens, larger text settings, and light/dark modes in your device acceptance review.
  • Plan for connectivity, updates, monitoring, and recovery—not just initial installation.

05 / Before a pilot

Start with the right
questions on the table.

TurnQ is experimental and still in active development. A focused pilot is a chance to validate fit and requirements—not a substitute for your organization’s security and operational review.

  1. 01
    People & permissions

    Who administers the environment, what each role can do, and how access is removed.

  2. 02
    Customer data

    What may be collected, how long records are retained, how deletion requests are handled, and which provider terms apply.

  3. 03
    Operational readiness

    Device compatibility, network needs, support ownership, deployment recovery, and any required identity controls.

Built for a better flow

Less coordinating.
More connecting.

TurnQ is an experimental product in active development. We’re getting it ready for a closer look.

Demo coming soonExplore the features