From Metal and Motors to Code and Constraints
The critical constraint in modern robotics is the software architecture, development practice, and human expertise needed to coordinate complex, AI-enabled machines in unpredictable environments. For decades, robotics progress was limited by motors, sensors, and mechanical precision. Now, a new research study from QNX, a division of BlackBerry, shows that hardware is no longer the main brake on innovation. In its Inside the Robot: Architecture Benchmark Report, almost one in three developers (27 percent) name software architecture and integration as their biggest performance bottleneck, compared with 16 percent who point to hardware. As robots move from fenced-off, repetitive jobs into hospitals, warehouses, and shop floors, their success depends on predictable, secure software foundations. That shift is turning robotics software development into the central discipline of automation, affecting not only engineering teams but also how factories staff, train, and organize everyday production work.
Inside the Robot: Architecture Becomes the New Limiting Factor
The QNX benchmark report highlights how the internal design of robotics software now shapes what machines can safely do. Developers are building systems that mix AI-driven decision making with real-time control, often in the same device. According to QNX, 85 percent of developers expect software to play an even greater role in robotics over the next three to five years, with teams planning major investments in AI decision engines, cybersecurity, operating systems, and real-time control layers. At the same time, 95 percent say deterministic, real-time execution is important to their systems, yet 91 percent still run at least some safety-critical workloads on general-purpose operating systems. This mismatch exposes a growing tension between flexibility and guaranteed behavior. Certification and standards add further pressure, with two-thirds of teams reporting project delays caused by compliance processes for cybersecurity and functional safety.
Factory Automation Software and the Changing Role of Workers
On the factory floor, software is reshaping what automation work looks like day to day. The spread of industrial robots—more than half a million units were installed in 2024 alone—means every new machine adds not just mechanical capacity but also new interfaces, alerts, and data streams. Automation is becoming a software problem because workers now rely on dashboards, updates, and data-driven decisions to keep lines running. A line operator might watch vibration and temperature trends, check error logs, and decide whether to intervene immediately or at the next planned stop. The worker closest to the machine becomes a workflow interpreter, translating what factory automation software reports into practical action. That makes software literacy as important as mechanical awareness: recognising a failed update or a suspicious permission change can protect uptime, quality, and safety across an entire line.
New Skills for a Software-Centric Robotics Era
The shift from hardware-centric to software-centric robotics demands new skill sets across both engineering and operations. Robotics software development now requires teams that understand AI models, safety-certified operating systems, and secure connectivity, instead of focusing mainly on mechanical design. At the same time, automation worker training must move beyond traditional robot safety and basic programming to build broad digital fluency. The World Economic Forum’s Future of Jobs Report 2025, based on views from more than 1,000 employers, says 63 percent of employers see skills gaps as a major barrier and that 59 percent of the global workforce may need reskilling or upskilling by 2030. For manufacturers, the goal is not to turn every operator into a programmer but to ensure workers can read dashboards, question defaults, understand what software updates change, and see how the digital layer shapes physical output.
Designing Robotics Architectures Around People and Software
As robots move closer to human co-workers, robotics architecture design must account for people as much as processors. Systems are increasingly deployed alongside humans, with more than four in five developers in the QNX study reporting that their robots already operate in shared environments. That raises the stakes for predictable real-time behavior, cybersecurity, and clear human-machine interfaces. In practice, a good architecture now spans edge controllers, secure operating systems, cloud analytics, and worker-facing dashboards. It must balance deterministic control with the adaptability of AI and data services. For manufacturing and logistics leaders, this means treating software—not hardware—as the core strategic asset. Investment decisions, hiring plans, and automation worker training all need to reflect that robotics success will depend on integrated, well-architected software systems and teams who understand how to operate and improve them over time.
