When we launched the first IoT product called Raqib commercially in 2018, we received a lot of feedback from users and potential customers.
We have to decide to enhance the current product or spawn into a new product altogether.
Meanwhile, there are two more IoT products that we are still building and enhancing – the second product called Favorsense and the third product called Favoriot IoT platform.
Finally, we decided to follow our gut feeling and start building our fourth IoT product called Dscover (formerly named D’scover – we will reveal the reason for changing the spelling later).How We Build Our Fourth IoT Product Click To Tweet
The Problem Statement
When we introduced Raqib as a single device solution for tracking (instead of using a Bluetooth smartwatch and a smartphone), we received much feedback that they don’t need the features of monitoring vital health signs.
But in which market is tracking the best suit for this product? Why the need for monitoring an individual in the first place?
In our early customer development process, tracking an individual is critical for safety – especially during travel.
If a person travels in a tour group, he wants to have some freedom on his own. But he also needs to be constantly connected with the group or his tour bus.
In the case of a tour guide responsible for the group, he must ensure the group’s safety, and the travel itinerary must be adhered to and to ensure no one is late or left behind.
If that person is lost, the easiest way is to locate through the mobile app. The app should also have a travel planner feature to organize and share among the tour members.
How Big is the Market
Initially, we targeted the Travel and Tourism market, which was vast and active before the Covid-19 strikes in early 2020.
Below are the statistics of the world’s and Malaysia’s No. of arrivals.
However, when travel and tourism were severely affected in 2020 and 2021 by restricted movement orders and banned in traveling, we pivoted our market to a family and friends app.
The IoT Solution
We chose a mobile app as the solution because of the following reasons:
- Cheaper because this “IoT” solution uses the individual’s device, i.e., smartphone. GPS is the only sensor needed. The user has paid their connectivity charges (mobile data). The user only needs to download the app and pay for premium features.
- Easier to deploy and manage the users (only via the Google Store and App Store)
The biggest challenge for such a product is that it has become a B2C model whereby the channel to market can be very challenging.
The most accessible marketing channel to reach the users is via Social Media – Facebook, Instagram, and Twitter.
To conduct targeted ads, we need to identify the users’ demographics – in this case, the family members and friends.
Earlier, we named the product D’scover, but it is complicated for a user to search the app in the App Store because of the unique spelling. Finally, we decided to change the name to Dscover.
In the travel and tourism market earlier, we have a B2B model approaching Travel Agencies and Government, but unfortunately, Covid-19 has a significant impact in this sector.
We have even expanded the market segment to solve the issues of monitoring quarantined patients. However, for some unforeseen reasons, this solution did not get the buy-in from the authorities.
Time to Stop Developing New IoT Products
We asked ourselves, have we done enough marketing and sales before moving into another product? Building a new product can be long and tiring.
All four IoT products have their strengths and weaknesses – which I will be able to share in other Blog articles. It is only the beginning of my IoT Adventure – you may subscribe to the newsletter or the RSS feed.
- Google Play – Download
- iOS App Store – Download
- Dscover Ver 3.0 Video
- Dscover – Video Playlist
- Travel with Dscover
- Dscover How-To Videos
- Dscover Review by FreeAppsForMe
- Dscover Review by AndroidAppsForMe
- Dscover Review by AppPearl
Articles worth reading:
- How We Build Our First IoT Product
- How We Build Our Second IoT Product
- How We Build Our Third IoT Product
- How We Build Our Fourth IoT Product
6 thoughts on “How We Build Our Fourth IoT Product”