From Circuit Board to Cloud, Delivered by One Team
XTELL takes on every layer a connected product needs: the board, the firmware, the Linux board support, the device interface, the mobile app and the backend the devices report to. One brief, one team, one schedule - or just the layers you need.
XTELL is a product design and development company that takes a connected product across every layer it needs - the board, the firmware, the Linux board support, the interface on the panel, the phone app and the backend the devices report to. One brief, one team, one schedule.
The case for this is not that any single layer is better done here. It is that the expensive failures in connected products live between layers, and a vendor who owns only one of them cannot fix those. A stream that drops could be the camera, the broker or the app. A device that will not pair could be the firmware state machine or the provisioning flow. When four suppliers each own a piece, diagnosis becomes negotiation.
The 433MHz security system is the whole argument in one project: STC32G128K terminals on FreeRTOS, an IPC camera, a Flutter app for iOS and Android, and a NestJS backend running PostgreSQL, Redis, an EMQX MQTT broker and ZLMediaKit. Every layer written by the same team, so a fault anywhere in it gets traced in one sitting.
You do not have to take all of it. Most engagements are partial - existing hardware that needs an app and a backend, an existing platform that needs new device firmware, a board that needs an FPGA and the logic to go on it. The individual layers each have their own page.
Engagements run open or closed. Under an open engagement design data transfers to you and your team carries the product forward independently; under a closed one we retain the design and supply finished hardware on an ongoing basis. Both are normal, priced differently, and settled at quoting time rather than at delivery.
STC32G128K terminals on FreeRTOS with an IPC camera, a Flutter app for iOS and Android with QR provisioning and RTSP video, and a NestJS backend with PostgreSQL, Redis, EMQX MQTT and ZLMediaKit - one team across all of it.
Tina-Linux on R528 with HTTP file transfer and WebSocket real-time control, GCODE dispatch, five UART channels plus GPIO and USB peripheral drivers.
Native Android touch interface for a medical ultrasound console, communicating with the imaging device over the M8 Touch protocol.
What the product does, which layers it needs, and what the constraints are.
Silicon, connectivity, power and backend decided together rather than in sequence.
Hardware, firmware, app and backend developed in parallel by one team.
The layers brought together early and often, since this is where products fail.
Iteration to a production-ready design with full documentation.
No, and most clients do not. Partial engagements are normal - existing hardware needing an app and backend, or an existing platform needing device firmware. The value of one team is highest when the layers have to be debugged against each other, which is not every project.
Per layer we are not cheaper than a specialist. The saving is in integration time and in the diagnosis that does not turn into a dispute between suppliers. On products where the layers interact heavily that difference dominates; on simple ones it may not, and we will say so.
Depends on the model. Under an open engagement design data transfers to you and your team carries the product forward independently. Under a closed one we retain the design and supply finished hardware. Both are normal here and priced differently - tell us early which fits your plan.
For a connected product with hardware, firmware, an app and a backend, typically four to nine months from definition to production-ready, with hardware revisions being the pacing item. Partial engagements are much shorter. We schedule against your actual scope rather than a template.
Contact us for customized solutions and quotes