How to select the right IoT hardware: From prototype to production

IoT development boards and modules are at the center of every connected product. As IoT has developed, the variety and technical capabilities of these boards has only become more complex. When building an IoT product, you you’ll want to start with a simple prototyping kit, but as you progress through the hardware development and design process, you’ll need to invest in hardware boards that are designed for scaling and manufacturing.

But what is the difference between prototyping and production hardware? This article aims to clean up some of the noise and make it easier for you to choose the right hardware solution for your IoT product.

What is the difference between prototyping and production hardware?

In general, you can easily differentiate between prototype and production hardware based on these features:

Prototyping hardware is optimized for:

  • Flexibility – usually breadboardable and has an open SIM card slot
  • Affordability – low cost
  • Modularity – compatibility with other hardware ecosystems
  • Ease of use – can be setup in minutes and comes with tools
  • Beginner audiences – content and examples optimized for beginners

Mass production hardware is optimized for:

  • Reliability – Has SMT(surface-mount-technology) components, can withstand extreme temperatures, and comes with hardware warranties
  • Manufacturability – pick and place machine ready
  • High volumes – can be ordered through a wholesale store
  • Ease of integration – should have complete product certifications
  • Advanced audiences – comprehensive datasheets and application notes

Prototype & production hardware examples

For instance, Particle produces three basic kinds of hardware – Development kits (DKs), Evaluation kits (EVKs), and Mass production modules (MPMs). These are defined below:

particle-photon.jpg

Development kits (DKs)

Development kits are breadboard friendly and optimized for expandability, modularity, and ease-of-use. As a result, they can be used for scaling depending on the use case and application, but maybe best used as short term PoCs in friendly environments.

  1. Intended use – Useful for iterating/prototyping hardware and firmware systems quickly. It provides a quick start solution and gets an IoT project rolling.
  2. Features – USB connectivity, ecosystem of hardware accessories, breadboard-able headers, RGB status LED, on-board antenna, affordable costs
  3. Audience – Hobbyist developers, engineers very new to hardware
  4. ExamplesPhoton, Electron

e-series.jpg

Mass production modules (MPMs)

Mass production modules are optimized for deployment in a mass production product, not for development. These are the real deal, intended for deployment for 5-10 years in hostile environments and small spaces. These products have little utility until they are soldered into your end product.

  1. Intended use – Deployment in a mass production product
  2. Features – Certifications, hardware warranty and support, environmental robustness, optimized for size and manufacturability
  3. Audience – Companies manufacturing products at scale
  4. ExamplesP0 / P1 / E-Series MPMs

eval-kit.png

MPM evaluation kits (EVKs)

MPM Evaluation kits are expansion boards for mass production modules and allow you to develop, iterate, and debug your IoT solution quickly and easily. In other words, they provide a friendlier development experience for mass production hardware solutions. They have a MPM soldered to them, and in many ways can act as a good reference design.

  1. Intended use – Companies designing a product for deployment at scale, companies iterating from DKs to MPMs. Useful for iterating and refining production firmware in the context of production hardware (MPMs).
  2. Features – Largest number of GPIO and peripherals, large/comfortable debugging-optimized board layout, application notes and professional documentation
  3. Audience – Professional engineers who are comfortable designing custom circuit boards, companies with intentions to deploy at scale
  4. ExampleE-Series Evaluation Kit

Other factors to consider when choosing IoT hardware

When you’re sourcing hardware for prototyping or production, you should also look at the platform, tools, and support that comes with it:

1. Consistent platform, infrastructure, firmware, and development tools

You’ll want to continue using the same cloud infrastructure and development tools as you scale. Switching between different hardware designs is enough of a task, you don’t want to carry this over to the software you are using. The same firmware application, when compiled on your DKs and MPMs, should perform exactly the same way. There should never be a need to tweak or modify the firmware application to get it running on a MPM.

2. Domain experts & support

When selecting a hardware-solution, it’s also important to consider the community surrounding it. Hardware solutions with limited adoption will have fewer resources available to aid you in development. For example, Particle’s development kits have a large developer community surrounding it, which makes it easier to find information and support when needed. If you’re deploying at scale, Particle also offers engineering services that help you build your IoT product from concept to market.

3. Ease of deployment

You want to be able to get your product up and running as quickly as possible. When sourcing hardware, check the articles and documentation that comes with it. Having these resources at the ready will make it easy for you to get your questions answered immediately.

The bottom line

When sourcing prototyping and production hardware, you want to examine its accessibility, affordability, integrations, and manufacturing features. Whether you’re prototyping or building a scalable IoT product, you want to choose hardware that offers a consistent platform environment and ease-of-deployment.

Author Bio

Technical Content Writer at Particle - Discovering how the world is using real IoT one story at a time.

Leave a Reply

Your email address will not be published. Required fields are marked *