In this article
Custom chip development for products such as audio equipment, wearables, cameras and connected home devices. These applications often balance unit cost, energy use, integration and user-facing performance.
Optimize the complete product
Consumer electronics ASICs can integrate processing, interfaces, sensing or power-related functions in devices used by many people. Their value often comes from a combination of energy, size, recurring cost and user experience. Begin with the product's actual usage patterns, including sleep, wake-up and occasional peak activity. A design optimized only for continuous operation may miss the states that dominate battery life or responsiveness. Define what the user experiences and translate those expectations into measurable hardware and software requirements.
Integration versus flexibility
Integrating several functions can reduce board complexity, but it also makes their lifecycle more closely connected. A change in one interface or feature can affect the entire chip revision. Decide which behaviors should remain configurable in software and which are stable enough for fixed hardware. Consider how the device will support accessories, manufacturing variants and future software updates. Flexibility has a cost, so it should be allocated to plausible product changes rather than added indiscriminately or removed solely to minimize an early area estimate.
Volume economics and manufacturing
Expected production volume affects how non-recurring development costs compare with recurring component costs. Use realistic scenarios rather than assuming a successful product launch. Include packaging, test, yield learning, validation and the surrounding bill of materials. A smaller die may not reduce total product cost if it requires a more expensive package or additional external components. Production test also needs a plan that balances coverage and throughput. Manufacturing requirements should influence design decisions early enough to avoid expensive changes after the layout is nearly complete.
Real-world experience
Startup time, interface recovery, thermal behavior and firmware updates can strongly affect product quality. Test common usage sequences and unusual events such as interrupted power, failed communications or an incomplete update. Diagnostics should support factory testing and customer-support investigations without exposing unnecessary internal access. Where the product handles personal data, security and privacy requirements should be part of the architecture. A successful chip supports the complete product lifecycle, from manufacturing and first setup to routine use, updates and eventual retirement.
Questions about consumer ASICs
Is an ASIC always cheaper than standard components?
No. The answer depends on volume, integration benefits, development investment, manufacturing costs and product changes. Compare complete scenarios rather than one component price.
Should every product feature be fixed in hardware?
No. Functions likely to evolve may benefit from software or configurable hardware. The architecture should balance efficiency with the flexibility needed for the expected product roadmap.
Derive chip requirements from system behavior
Begin with the product's intended tasks, users and environment. Describe the signals it receives, decisions it makes and outputs it produces. Include timing, energy and operating limits where they matter. Distinguish requirements that the chip can satisfy directly from those that depend on software, sensors, power supplies or other components. This prevents a good component specification from being mistaken for complete product performance. A useful system review identifies the boundaries and assigns an owner to each assumption that crosses them.
Allocate integration and flexibility
Choose which functions belong in fixed logic, software or external devices. Integration can reduce board complexity and communication overhead, but it also connects the functions' revision and manufacturing lifecycles. Preserve flexibility for plausible product changes without assuming that every requirement can remain open indefinitely. Consider configuration, firmware and interface compatibility alongside area and power. The architecture should explain why each function is integrated and what evidence supports the choice. A custom chip is most useful when it addresses a concrete product constraint rather than simply increasing the amount of circuitry on one die.
Exercise realistic operating cases
Test normal use, startup, interrupted power, invalid inputs and the relevant error or recovery sequences. Use representative workloads and environmental assumptions. Include software-visible behavior so the complete product can detect and respond to important conditions. Measurements should state the setup, configuration and product boundary. A chip-only benchmark can answer a narrow question, but it may not represent what a customer experiences. Preserve reproducible tests and distinguish measured results from estimates while the design and evaluation platform are still evolving.
Plan manufacturing and support
Include package, test access, diagnostics and expected production life in the development plan. Discuss traceability and change control according to the application's actual needs. If qualification or regulatory requirements apply to the finished product, coordinate them with the responsible product team; the presence of an ASIC does not establish compliance. Consider how firmware, supplier changes and field issues will be managed over time. A supportable design connects technical behavior with the information and responsibilities needed to manufacture, evaluate and maintain the product after the first successful demonstration.
A practical cross-discipline review
Before committing the next stage, bring the design, verification and product-engineering owners together around the same revision. Confirm the assumptions that pass between them: operating modes, interfaces, test access and the evidence expected at release. List unresolved issues with a responsible owner and a concrete way to close them. An open question is easier to manage when its consequence is understood than when it is hidden inside a general progress estimate. Preserve the decision record so a later change can be evaluated against the original reasoning. This review is useful even for a narrow specialist task, because the surrounding product still determines whether the delivered result is usable.
Include the receiving team's acceptance question in the review: what must be demonstrated before this result can be used safely in the next engineering stage? Agree how that demonstration will be recorded and how a subsequent change triggers a focused reassessment of the affected evidence.
Explore the related Avnet offering or discuss your project requirements.
