Jitoma Solutions
EN

Embedded software and firmware development for connected devices

From the firmware on the device to the phone app it pairs with, built and tested by one team.

Start a project See relevant work
  • C++
  • Rust
  • Linux
  • Python
  • REST

What we build

Firmware and device software we build

Devices fail quietly: a missed timing window, a battery drained overnight, a firmware update that bricks half the fleet. We write the C++ and Rust that runs on the device, the Bluetooth link to the phone or desktop app beside it, and the path data takes from the device up to your cloud. Our own DJI Mic Recorder app talks to DJI wireless microphones over Bluetooth on the phone: real device connectivity work, not a lab demo.

  1. 01

    Firmware for constrained targets

    Control and application firmware in C++ and Rust, sized to fit limited flash, RAM and CPU budgets.

  2. 02

    Linux-based device software

    Application and system software for Linux-based devices, from boot to the services that keep the product running.

  3. 03

    Bluetooth and wireless connectivity

    Pairing, streaming and control between a device and its phone or desktop app, the link our DJI Mic Recorder app relies on.

  4. 04

    Device-to-cloud data pipelines

    Provisioning, telemetry and configuration that move data from the device to your backend in a format it can actually use.

  5. 05

    Field firmware updates

    Update mechanisms built to survive a dropped connection or a power cut, so a bad rollout does not mean a truck roll.

  6. 06

    Logging, diagnostics and test rigs

    Diagnostics that make sense of a device already in the field, and test setups that run against real hardware.

Typical problems we solve

Decisions that shape a device product

  • Is Rust worth it, or should we stay in C++?

    We choose per component, not by ideology: C++ where an existing codebase or a vendor SDK expects it, Rust where memory safety on a network-facing or long-running module is worth the switch.

  • How do we update firmware once devices have shipped?

    We design the update path before the first device leaves the building: staged rollouts, integrity checks and a fallback image, so a failed update does not turn into a support call.

  • The prototype works on the bench, not in the field.

    We test against the actual hardware and radios you will ship, under real power and interference conditions, instead of trusting behaviour that only held up on a development board.

  • Bluetooth pairs fine in the demo and drops in daily use.

    We build the reconnection and error handling most demos skip: lost links, a backgrounded phone app and battery-saving modes are the normal case, not the exception.

Own products

We ship and run our own software, too.

Products we design, build and operate ourselves, used by real people every day. Your project gets the same care.

  • Bluetooth audio recorder

    DJI Mic Recorder

    Records from DJI wireless microphones over Bluetooth, straight on your phone, and keeps you in control of your sound.

    Independent app, not affiliated with DJI.

How we work

From hardware bring-up to firmware in the field

How every engagement runs

  • Clear scope and estimate

    You know what you get, when, and what it costs before work starts.

  • Working software early

    Short iterations with results you can see and test.

  • Transparent communication

    Direct contact with the engineers, regular updates and no surprises.

  • Support after release

    We stay responsible for what we delivered.

Start a project

Questions and answers

Frequently asked questions

  • Do you design the hardware or only write the software?

    We write firmware, control software and the connectivity around it. We work from a board you already have or one your hardware partner is designing, and we are direct about where a decision belongs with an electronics specialist instead of guessing.

  • How do you update firmware once a device is already in the field?

    We build the update mechanism into the product from the start: signed images, a staged rollout to a subset of devices first, and a fallback so a bad update does not leave a device unusable. What fits depends on the connectivity the device has, Wi-Fi, Bluetooth through a phone, or a wired service tool.

  • What happens when a device only shows problems weeks after it ships?

    We build logging and diagnostics into the firmware from day one: what to record, how much it costs in flash and battery, and how to pull it off a device that a support team cannot plug a debugger into. That is what turns a vague field complaint into a fixable bug.

  • Can the device talk to a phone app over Bluetooth?

    Yes. Our own DJI Mic Recorder app connects to DJI wireless microphones over Bluetooth on the phone, handling pairing, streaming and reconnection, the same class of problem a companion app for your device needs solved.

  • What affects the cost of an embedded software project?

    Mainly the complexity of the real-time behaviour, how constrained the memory and power budget is, how many wireless protocols and integrations are involved, and whether updates and diagnostics need to be built in from the start. A narrow first version on real hardware is usually the fastest way to find out what the rest will cost.

Contact

Tell us about the device you are building

Share what the device needs to do, the hardware you have or are choosing, and any deadline. We will reply with concrete next steps and the questions that matter most for your product.

What happens next

  1. We get back to you as soon as possible.
  2. A short call to understand your goals and scope.
  3. A written proposal with an estimate. No obligation.

Registered office

Děčínská 552/1, 180 00 Praha 8

Only this form reaches us. Your details stay with us and are never shared.

Capabilities

Other services

  • Websites

    Fast, search-friendly websites that explain what you do and turn visitors into enquiries.

  • Web applications

    Customer portals, internal tools, dashboards and workflow systems on backends built for real load.

  • AI agents and automations

    AI agents, integrations and automated workflows that take repetitive work off your team and run reliably in production, not just in a demo.

  • Desktop programs

    Cross-platform desktop applications for demanding workflows, specialized hardware and data visualization.

  • Mobile applications

    Android and iOS apps, from public app-store products to internal tools for teams in the field.

  • Consulting and architecture

    Requirements, technology choices, architecture review and delivery planning, so you invest in the right thing from day one.

  • Maintenance and support

    Updates, fixes and new features after launch, for software we built and for systems you already run.

  • Not sure which service fits?

    Describe your project and we will recommend the right approach, even if it is not us.