Embracing a Consumer-Centric Approach to Product Development

Over the Air · 8 Jun 2021 · 35m

What this episode covers

Doug Roberson, CTO of Alterco Robotics (maker of the Shelly IoT brand), explains how the company uses a consumer-centric approach to product development by listening to customers via social media and forums. He discusses the importance of versatile hardware form factors, such as the Shelly 1 relay, and the critical lesson that a working prototype does not guarantee a profitable product due to Bill of Materials costs. Roberson also emphasizes data privacy by offering local control options and advises founders to build experienced teams and say 'no' to superfluous features to avoid failure.

Other shows on the same ground, closest first.

  • Product Startup · 20m

    128: Creating an App for Your Hardware Device

    Piotr Zajac, CEO of Untitled Kingdom, a 55-person app development firm specializing in IoT, MedTech, and FemTech, explains how to build successful apps for hardware devices. He argues that developers must focus on one or two core features and prioritize user feedback to avoid over-engineering, citing a failed project where a client spent millions on unnecessary features. Zajac emphasizes that onboarding is crucial for creating user habits and that high-quality, secure software aligned with FDA and ISO standards is far cheaper in the long run than cheap, buggy code. He illustrates these points with the Irgo hearing aid and its Soundmatch app, which uses ultrasound to personalize hearing profiles.

  • IoT For All Podcast · 26m

    Maximizing ROI for IoT Prototyping and Development | Blynk's Pavel Bayborodin

    Pavel Bayborodin, Founder and CEO of Blynk, discusses the company's journey from a Kickstarter-funded prototype to a commercial IoT platform. He outlines the typical IoT development lifecycle, emphasizing that hardware design and connectivity are the primary hurdles, while software integration often requires significant organizational change. Bayborodin also details monetization strategies for connected products, including indirect data value, premium services, and automated replenishment, noting that software costs should roughly match hardware costs.

  • The Amp Hour · 1h 09m

    The EEVblog Sparkgap Generator

    Dave Jones of EEVblog and Chris Gammell of Contextual Electronics discuss the pitfalls of IoT white goods, illustrated by Jones's new Miele dishwasher, and explore local IoT solutions using MQTT and ESP8266. Jones provides an update on his upcoming multimeter Kickstarter, detailing the challenges of cross-platform app development, Bluetooth packet corruption, and the high costs of custom packaging and PCB revisions. The hosts also analyze the bankruptcy of TechShop, debating the viability of commercial makerspaces versus non-profit models, and critique a Shark Tank pitch for a barcode luggage tag to emphasize the importance of product-market fit.

  • The Hardware Entrepreneur · 43m

    #017 - How *not* to think about IoT, with Michael Vladimer of Orange IoT Studio, USA

    Michael Vladimer, co-founder of Orange IoT Studio, outlines a framework for building successful IoT products, arguing that they must solve compelling problems rather than just connecting everything. He defines the core MVP of an IoT device as consisting of sensors, connectivity, computation, and user interface, while warning against expecting users to invest smartphone-level effort into these devices. Vladimer also discusses the nuances of IoT security, advocating for context-specific standards based on data sensitivity, and shares insights on cross-cultural communication and storytelling in product development.

  • IoT For All Podcast · 23m

    Custom vs. Off-the-Shelf IoT Solutions | Brash Inc.'s Richard Beranek | Internet of Things Podcast

    Richard Beranek, Managing Partner at Brash Inc., discusses the strategic decision between custom and off-the-shelf IoT solutions for product development. He explains that while off-the-shelf hardware and software offer speed and vendor support, custom development is often necessary for specific functional requirements, legacy system integration, or seamless user experiences. Beranek advises companies to start with proof-of-concept prototypes using existing tools to validate their thesis before committing to expensive custom engineering, noting that most successful deployments are hybrid approaches combining both.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by Over the Air. The episode itself belongs to its publisher.