Matter firmware development means implementing a standardized, IP-based application layer on top of Thread or Wi-Fi so that a single device works with every major smart home ecosystem without a vendor-specific bridge or cloud account. In practice it changes three things about your firmware project: you adopt a defined data model instead of inventing your own, you must support a secure onboarding flow, and you take on a certification step before you can carry the logo. The payoff is that one build works across the platforms your customers already own.

Why Matter changed the calculation for smart home products

Before a common standard, a connected home product had to pick winners. Each ecosystem meant a separate integration, separate certification, separate cloud plumbing, and separate maintenance — multiplied by however many platforms you wanted to support. Small companies simply chose one and lost the rest of the market.

Matter replaces that with one application layer. It runs over IP, defines device types and their capabilities in a shared model, and handles security and onboarding uniformly. Local control also becomes the default rather than an exception, which means the light still turns on when the internet is out — a real, marketable reliability advantage.

What the standard actually asks of your firmware

Matter is a specification, not a library you drop in and forget. The main work areas:

  • The data model. Your device declares endpoints, clusters, attributes, and commands drawn from the standard device types. Choosing the right type — and resisting the urge to invent custom clusters — is what makes your product behave predictably in every app.
  • Transport. Either Thread, for low-power battery devices in a mesh, or Wi-Fi, for mains-powered devices with more bandwidth. This choice drives your radio, antenna, and power architecture.
  • Security and identity. Every device carries cryptographic attestation credentials that must be provisioned during manufacturing and stored so they cannot be extracted. This means secure storage in silicon and a factory provisioning step, not a file in flash.
  • Fabric and multi-admin handling. A Matter device can belong to several ecosystems simultaneously. Your firmware has to manage multiple fabrics, credentials, and access control lists correctly, including the reset path when a user sells or moves the device.
  • Persistence and recovery. Network credentials, bindings, and scene state must survive power loss and firmware updates without stranding the device.

Choosing a platform: not every microcontroller qualifies

Matter has real resource requirements. The stack, TLS-class cryptography, and IPv6 networking need substantially more flash and RAM than a simple Bluetooth sensor, plus hardware crypto acceleration and secure key storage to be practical.

The sensible route is a chipset from a vendor with a maintained Matter SDK, a certified reference design, and a documented provisioning flow. That choice constrains everything downstream, so make it early — the same reasoning we lay out in how to choose a microcontroller. Most Matter SDKs sit on a real-time operating system, so the tradeoffs in FreeRTOS vs Zephyr apply directly. For devices with a heavy interface or gateway role, the microcontroller versus embedded Linux question comes up as well.

Commissioning: your product's first impression

Commissioning is how a device joins a home. The user scans a code, the ecosystem app discovers the device over Bluetooth Low Energy, verifies its attestation, hands over network credentials, and the device joins the Thread or Wi-Fi network. It should take under a minute and require no account creation.

Firmware quality shows up here more than anywhere else. Things that go wrong in the field: onboarding codes that do not match the label, attestation certificates not provisioned in production units, BLE advertising that stops too early, devices that cannot rejoin after a router reboot, and no clear factory-reset gesture. Test commissioning on multiple ecosystems, on congested networks, and at the edge of radio range — not just on a clean bench.

Radio design is half the job

Matter is a software standard, but the customer experiences it as radio reliability. A Thread or Wi-Fi device inside a plastic enclosure next to a metal bracket and a switching power supply will underperform its datasheet unless the RF layout was done deliberately. Plan antenna placement, keep-out zones, and ground reference at schematic time, as covered in antenna design for wireless products.

Certification, testing, and the long tail

Two separate approval tracks apply in the US, and both are educational context here rather than regulatory advice — confirm requirements for your specific product with a qualified test lab.

  • Matter certification requires membership in the standards organization, testing against the conformance suite at an authorized lab, and passing interoperability testing before you may use the logo.
  • Regulatory approval is unrelated to Matter and unavoidable for any intentional radiator sold in the US. See FCC certification for electronic products and budget for EMC testing.

Budget for both time and money: certification is a scheduled, lab-dependent activity, and re-testing may be required after significant firmware changes. Costs typically run from the low thousands into the tens of thousands of dollars depending on device complexity and how many test cycles you need.

Then there is life after launch. The specification evolves, ecosystems update, and security patches are not optional for a device on someone's home network. A robust OTA update mechanism is a launch requirement for a Matter product, not a later feature.

Does your product actually need Matter?

Matter earns its keep when the product is genuinely part of a home system — lighting, plugs, sensors, thermostats, locks, blinds, appliances — and when working with the customer's existing app is a buying criterion. It is overhead you do not need for an industrial device, a wearable paired to your own app, or a product whose value is entirely inside a proprietary experience. For those, a direct BLE or Wi-Fi design is simpler and cheaper.

Either way, expect the firmware effort to exceed a simple connected device. Factor that into your firmware development budget and overall product cost, and see the embedded software pillar for how the pieces fit together.

Considering Matter for a smart home product? Tell us about the device through our contact form and we will assess whether the standard fits your use case and what the firmware and certification path would involve.