From Embedded to IoT: Evolution of Tech, Roles, OS, and Business Models

1. Technology Stack Shift

After decades of development, embedded technology is now pervasive, yet it remains niche and highly specialized. Over the past ten years, the Internet of Things (IoT) has expanded into homes, commerce, industry, and agriculture, attracting both traditional embedded engineers and newcomers from other fields. Four major changes are evident:

IoT demands a broader technology spectrum, raising platform requirements.

Developer expectations now emphasize tooling and ease of use.

IoT operating systems have moved beyond traditional kernels to integrate many capabilities.

IoT is cloud‑integrated, offering rich application scenarios and business models that aggregate resources.

The article focuses on technology, people, operating systems, and business models to explain the transition from embedded to IoT.

2. Developer Shift

IoT developers can be divided into two groups: those building platform capabilities and those building applications on top of those platforms.

The first group must master the entire IoT technology stack—from device hardware to cloud services—to design platforms that attract a broader ecosystem of second‑group developers. The second group includes traditional embedded engineers and internet developers, both of whom must acquire new knowledge in multimedia, cloud, and AI to effectively deliver IoT solutions.

Key responsibilities for the first‑group developers are:

Providing rich functional components, including hardware modules, device‑side and cloud‑side software, and development/debug tools.

Enabling low‑code development with languages such as Python and JavaScript to lower entry barriers.

As IoT matures, platform‑building developers will become fewer, while application developers—from students to front‑end engineers and product managers—will increasingly contribute to IoT innovation.

3. Operating System Shift

IoT operating systems have evolved through four stages:

No OS: Early single‑function embedded devices required no operating system.

Simple OS: Event‑driven systems like Contiki and TinyOS appeared for multi‑device networking.

Real‑time OS: Solutions such as FreeRTOS offered better real‑time performance with richer kernels.

IoT OS: Modern systems (e.g., RT‑Thread, LiteOS, AliOS Things, Linux, Android) integrate networking, multimedia, provisioning tools, and application ecosystems, co‑existing due to diverse chip vendor preferences.

While some argue that unifying the OS would solve IoT fragmentation, the author disagrees, emphasizing that fragmentation is inherent and that the value of IoT OS lies in deep hardware‑software integration for performance and cost advantages.

4. Business Model Shift

Traditional embedded businesses relied on hardware sales, limiting scale. IoT’s cloud‑integrated nature enables recurring revenue streams—cloud storage, services, and content—transforming a one‑time hardware sale into an ongoing, high‑value operation. This shift creates opportunities for billion‑dollar IoT companies and reinforces the ecosystem’s growth.

5. Summary

The evolution from embedded systems to IoT raises technical complexity but simultaneously lowers development barriers through scripting languages, rich ecosystems, and powerful tools. This democratization allows a wider range of developers to create innovative products, while the cloud‑centric business model drives high‑margin, scalable revenue, paving the way for massive IoT enterprises.