Blogs

A weekend at Emergent, a Chrome extension, and why planning before a room opens is the real work.

Osiflow HMI was demoed at the Claude community meetup in Delhi alongside physical AI agents, pre-commit pipelines, and robotics tooling. Before the solution landed, the problem did. Designers and developers in the room had all hit the same wall: robot specs, ROS node graphs, and machine jargon with no design vocabulary to translate any of it. This is what that room looked like.

At some point in every robotics HMI project, a designer opens a file that was never written for them. It might be a 60-page system architecture document. A ROS node graph. A manual dense with coordinate system notation. Whatever form it takes, the message beneath it is the same saying "You're on your own here." This isn't a skill gap. It's a vocabulary gap and nobody in the design industry has solved it yet. Here's what it actually looks like.

Robots are being deployed at unprecedented scale. No shared design infrastructure exists for the interfaces & experiences operators use to control them. Osiflow HMI is building it.