Nordic Design Partner

Generalize problems, reuse solutions

Our philosophy is quite simple: By basing your product on ready-made, well-tested, reusable building blocks, the time you have to spend on things unrelated to your idea is minimized.

Let's walk through a typical project setup!

Systematization and planning

1Systematization and planning

The system is mostly about avoiding dead ends: choosing the right connection, power budget and architecture without painting yourself into a corner. With solid experience in modern IoT development, we've seen it all and can help you find the right one no matter where you are in the idea stage.

Start building firmware ASAP

2Start building firmware ASAP

We don't have to wait for ready-made hardware to start hacking. We've developed our Kite™ development boards to provide a platform for production grade prototyping, which we combine with PMod breakout boards (and often a 3D printed chassis) to get something in your hands in no time.

Parallel hardware design

3Parallel hardware design

This is how we try to think when we make hardware:

  • Communication paths must be open - firmware and hardware are developed side by side, not in turn.
  • Dull jobs must be automated - we build hardware as we have built software for 20 years: scripted, version managed and repeatable.
  • Changes should happen quickly - nimble decisions where iterations feel like progress instead of setbacks.
Cloud-ready from day one

4Cloud-ready from day one

You don't have to wait months for a ready-made cloud either - Uncomplicated Cloud™, our cloud offering for rapid prototyping, takes care of the entire communication chain from device to backend. Power-efficient, memory-efficient and easy to use, translated into an API all cloud developers are familiar with - completely automatically and of course without compromising data security.

Out in reality

5Out in reality

When everything works on the desktop, it's time for the only test that matters – reality. This is where observability and remote updates help you refine - or completely question - your assumptions. When it's quick to get started, it's also quick to rethink.

Iterate

6Iterate

IoT products are never finished. We know that from the beginning, so we build to be able to change direction. Requirement specs are made to be broken!

Our process is a loop: discussion, implementation, CI/CD, HIL, FOTA, monitoring – and back to discussion again. Everything is connected, so that change becomes part of the flow, not an interruption.

Industrialization and manufacturing

7Industrialization and manufacturing

Anyone who has built anything knows how long the step from "finished design" to "finished product" can be. Here too, we try to use the same philosophy: generalize problems, reuse solutions and let the machines do the boring work. We call the initiative Prod-To-Go - read more about it here.