Application logic
Device behaviour expressed as explicit states and transitions, so the product is predictable in unusual conditions as well as normal ones.
T · [CLIENT TO PROVIDE] E · [CLIENT TO PROVIDE]
Overview
Embedded application software carries the product logic: what the device does, in what order, with what data, and how it presents itself to users and to other systems. It is where most product requirements actually land.
The constraint is that it runs on a platform with finite memory, limited processing headroom, a power budget and often an unreliable connection. Patterns borrowed from server or desktop development frequently do not survive that environment.
We design the software around the constraints: predictable memory use, bounded work per cycle, explicit state handling and data structures sized for the platform. The supporting tooling — configuration utilities, diagnostics, production test software — is treated as part of the deliverable rather than an afterthought.
Software scope
The layer that turns a working board into a product that behaves correctly.
Device behaviour expressed as explicit states and transitions, so the product is predictable in unusual conditions as well as normal ones.
Acquisition, buffering, storage and transmission of device data, sized for the memory, bandwidth and power available.
Parameter storage, defaults, validation and safe recovery, so a misconfigured device can be brought back rather than replaced.
Service interfaces, production test software and configuration utilities that let manufacturing and support teams do their jobs.
Interfaces to gateways, applications and backends, with behaviour defined for the connection being unavailable as well as present.
Practical measures appropriate to the platform: credential handling, update integrity, interface exposure and data at rest. Formal certification scope: [CLIENT TO PROVIDE].
Constraint
Approaches borrowed from server or desktop development assume memory, processing headroom and a reliable connection. Embedded platforms offer none of those by default.
So the software is designed around the constraint: predictable memory use, bounded work per cycle, explicit state handling and data structures sized for the device.
Delivery approach
Built in slices that can be demonstrated on hardware, not in one long integration phase.
Stage 01
Operating states, data flows, configuration parameters and external interfaces defined before implementation.
Stage 02
Memory, CPU and bandwidth allocated deliberately, so the software has room to grow without a redesign.
Stage 03
Functionality built in slices that run on real hardware, each demonstrable rather than theoretical.
Stage 04
Configuration, diagnostic and production-test utilities developed alongside the device software.
Stage 05
Behaviour verified on hardware, including degraded conditions: lost connectivity, low power, invalid configuration.
Stage 06
Versioned builds, release notes, update packaging and documentation for support and manufacturing.
Applications
Anywhere the device has to do something more interesting than move bytes.
FAQ
How this layer is usually scoped alongside firmware and hardware.
We use firmware for the layer closest to the hardware — drivers, timing, control — and embedded software for the application layer above it. In practice they are delivered together, but separating them keeps the architecture clean and testable.
Yes, where it is in scope. Production test software, configuration utilities and service interfaces are often the difference between a design that can be manufactured smoothly and one that cannot.
Yes. We implement the device side of the interface and work to your API or protocol. If the interface is not yet defined, we can help specify it from the device constraints outward.
That case is designed, not discovered. Buffering, retry behaviour, local operation and recovery on reconnect are specified as part of the behaviour model.
Related
Describe the behaviour, the data and the platform constraints. We will propose a structure that fits all three.
Device control, drivers and real-time behaviour.
Open →02System architecture across hardware and software.
Open →03Board support, kernel and userspace engineering.
Open →04Provisioning, management and secure updates.
Open →05Sensing, connectivity and device data end to end.
Open →Next step
Tell us what the product has to do and we will tell you what engineering it needs.