12 Device Evolution: IoT Products and Enablers

12.1 Start With the Decision

A smart washer senses its load, checks energy prices, and changes the cycle. The product claim is credible only when sensors, compute, radio, and service costs support it.

12.2 Route Overview

This is part 3 of 4. Review Device Evolution: Boundaries and Connected Products for the preceding evidence.

12.3 Learning Objectives

• Trace how sensing, edge compute, BLE, and cloud services enable an IoT product.
• Test a product benefit against battery, privacy, and operating-cost limits.

12.4 Chapter Roadmap

• IoT Products (2010s-Present)
• Common Pitfalls and Misconceptions
• Embedded to Connected to IoT
• Why This Evolution Matters
• Connected vs IoT ROI Tool
• Knowledge Check: Business Impact
• Microwave Evolution
• Checkpoint: Pricing Evidence
• What is an Embedded System?
• Defining Principle
• Cortex-M Low Power
• BLE for Battery Devices
• Checkpoint: Enabling Technologies
• Phoebe’s Field Notes: What The “Coin Cell For A Year” Claim Actually Budgets
• IoT Battery Life Calculator
• Knowledge Check: Enabling Technologies
• Knowledge Check: BLE Adoption

12.5 IoT Products (2010s-Present)

Definition

IoT products represent the most advanced stage, combining embedded technology, connectivity, and intelligent decision-making. These devices leverage data analytics, machine learning algorithms, and sensor fusion to optimize performance, adapt to user behavior, and interact autonomously with other systems.

Key Characteristics:

• Autonomous intelligence: Makes decisions without human intervention
• Machine learning: Learns patterns and improves over time
• Sensor fusion: Combines multiple data sources for context awareness
• Ecosystem integration: Communicates with other IoT devices and cloud services
• Edge computing: Processes data locally for real-time responses

Example

A smart washing machine that automatically selects optimal washing cycles based on water usage, energy efficiency, and load type. Function: Uses data analysis and predefined logic to enhance resource management and user convenience. It detects fabric types via sensors, learns your usage patterns (you always wash jeans on Wednesdays), adjusts water temperature based on energy prices from the smart grid, and orders detergent automatically when running low.

Value

• Benefit: High-level impact through resource savings, time efficiency, and continuous optimization. Reduces water consumption by 30%, energy by 25%, and delivers perfectly cleaned clothes based on learned preferences. Integrates with smart home ecosystem (starts cycle when solar panels generate excess power).
• Limitation: May require more complex infrastructure, data management, and security considerations. Higher upfront cost, ongoing cloud service fees, privacy concerns about usage data, and potential security vulnerabilities if not properly secured.

12.6 Common Pitfalls and Misconceptions

The “Smart” Label Trap: Many products marketed as “smart” offer only basic connected control with premium branding. Apply the three-part maturity test: Does it learn? Does it decide? Does it adapt to changing conditions? A light bulb controlled from a phone can meet the baseline IoT test, but it should not be sold as adaptive. A more mature lighting system may learn a routine, use ambient-light sensors, and coordinate with other devices.

Confusing Connectivity with Intelligence: Connectivity can establish an IoT data path, but it does not prove intelligence. A thermostat with an app is connected IoT; a thermostat that learns your schedule and adjusts from occupancy, weather, and energy prices is adaptive IoT. The distinction matters because products lose trust when basic connectivity is sold as autonomous optimisation.

Ignoring the Embedded Foundation: IoT devices do not replace embedded systems — they build on top of them. Every IoT device still contains an embedded core that must balance the cost-power-performance triangle. Engineers who skip embedded fundamentals (real-time constraints, sub-1 uA sleep currents, deterministic behavior) build IoT devices that drain batteries in weeks instead of years.

Assuming Linear Evolution: Not every product should become connected or adaptive. A simple kitchen timer can remain embedded; it does not need ML or cloud analytics. Forcing connectivity or intelligence into products where users do not need it adds cost, complexity, and attack surface without proportional value.

Overlooking the Ecosystem Opportunity: Ecosystem integration is not required for baseline IoT, but it can extend value. A thermostat may gain useful capabilities by coordinating with a home platform, blinds, and occupancy sensors. Build those integrations only when their service boundary, failure modes, and customer value are clear.

12.7 Embedded to Connected to IoT

Use Figure 12.1 to prepare the decision in embedded to connected to iot. The diagram names Evolution of the Internet of Things and The Internet, the two anchors needed to assess evolution from embedded products to connected products to full iot products.

Compare Evolution of the Internet of Things with The Internet inside the visual at Figure 12.1. Next find Host-to-Host, which completes the scope of evolution from embedded products to connected products to full iot products. The decision in embedded to connected to iot must preserve that labelled boundary.

12.8 Why This Evolution Matters

Understanding the differences among these categories is essential for grasping the transformative potential of IoT in various industries. IoT products not only enhance functionality but also deliver smarter, more sustainable solutions.

Real-World Impact by Era:

12.9 Connected vs IoT ROI Tool

Compare the total cost of ownership and return on investment between Connected and IoT devices over their customer lifetime.

Key Finding: Notice how basic connected services struggle to justify subscription revenue without measurable savings. Adaptive automation may create quantifiable value, but the evidence and operating costs still belong in the business case.

Key Takeaway: The progression from Embedded -> Connected -> IoT represents not just technological advancement, but a fundamental shift in business models (one-time sale -> subscription services), value proposition (features -> outcomes), and customer relationships (transactional -> ongoing engagement).

12.10 Knowledge Check: Business Impact

Question 3: A startup is designing a pet feeder. Version 1 dispenses food on a fixed schedule. Version 2 adds Wi-Fi so owners can trigger feeding from their phone. Version 3 uses weight sensors, pet activity tracking, and ML to automatically adjust portion sizes based on the pet’s health data. Which version can most justifiably charge a monthly subscription fee, and why?

a) Version 1 - because it is the most reliable b) Version 2 - because it requires cloud servers for the app c) Version 3 - because it delivers ongoing value through personalized health optimization d) All versions can equally justify subscriptions

12.11 Microwave Evolution

Scenario: A kitchen appliance manufacturer is planning their product roadmap for the next 5 years. They currently sell three microwave models and want to understand their competitive positioning:

Model A (Budget): Digital timer, preset power levels, mechanical door sensor. Price: $99 Model B (Premium): Model A features + Wi-Fi connectivity for remote start via smartphone app and recipe downloads. Price: $249 Model C (Innovation): Model B features + weight sensors, humidity monitoring, and ML algorithms that automatically adjust cooking time and power based on food type. Price: $399

Question: How should each model be classified in the Embedded -> Connected -> IoT evolution framework?

Answer: Model A is Embedded, Model B is Connected, Model C is IoT

Classification Breakdown:

Model A (Embedded Device):

• Thing: Physical microwave
• Computation: Digital timer, preset controls
• Internet: No connectivity
• Value: Basic functionality, operates independently

Model B (Connected Device):

• Thing: Physical microwave
• Computation: Digital controls + app interface
• Internet: Wi-Fi for remote control
• Value: Convenience (remote start, recipe downloads)
• Limitation: No intelligent decision-making, just remote control

Model C (IoT Device):

• Thing: Physical microwave
• Computation: Advanced processing + ML
• Internet: Wi-Fi + cloud analytics
• Intelligence: Sensors + algorithms optimize cooking automatically
• Value: Autonomous optimization, learns food types, prevents overcooking

Real-World Parallel - Thermostats:

• Embedded: Honeywell programmable ($50) - set schedule manually
• Connected: ecobee3 lite ($140) - control remotely via app
• IoT: Google Nest ($250) - learns your schedule, auto-optimizes, saves 10-20% energy

The Basic-Connectivity Gap: Many “smart” devices struggle because their value stops at remote control:

• Remote control is nice-to-have, not must-have
• Customers won’t pay 2-3x for convenience alone
• Adaptive automation can solve measurable problems customers may pay for

12.12 What is an Embedded System?

An embedded system is a computer system that combines a computer processor, memory, and input/output peripheral devices to perform a dedicated function within a larger mechanical or electrical system. These systems are purpose-built and optimized for specific applications.

12.13 Defining Principle

“An embedded system is a computerized system that is purpose-built for its application.”

• Elicia White, Making Embedded Systems (O’Reilly)

This definition has deep implications for how embedded systems are designed:

1. Minimize cost / Maximize lifetime for a given expected workload
2. Optimized, custom software that uses as few resources as possible
3. No general-purpose bloat - every byte of code and every milliamp of power must justify its existence

Unlike desktop software where you can always throw more RAM or CPU at a problem, embedded systems force engineers to make hard trade-offs. This is why IoT firmware developers often write in C rather than Python - the efficiency gains directly translate to lower costs, longer battery life, and more reliable operation.

Key Characteristics of Embedded Systems

• Purpose-Built Functionality: Embedded systems are designed to perform a single, specialized task, making them highly efficient in operation.
• Low Power Consumption: Due to their focused functionality, embedded systems operate with minimal power requirements, allowing them to fit in small spaces and extend device longevity.
• Cost-Effective: Embedded systems are typically inexpensive, making them an economical solution for controlling devices in various applications.
• Market Dynamics: Embedded systems markets often operate within tight margins, such as in household appliances and consumer electronics.
• Optimization Requirements: Designers must optimize code and use minimal microcontroller resources to keep costs low and efficiency high.

Applications and Market Scale

Embedded systems are found in virtually every electronic product across major industries:

Pause at Figure 12.2 before carrying defining principle forward. Its visual vocabulary joins DAC to Digital-to-Analog, which frames diagram of an embedded system showing components like processors, converters, and amplifiers.

At DAC in Figure 12.2, compare the diagram with Digital-to-Analog; then locate ADC. That labelled check bounds diagram of an embedded system showing components like processors, converters, and amplifiers. For defining principle, retain ADC as evidence for the resulting choice.

Embedded systems are fundamental to modern electronics, providing tailored solutions to a wide range of technological challenges.

Figure 12.3 makes defining principle inspectable through Embedded Design Tradeoffs and Performance. Those diagram labels establish the scope of embedded systems design triangle balancing cost, power, and performance.

Begin Figure 12.3 with Embedded Design Tradeoffs, then distinguish Performance and CPU, memory. The diagram separates Embedded Design Tradeoffs from Performance within embedded systems design triangle balancing cost, power, and performance. Keep both distinctions explicit in defining principle.

This “design triangle” of cost, power, and performance defines the fundamental constraints that embedded system engineers must balance. IoT devices inherit these constraints but add connectivity and intelligence on top, making the engineering challenge even more demanding.

12.14 Cortex-M Low Power

The ARM Cortex-M processor family revolutionized embedded computing:

• First ultra-low-power 32-bit processor designed for embedded applications
• Resources: 8-96 kB RAM, 64-512 kB code flash
• Game-changer: Sleep currents recently dropped below 1 uA - enabling devices to run for years on coin cell batteries

Before Cortex-M, designers had to choose between 8-bit processors (simple but limited) or power-hungry 32-bit chips. Cortex-M gave IoT devices full 32-bit capability with microamp power consumption.

12.15 BLE for Battery Devices

BLE transformed wireless connectivity for IoT:

• Energy efficiency: Send a 30-byte packet once per second and last a year on a coin cell battery
• Critical adoption moment: Support was weak until Apple incorporated BLE into iBeacon (2013)
• Now universal: All major smartphones include BLE, making it the de facto standard for device-to-phone connectivity

The combination of Cortex-M processors and BLE radios enabled the first generation of truly practical consumer IoT devices - fitness trackers, beacons, smart home sensors - that could operate for years without battery replacement.

12.16 IoT Battery Life Calculator

Calculate how long your IoT device will run on battery power. This demonstrates why ARM Cortex-M + BLE was revolutionary for practical IoT.

Experiment: Try legacy values (sleep current = 10 µA, duty cycle = 1%) vs. modern Cortex-M values (sleep = 0.8 µA, duty cycle = 0.1%). The difference is measured in years of battery life.

12.17 Knowledge Check: Enabling Technologies

Question 4: Why was the ARM Cortex-M processor considered a “game-changer” for IoT development?

a) It was the first processor that could run Linux b) It provided 32-bit computing capability with sleep currents below 1 microamp c) It was the cheapest processor ever manufactured d) It was the first processor with built-in Wi-Fi

12.18 Knowledge Check: BLE Adoption

Question 5: What event was critical in driving widespread BLE adoption for IoT consumer devices?

a) The Bluetooth SIG released the BLE specification in 2006 b) Samsung included BLE in the Galaxy S3 c) Apple incorporated BLE into iBeacon in 2013 d) Google released the Eddystone beacon protocol

12.19 Continue to the Next Part

Carry this evidence into Device Evolution: Wireless and Classification, which begins with Wireless Paradigm Shift.