(This blog post is part of a 5 part series, titled “How to launch IoT devices”. It will cover the key choices and concerns when turning bright IoT ideas into a product in the market. Sign up to the webinar on How to launch IoT devices to get the full story, all in one place.)
Part Two can be found here: How to launch IoT devices – Part 2: Select the right hardware and foundations
Part Three can be found here: How to launch IoT devices – Part 3: make vs buy decisions
You have a budget and a bright idea. How do you turn that into a revenue generating and market capturing product? How do you escape “Pilot Purgatory” and the volume of decisions that need to be made about IoT before day-0?
This blog series distills the learnings from over 30 Canonical project summaries and case studies from IoT launches. You’ll learn about the key design decisions and choices to consider. The goal is to increase the velocity of your technical decision making. It will show how Ubuntu Core and its suite of products are designed to turn IoT launches into a 5-step journey that can take as little as 2-weeks.
Need for speed: How e-commerce launches fast
This decade, IoT will become a trillion dollar industry. Currently it sits between $200 and $250 million, so there is a lot of planned growth. Best of all, the projected value is still up for grabs by new players in the market, i.e. you.
Contrast this sentiment with McKinsey’s finding that 85% of IoT products are still in pilot, one year from starting. 25% take more than 2 years to release. To find out why, let’s compare IoT with another “modern” business model: e-commerce and retail.
Generally speaking*, the steps to launch a retail product are outlined above. The internet’s impact is that each stage is, at best automated (Amazon, Sourcify, Swipe) and at worst commoditised (Ali Baba, East-Asian manufacturing and wholesale, 3PL). The result is a de-risked, faster and cheaper retail product launch.
So why are so many IoT business ideas, stuck in Pilot Purgatory?
Automated and Commoditised launch of IoT devices
To answer this question, I looked at Canonical’s internal database of projects, to see how successful IoT devices are launched, as well as the problem statements customers came to us with. This covers +30 business cases, project summaries and case studies.
A few things stood out as different (but similar) to e-commerce and retail, as seen below.
A decision on what IoT hardware to use becomes a decision on what your entire software stack needs to be. Parts of that stack might not work together or with the operating system, apps or your current CI/CD while remaining reliable, robust and secure.
Best case scenario: Select hardware that is known to work with a full-featured IoT stack, now and in the future.
Making a portal is not about finding a GUI that a human user/customer can easily access (as is the case with retail). IoT devices are typically unmanned for much of a device’s life. While fleet management vendors exist, it is difficult to get this to work with a) the hardware selected and b) the operating system and software stack selected.
Best case scenario: Select a software distribution method that allows a device manager full control over what is running on a device, with minimal downtime and in-field engineering costs when apps change.
Write good software that solves a use-case, and integrate this so it works well with hardware and the operating system. This requires deep knowledge of embedded development and the hardware, operating system and kernel.
Best case scenario: Leverage your current code base and DevOps while writing code that will definitely work on your device
Finally, to ship a device, it needs to be configured specifically for each customer. Letting the customer configure a device, is a large source of friction. Configuring a device before shipping reduces first touch friction for the customer at the cost of engineering time.
Best case scenario: Provision a device in your factory, but without needing extensive engineering support and costs.
Many modern businesses have commoditised or automated steps which make taking a product to market faster and easier. IoT does not have this yet. To get the answer to these questions now, contact Canonical and read this white-paper on IoT app stores for a bit more background.
The following blogs in this series will show you how to reach the “best case scenario” in all of the above steps. Next, we will look at selecting hardware. You should sign up to our IoT newsletter on the right hand side of this page to make sure you read it when it comes out. If you can’t wait till then, sign up to the webinar on How to launch IoT devices to get the full story, all in one place.
*Specifically, you can start with Chinese wholesalers like Alibaba and get the raw materials to sell. Amazon provides access to +250 million customers with a store front, or Shopify can be used for the DIY enthusiast. Then, East-Asian manufacturing can be leveraged at any scale, for example by using Sourcify. This adds value to raw materials and turn it into a unique product, while Stripe, Paypal, or banks take payments. Finally, third-party logistics gets the product from warehouse to consumer.
From home control to drones, robots and industrial systems, Ubuntu Core and Snaps provide robust security, app stores and reliable updates for all your IoT devices.
If you are packaging your IoT applications as snaps or containers, you are aware of the benefits of bundling an application with its dependencies. Publishing...
Ubuntu Core is the operating system for IoT and edge Ubuntu Core, the Ubuntu flavour optimised for IoT and edge devices, has a new version available. With a...
The development of graphical applications intended for use on IoT devices isn’t trivial. The complexity goes beyond the usual challenges that exist in the...