*Web app for tracking QC, history, and location of WIP devices.*
# Core Features
- Each machine has its own ID
- User login using `@bigscreenvr.com` accounts
- Idling goes to a "page screensaver" featuring the username/icon. Users are asked to confirm whether it's their account before proceeding.
- Homepage for finding stuff
- Product details page featuring QC history, parts history, shipments history, location i.e. "with client" or "in house"
- Client history page with a list of timestamped events (a la Shopify history), relevant links & associated products

## Flow
- PPL scan QR code/nfc tag near the machine to log in (or can use "Login with Google")
    - That link opens their phone to a login page for the specific machine. Login here supports Passkeys and/or "Login with Google," requiring their `@bigscreenvr.com` acct.
    - Login to BQ on one machine logs out of BQ on other machines
- The login action pings a server (on my PC?) with the relevant info, which then somehow communicates with the client on the QC machine.
    - Comms-wise, this should work the same as 2FA codes. Look into that

# Pages
## Homepage
- Fuzzy search bar
- Radio buttons for search filter: `All`, `Devices`, `Clients`
- Connecting a device (HMD) instantly polls its SN and opens its details page
    - Will prob need to run an HID feature report for this. Use AI + example code from utility?



# Data Brainstorming
some data structures (tables) to consider:
- `Machine`: has columns for details like ID, Name, Description, and GPU
- `Product Type`: today, we need "Beyond 2 DVT-2" and "Beyond 2e DVT-2" types. later we may have "Halo Mount DVT", "Beyond Pro EVT", "Beyond Pro DVT-1" etc.
- `QC Template`: support many different templates, probably defined using JSON. because, for instance, Halo Mounts will have different QC steps and criteria vs. BS2E.
- `Product`: each entry has an assigned `Product Type`, and represents a unique physical product. entries will have differing identifiers, like the HMD serial number.
- `QC Entry`: each entry represents a filled `QC Template`. the bulk probably stored as JSON. should have a timestamp, and can be assigned to a `Product`.

"one-to-many" relationships:
- assigned to many `Product Types`s
  - `QC Template`
- assigned to many `Product`s
  - `Product Type`
- assigned to many`QC Entry`s
  - `QC Template`
  - `Product`
  - `Machine`

we should be able to assign a `QC Template` to a `Product Type`, and that will drive the experience of filling out a `QC Entry` for any particular `Product`.

at first, configuration assignments like that might be somewhere in __config files__ or in __the database__. then eventually, they'd be configurable on a settings page for `Product Type`s
-# such a settings page hasn't been discussed yet. we don't need to make it today!

## problems with spreadsheet
- visually overwhelming information density
- easy to overwrite cell contents/input into wrong cell
- adding comments is arduous
-