Writing · Checklist
Questions to ask before you hire an e-paper hardware partner
Before you hire anyone to build an e-paper product, ask four kinds of question. Have they shipped on your exact panel? How do they get battery life, and from what measurements? How does firmware reach devices already in the field? Who owns the code and the cloud at the end? The fourteen questions below are grouped by panel, power, firmware, network, certification, cloud and commercial terms, each with what a good answer sounds like and how we answer it ourselves.
Published 2026-11-16. Written for product leads and hardware founders choosing a partner for a color e-paper device. We are one such partner, building on ESP32-S3 and E Ink Spectra 6, so the last column is our own answer. Judge it the same way you would judge anyone else’s.
Start with the general questions
The usual advice for hiring a product development firm still applies. Simplexity’s ten questions to ask a product development firm covers relevant experience, NDAs and conflicts, whether product development is the firm’s core discipline, written specifications, who is actually on the team, process and tooling, and references. Velvetech’s questions for an IoT development partner adds how deep the firm’s hardware engineering really goes, whether it has built for your industry, and its typical rates. Ask those. Then ask the e-paper ones, because that is where general embedded experience runs out.
Why e-paper is different: An e-paper panel is driven by waveforms, refreshes in seconds, behaves differently in the cold, shows only a handful of colors and holds its image with no power. Each of those changes the firmware, the content pipeline and the battery math.
The checklist
| Area | Question | A good answer | Our answer |
|---|---|---|---|
| Panel | Have you shipped a product on this exact panel? | Names the panel part number and a shipping product | Yes: Good Display 7.3″ and 13.3″ Spectra 6, in our own consumer frame |
| Panel | How do you source panels, and what is the lead time? | A direct supply line, a price per unit at your volume, a lead time | Direct supply; we quote panel price and lead time on the scoping call |
| Panel | How do you tune waveforms and handle ghosting? | Per-lot tuning, a clear-screen strategy, temperature in mind | Waveform LUTs tuned per panel lot |
| Content | How are images converted to the panel's colors? | A dithering pipeline tested on real panels, with a preview | In-browser dithering to the measured six-pigment palette, with preview |
| Power | What battery life do you expect, and from what model? | A number per refresh cadence, from measured sleep and wake current | Sub-100 µA sleep; e.g. 3,000 mAh lasts ~40 days hourly, ~7.8 months at 4/day |
| Firmware | How does firmware get updated after shipping? | A named method (OTA or USB), with signing and rollback described | USB reflash on our stack today; plan field updates explicitly |
| Firmware | What does the device show if the network or server is down? | The last good image stays; a retry and backoff plan | The panel keeps its last image with no power; the sign checks again at its next scheduled wake |
| Network | How is a new device put on Wi-Fi? | A provisioning flow that works without a developer laptop | The device starts its own setup hotspot; 2.4 GHz Wi-Fi only |
| Network | How does the device get new content? | Who initiates, how often, and what it costs in battery | The device wakes on a schedule and asks the cloud if its image changed |
| Certification | What is the certification path? | A pre-certified module, host testing still budgeted, labeling planned | Pre-certified ESP32-S3-WROOM-1 module on our 7.3″ build; FCC/CE modular path in the schematic |
| Cloud | Who hosts the cloud, and can we take it over? | Source in your org, deployable by you, or a managed option with an SLA | Next.js and Supabase, deployed under your brand or hosted by us |
| Commercial | Who owns the IP when we are done? | A signed transfer of IP and source in your repository | Full source in your GitHub org and a signed IP transfer |
| Commercial | What does a scope look like before we commit? | BOM, NRE, unit cost band at volume, week-by-week schedule | A one-page SOW with BOM, NRE, unit cost band and schedule |
| Commercial | Who builds production units? | A named route: their small batches or a DFM package for your CM | Small-batch runs by us, or a DFM package for your contract manufacturer |
Panel questions
Have they shipped on your panel?
Dev kits make e-paper look easy: a demo image appears on the first afternoon. The hard part is what happens after a thousand refreshes, at five degrees, on a panel from a different lot. Ask for the panel part number of something they have shipped, and ask to see it. Our dev kit to product checklist lists the gaps between a demo and a field unit.
Can they get panels at your volume?
The panel is usually the most expensive line on the BOM. Ask where it comes from, at what price for your volume, and what lead time. A partner who buys panels one at a time from a distributor cannot quote you a credible unit cost.
Content and power questions
Ask how images become six colors. A good partner has a dithering pipeline tested against a measured palette, and shows you a preview of what the panel will actually display before it ships. Our Spectra 6 image preparation guide shows what that involves.
Then ask for battery life as a table, not a headline. It depends almost entirely on how often the device wakes, so a partner who gives one number without a refresh cadence has not done the math. Our battery life post shows the table for our stack.
Firmware and network questions
How do updates reach the field?
This question separates prototypes from products. Some stacks update over the air, some by USB, some not at all. None is wrong for every product, but you need to know which you are buying and what it costs to change. On our stack today, firmware updates are a USB reflash; if your fleet needs over-the-air updates, that is work to put in the scope, with signing and rollback, not a checkbox.
What happens when things fail?
E-paper has a useful property here: it keeps the last image with no power. Ask what the device does when Wi-Fi is down, the server returns an error or the battery is nearly flat, and how anyone will find out. Ask how a new device joins the network without a developer present, and what the device needs from your IT team. The Wi-Fi checklist lists the network questions.
Where does rendering happen?
Some designs render on the device, some on a server. Rendering on a server and sending the finished image keeps the device simple and its battery long; rendering on the device saves bandwidth but costs power and firmware complexity. Our ESP32 vs Raspberry Pi comparison covers the trade-off.
Certification and commercial questions
- Certification: which radio module, whether it carries its own grant, and what host testing and labeling the finished product still needs
- Ownership: source in your repository, a reproducible build, and a signed IP transfer
- Cloud: who hosts it, under whose brand, and what happens to devices if the contract ends
- Scope: a bill of materials, NRE, a unit cost band at your volume and a week-by-week schedule, before you sign
- Production: who builds the first batches, and whether you get a DFM package for your own contract manufacturer
- Support: who fixes a bug in 18 months, and at what rate
For certification detail, read do you need FCC certification with a certified ESP32 module.
Red flags
- A battery life number with no refresh cadence attached
- No shipped product on the panel you plan to use
- Images converted with a generic dither and no preview on a real panel
- Firmware updates described as 'easy to add later'
- Source code kept in the partner's repository, or no IP transfer in the contract
- A schedule with no time for panel or battery testing in the cold
FAQ
What should I ask an e-paper hardware development partner first?
Ask whether they have shipped an e-paper product to real customers, on the panel you plan to use. E-paper has problems a generic embedded shop meets for the first time on your budget: waveform tuning, temperature behavior, dithering for a limited palette and long refresh times. A partner who already ships on that panel has paid for those lessons.
Who should own the firmware and cloud code?
You should, unless you deliberately choose a managed service. Ask for the source in your own repository, a written IP transfer, and a build you can reproduce without the partner. If the partner hosts the cloud, ask what happens to your devices if the contract ends.
How long does an e-paper prototype take?
It depends on how much is new. A partner adapting a stack that already ships can quote weeks; one designing panel driving, power and firmware from scratch will need months. We quote about six weeks from kickoff to a working unit on your desk, because we fork the stack that ships in our own frame.
Do I need to certify an e-paper device?
Yes, any electronic device you sell needs the right approvals for its market, such as FCC in the US and CE in the EU. Building on a pre-certified radio module avoids a full radio filing, but the finished product still has its own obligations. Ask the partner how the schematic keeps that modular path open.
What questions catch weak e-paper partners?
Ask how they handle ghosting and cold-temperature refreshes, how they convert images to the panel's palette, what the device shows when Wi-Fi is down, and how firmware gets updated in the field. Vague answers to any of those are a warning sign.