Building a Better Display Local Device
What began as a search for a simple Android box became a months-long process of testing hardware, evaluating manufacturers, customizing firmware, and building a genuinely plug-and-play digital signage player.
Reliable · Economical · Branded · Customizable
Our goal sounded straightforward: create a reliable and economical device that customers could plug in and use, while giving us complete control over its configuration and the Display Local experience.
Until now, we used an off-the-shelf Onn 4K streaming device from Walmart. We provisioned each unit to transform it from a consumer streaming product into a plug-and-play digital signage player. It worked well, helped us grow, and gave us an effective way to get Display Local into customers' hands.
But as we expanded, the limitations of depending on a retail product became increasingly important. It was time to move from adapting someone else's device to creating a hardware experience of our own.

The starting point
A good solution with an uncertain future
We relied on a specific Onn model running a particular version of Android firmware. Our provisioning process required system-level customization, which meant an unexpected firmware update could potentially change or remove capabilities we depended on.
There was also no guarantee that the preferred model would remain available. Consumer electronics change quickly. A retailer can discontinue a product, introduce a revised model, or ship new firmware without considering how a specialized business has adapted that device.
The devices also carried someone else's identity. The case, onboarding screens, and startup sequence were designed for a consumer streaming product—not Display Local. That didn't prevent the player from working, but it made the experience feel less cohesive than we wanted.
We wanted control over the hardware, firmware, branding, and customer experience—not just a temporary supply of devices that happened to work today.
The search
Going down the hardware rabbit hole
The process probably looks different for a large company ordering thousands of units. As a scrappy startup, however, you have to approach it differently. You research, ask questions, order samples, solve unexpected problems, and learn as you go.
Because the Display Local application and mobile device management system were built around Android, we began by looking for Android media boxes. That still left us with a huge range of Android versions, chipsets, memory configurations, manufacturers, and firmware options.
Starting with the marketplaces
Our first stop was Alibaba and AliExpress. These marketplaces are useful for discovering products, but buying through a listing did not solve our long-term problem. Communication was often limited, product details could be unclear, and there was no certainty that a seller—or the exact configuration being advertised—would remain available.
Amazon presented a similar issue. Many generic Android boxes were available, but the source and long-term consistency of the hardware were difficult to establish. Prices were also often two or three times higher than the underlying hardware should cost.
Our real objective was not simply to find a box. It was to establish a repeatable hardware configuration and a relationship that gave us visibility into future changes.
Going to the source
Finding the right manufacturing partner
Once we determined that marketplace listings were not a dependable long-term strategy, we began researching the manufacturers behind these devices.
Most manufacturers in this space are located in China. That made communication, sampling, and testing more involved. Language differences had to be navigated carefully, and international shipping made every sample significantly more expensive than its unit price suggested.
We identified several reputable manufacturers and began discussing chipsets, memory, storage, firmware, branding, minimum order quantities, and long-term availability. Over several months, we narrowed the field to two manufacturers we trusted and ultimately selected one partner for our initial production devices.
What mattered in that decision
Clear, consistent communication
Reasonable sample quantities
Support for smaller initial orders
Hardware consistency
Competitive pricing
Firmware expertise
Customization capabilities
Long-term product availability
Defining the device
Balancing performance with economics
We eventually focused our search on two Amlogic systems on a chip: the S905W2 and S905Y5. Our target configuration included 2 GB of RAM and 16 GB of storage.
There are less expensive chipsets and memory configurations, but our testing showed noticeable compromises. Video could lag, animations could become sticky, and the overall experience felt less polished. More expensive configurations performed well, but the improvements were not noticeable enough in everyday signage use to justify their additional cost.
Amlogic S905W2
A proven digital signage chipset that delivered reliable real-world performance, supported the required customizations, and fit our preferred compact device format.
Amlogic S905Y5
Technically a little faster, but the difference was not noticeable during typical use. It also cost slightly more and came in a larger form factor.
We completed the firmware customization required for both chipsets, so the final decision came down to practical value. The S905W2 gave us the performance we needed without charging customers for specifications they would be unlikely to notice.
Beyond the specification sheet
Testing for the real world
Selecting a processor and memory configuration was only the beginning. Specifications can tell you what a device should do. Testing tells you how it actually behaves.
TEST 01
Wi-Fi reliability
We evaluated how consistently each device connected, remained online, and recovered from interruptions.
TEST 02
Video and animation playback
We looked beyond specifications to see how content actually performed in a real digital signage environment.
TEST 03
Continuous operation
We monitored heat and stability while devices operated for extended periods.
TEST 04
Automatic application launch
The Display Local application needed to launch predictably without unnecessary customer interaction.
TEST 05
Remote management
We tested device management and over-the-air updates so deployed players can be supported remotely.
The finished experience
What plug and play should actually mean
Previously, preparing an Onn device for a customer took roughly 30 minutes. We had to work through the consumer onboarding process, connect a Google account, apply our settings, and complete the provisioning required to turn it into a signage player.
Our new device reduces that process to a minute or two. The factory configuration already reflects how the device will be used, so our team can prepare deployments faster and more consistently.
The startup experience
01
Plug it in
Connect the device to the display, power, and network.
02
Display Local starts
The branded startup animation appears automatically.
03
Content takes over
The Display Local application launches and begins doing its job.
The physical device now carries Display Local branding, and that identity continues through the boot sequence and into the application. The result is not only faster to deploy; it feels like one complete product from the moment it is powered on.
The economics of hardware
Why scale changes the calculation
Ordering a single sample from overseas can look almost ridiculous on paper. The device itself may be reasonably priced, but shipping, customization, and import costs can easily outweigh the cost of the hardware.
That changes as order quantities increase. When we order 10, 20, or 50 devices at a time, the fixed costs are spread across more units. The economics begin to make sense, and a customized device becomes competitive with—or more economical than—buying generic hardware through retail channels.
Shipping costs, tariffs, lead times, and minimum order quantities now form part of our planning. These details may never be visible to customers, but managing them carefully helps us maintain dependable supply and sensible pricing as Display Local grows.
What customers gain
The invisible work behind a simpler experience
Most customers will never need to think about firmware versions, manufacturing relationships, chipset comparisons, or international shipping. That is the point. We did this work so the device itself can fade into the background and simply run the content it is given.
More consistent hardware
A defined hardware configuration gives new deployments a dependable and repeatable foundation.
Greater firmware control
We are less exposed to unexpected retail firmware changes disrupting our provisioning process.
Faster setup
Factory customization reduced hands-on provisioning from roughly 30 minutes per device to only a minute or two.
A polished experience
The device, startup sequence, and application now feel like one cohesive Display Local product.
Easier support
A known hardware and firmware configuration makes troubleshooting more consistent.
A path forward
Our manufacturing relationship gives us a foundation for testing higher-performance and premium configurations.
What comes next
A foundation we can continue building on
We now have a direct manufacturing relationship and a defined hardware and firmware configuration. That gives us far greater consistency, along with better visibility into future component or firmware changes.
The S905W2 configuration gives us the balance we were looking for: dependable performance at an economical price. It also gives us a starting point for testing higher-performance chipsets, additional memory, and premium device options in the future.
This process took months of research, conversations, samples, testing, firmware work, and plenty of trial and error. But the outcome is more than a new Android box. It is a device selected and customized specifically for Display Local and the customers who depend on it.
Customers should be able to plug in their Display Local device, see it come to life, and trust it to keep working.

