Get Your IoT Prototype from 0 to 1 Faster: Blast Through Technical Glass Ceilings with These Tips
Until recently, the process of building an IoT prototype has been convoluted. You have an idea. You grab the hardware you need. You build a V1 concept. You bring it to life on a WiFi network. It works—great. But come time for deployment, the transition from WiFi to cellular networks has the potential to become bumpy and cause development delays.
For a smooth transition from idea to scalable, functional product, you need to be able to figure out the nuances in the earliest stages. What if you’re building an early version of a pump monitoring system? Or perhaps a residential solar monitor? Every idea starts as a seed before deployment. The earlier that testing and quality control begins, the more resources (time, money, brainpower) that developers save.
Why IoT Developers Are Stuck
It doesn’t make sense to pay for an expensive cellular bandwidth plan during product testing stages. Builders take on immense risk by signing up for long-term commitments and data plans that may ultimately turn useless. So developers use WiFi to build V1s instead.
The task becomes harder in organizations with extensive R&D operations. Connectivity challenges stifle open dialogue and bi-directional knowledge sharing between engineering teams. WiFi and closed-ecosystems are the arch-enemy of IoT engineering.
How to Get Un-Stuck – Prepare to take the path of least resistance
That’s why big companies prefer the Raspberry Pi and Beagle Boards for prototyping. Organizations can bring in developers with any skill set to develop a prototype. When the product goes to market, teams can bring in analog engineers, embedded engineers, and firmware engineers with little friction.
But connectivity challenges still remain for building certain IoT projects over WiFi – particularly if it’s a project that isn’t meant to be near a WiFi hotspot location. WiFi also requires additional configuration that may cause headaches during deployment, just think about everytime you have to ask someone for a WiFi password. That’s where cellular comes in with instant connectivity.
Hologram recently announced the release of Nova, an open-source USB cellular modem built for the developer community; everyone from makers to system architects. Nova and the Hologram Python SDK makes cellular connectivity extremely intuitive for Single Board Computers (SBC) like the Raspberry Pi family, Beagle Boards, CHIP, and Debian based systems.
It’s for people who want to prototype and later on integrate the exact same modem into their Printed Circuit Board (PCB) design. The General Purpose Input Output (GPIO) pins are exposed, everything is unlocked. People can code with it. But the even-more practical part of Nova is that it comes with a software developer kit that developers can install on a Raspberry Pi. This ecosystem makes interacting with a device’s modem simple. It abstracts away complexities with a tool chain by developers, for developers.
- To learn more about the Nova, read this blog post
- To learn more about the Nova’s open source commitment, read this blog post
- Get started with the Nova starter kit here
Iterate your way to a V1
Developers are more than aware that paths from 0—> 1 aren’t steps. They’re journeys. And complex ones. Even with straightforward technologies and support from cross-sector open source communities, prototypes and deployments can tank.
Any developer who builds a product from scratch faces risk and uncertainty, particularly in a new technical ecosystem like the Internet of Things, in which there are more questions than answers. How can companies ensure that devices are safe, reliable, and adaptable to ever-evolving technology stacks?
There’s a simple mind trick—from the first moment that you create a blueprint, whether on paper, via Legos, or a hardware puzzle. You need to connect a lot of different things together. Here are some tips that the Hologram team recommends.
- Break stuff. See how often your prototype malfunctions at every step of development. Refine accordingly.
- Isolate different parts of your prototype. In other words, this is your part-2 to breaking stuff. See what’s working and what isn’t. Keep breaking stuff until every single component does its job reliably.
- See how much power you’re consuming. Figure out why and start thinking of ways to reduce your power consumption. This will be the key areas in which you’ll need to iterate for a large-scale deployment.
- Don’t optimize too early. Focus on developing your basic proof of concept. Make sure that you’ve captured your vision and product/market fit for what you want to build.
- Use basic components for your prototype. You can always upgrade later. Build your prototype as quickly as possible and get it working on cellular (it’s easy to get on the Hologram network).
- Build with scalability in mind. Consider using cellular to test your product and save yourself the headache of unexpected hiccups with WiFi.
- Analyze. Look at how much data you’re using. Figure out potential cost sinks that are likely to arise. Use the prototyping stage to architect a way to get your costs down, long-term.
- Test integrations. Identify potential problems and iron out points of friction sooner rather than later.
- Get feedback. This step will be most critical. Your customers can help you create a better product while saving you time and resources. Gather as much feedback as you can, detect patterns, and focus on building the features that are most valuable to your customer base.
Process + Software + Hardware = Streamlined IoT Development
The first line of code that you write and the first components that you choose should set you up to scale. Don’t let bandwidth constraints stand in your way. If you’re looking to get started with an idea to build, check out our projects hub.