Firmware & App Development

Firmware Programming & App Development – Customized Digital & Product Solutions

We have experience with the following Product Customization:

We can offer development For:

Why develop with us?

We ensure firmware reliability by following the following practices:

• We focus on coding in C for STM32 & PIC32
  • For the price to quality/performance ratio we recommend STM32 & PIC32
  • We can also develop in Javascript, Python, Lua, C++ during prototyping or Proof of Concept (PoC), but for full production, we recommend C as its optimized and robust for MCUs.

• We use generally accepted Firmware coding standards – We adhere to most of the Linux Kernel coding style. We internally audit our source code against a checklist of coding principles for firmware. We like to use designs that allow for user-friendly Over the Air (OTA) firmware upgrades.

• We build in engineering teams and cross-train.
  • Project Teams: We have a team of electronics engineers on each project. We generally have 2 firmware developers, 1 hardware developer and 1 for quality assurance (QA). Having a team speeds up debugging which we all know eats up a lot of valuable time.
  • Cross-training: most of the toughest bugs arise at when the hardware interplays with the Firmware. Cross-training helps with problem-solving. We train everyone in PCB design, PCB troubleshooting, RF, EMC, mechanical design and manufacturing. This way our team members can be aware of challenges and opportunities that exist in the other disciplines.

We do Design for Testing to ensure Quality Assurance.

QA is not about lots of testing, it’s beginning with the end in mind. We carefully and methodically define a matrix of requirements and their test procedures, so that code is compliant enough such that most testing becomes unnecessary.

By ensuring a high level of test-ability throughout development and production, we speed up validation and industrialization of our designs.

We create impeccable Documentation

At a high level, we document every project through internal Evernote-based wikis.

The most important elements of our documentation are:

– Well-built readme files for every repository, including all necessary instructions to review, compile and test the code

– Repositories management

Effective version control is a storyline which depicts the evolution and decision-making path of a project, as well as the user manual for reusable code. All source code is Doxygen compatible and all releases are properly tagged so automatic changelogs are created. We believe in the advantages of following git-flow, enforce conventional comments and implement a slightly modified flavor of semantic versioning.