Solution 01 — TV, AV & Streaming

One handset for the installed base and the new box.

Viewers do not know which generation of hardware is in the room. They know that one remote should turn on the TV, switch to the soundbar and reach the streaming menu — without a manual.

Describe the project Check a device

The brief

The remote is the only part of the system the viewer actually touches.

Panel, SoC and streaming OS are chosen months before the remote brief arrives. By then the installed base is fixed, the app team has its own roadmap, and the remote has to make all of it feel like one product.

Most of the work is not the enclosure. It is code coverage, device switching logic, pairing recovery and the order of keys on a surface the viewer reads in the dark.

Where programs typically stall

IR coverage assumed from a spreadsheet instead of measured on samples
Voice key added after the ID and PCB are frozen
Pairing flow depends on an app that is not built yet
Certification testing scheduled in the final week
Key map copied from a competitor, not tested with viewers

What we build

Four decisions that determine whether the remote feels finished.

Each one is agreed and documented before tooling. If a requirement is not testable, it is not in the spec.

01 / Code library

IR coverage you can verify

We build from your device list and sample remotes, then verify each code on the actual unit. Coverage is reported as tested models, not as a claimed percentage.

02 / Radio

IR and BLE, one power path

Dual-radio boards share the key matrix and battery budget. We define which keys are IR-only, which are BLE-only and what happens when the link drops.

03 / Interface

A key map with a hierarchy

Primary viewing keys stay large and reachable. Source and setup keys move to a secondary group. The layout is reviewed as a printed template before tooling.

04 / Integration

Voice, app and pairing handoff

If voice or app pairing is in scope, we work from your existing stack or define the BLE service with your firmware team. Recovery is part of the flow, not an afterthought.

Recommended control stack

Start standard, then customize only where the product requires it.

The table is a starting point for scoping, not a fixed catalogue. Each row is confirmed against your device list and target market.

Layer	Standard path	When it becomes custom
IR link	NEC, RC-5, RC-6 plus a learned code set	Non-standard boxes or codes that must be captured from samples
BLE link	HID over GATT for standard navigation	Custom GATT service, voice transport or secure pairing
Input	Silicone keypad, 2× AAA	Capacitive touch, rechargeable cell, backlight
Validation	Functional test on the agreed device list	Drop, key-life, temperature or cleaning beyond the standard plan

Project profile

Replacing two remotes with one, without losing the old boxes.

A streaming hardware brand needed a single handset for its new device and the TVs already in customers’ homes. The program was scoped around code coverage first, enclosure second.

2 radios

IR + BLE

One key matrix, two links

38 keys

Key map

Three device groups

3 markets

Certification

EU, US, UK targets

14 weeks

To pilot

Brief to pilot build

Profile note. Durations depend on tooling, component lead times and how quickly samples and approvals arrive.

Questions

TV / AV program FAQ

Can you match a code library we already maintain?

Yes. Send the library and the device list. We import it, test a sample against real units, and report gaps before the PCB layout is fixed. Codes we cannot verify stay on the gap list — they are not counted as covered.

Do we need to supply the app for voice and pairing?

Not necessarily. If you have an app team, we integrate with their BLE service and test the handoff. If you do not, we can define the service and a minimal pairing sequence, but the app itself remains your product decision.

How do you handle certification?

We prepare the technical file, run pre-scan where the lab supports it, and coordinate with the certification body for the target markets. Final certificates are issued to the applicant. We do not list a certificate until a copy exists.

What is a realistic first order?

Pilot builds typically start in the low thousands so the key map and firmware can be tested in real homes. Mass production quantities are agreed after the pilot, not assumed at the quoting stage.

Start a project

Send the device list. We will send back the gaps.

Tell us what has to be controlled, which markets you ship to and when the pilot needs to land.

Start a project See product platforms

Typical reply within one business day