Smart TV and keyboard-free surfaces
What this is
A television remote is a bad keyboard. So is a kiosk touch panel, a printer display or a smart device with a screen and three buttons. Veriqa's model — start where typing hurts, confirm on the phone the user already holds — fits those surfaces without inventing anything new for them: the screen shows a QR code or a short prompt, the user confirms in Telegram, WhatsApp or another messaging app, and the session on the big screen continues.
Structurally this is the familiar device flow: a screen that cannot accept input delegates the sensitive step to a device that can. The difference is where the confirmation lands — in a messenger the person opens every day, rather than in yet another authenticator app installed for this purpose alone.
What it is for
- Sign-in and registration on TV apps and kiosks without typing an email and a password with arrow keys.
- Linking a notification channel in the same action. The user signing in on the TV can, with one confirmation, also become reachable in that channel later — release reminders, subscription notices, support. On a surface with no convenient input this pairing is worth more than the sign-in itself.
- Services whose audience already lives in a messenger. Where the product already talks to people in Telegram, WhatsApp or another messenger, signing in through "their" channel converts better than an abstract QR code pointing at a browser.
Where this stands
Where the device has a browser or a webview, the ordinary sign-in through Veriqa works today: a
page with a QR code, confirmation in a messenger, OIDC tokens for the application. Without a
browser it works too, if the application has a backend of its own: the server creates a
confirmation transaction with POST /api/transaction/confirmation and receives the channel's deep
link together with a ready-made QR image — a TV app on any platform can display it — reads the
outcome with GET /api/transaction/{id}/result and exchanges the confirmed transaction for the
user's id_token. What is still missing is a path for a device with no backend of its own: a full
implementation of device flow is in progress. Veriqa has no native TV SDKs.
We are working on this: what works out will appear in releases as it is developed; if the direction does not hold up, this page will say so.