E1O guides / Engineering preview
Twitch chat in your glasses
A compact chat feed could help you catch a message while your hands are busy. Here is how E1O’s current renderer handles text, and what still needs a live test.
Catch a message.
Keep doing your thing.
Development preview. The software tests below use sample messages. Live Twitch authorization, physical readability and end-to-end reconnection are not established by these results.
A recent-message view
The useful unit is a short message you can identify quickly: who said it, followed by enough text to understand the point. Our renderer keeps a bounded recent-message list. It opens at the latest row and supports refreshing the view. Long messages are shortened to fit a row.
| Software test, September 8 | Observed result |
|---|---|
| Input | 40 sample messages with long text |
| Output | The newest 20 messages |
| Row budget | At most 64 characters, including the username prefix |
| Initial position | Latest row |
These are renderer limits, not a promise that every connector request returns 20 messages. The amount received depends on the configured source. They also do not measure how quickly a person can read the display. The empty-feed state asks for a refresh instead of inventing new messages.
The phone and connection still matter
The glasses do not establish a standalone Twitch connection. The intended flow uses an authorized connected service, the E1O phone app and the glasses display. A working rendering function is one part of that chain; a connected Twitch account and a successful live read must also be verified.
Twitch documents EventSub as its preferred interface for receiving chat events, with separate authorization and API behavior. An integration must handle those requirements as well as the display. See Twitch’s chat documentation.
A reproducible alpha test
- Use a channel and Twitch account you are authorized to test, together with the compatible E1O app, glasses and connected-service setup.
- Confirm the chosen channel on the phone before opening the glasses view. Send a distinctive test message and compare its username and text on both surfaces.
- Try short messages, long messages and an empty interval. Verify truncation and the empty-feed state without assuming the entire conversation fits.
- Send a burst of messages. Check that recent messages remain identifiable and that scrolling or refreshing does not make it difficult to keep your place.
- Disconnect and reconnect the phone’s network, then the glasses connection. Send a new message after recovery and verify that it actually arrives.
This is the validation sequence for the alpha, not a report of a completed live-stream trial. Until that run is documented, there is no measured end-to-end delay or verified busy-chat readability result to quote.
Reconnection needs its own evidence
A displayed message can remain visible after a connection drops. That does not mean new messages are still arriving. Recovery needs a fresh input and a visible update. The upstream connection also has its own lifecycle; Twitch describes keepalives and reconnect messages in its WebSocket event documentation.
We are working toward a useful recent-message view, with clear limits on how much can be shown at once. We are not promising a full moderation console, automatic reading of every message, or independent operation without the phone.
Help choose the right test
When requesting early access, describe your stream: what you do with your hands, roughly how busy chat gets and which messages you most need to notice. That gives us a concrete situation in which to test the display and connection.