- 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 V1Developers 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 DevelopmentThe 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.