You Can Build a Workflow From Your Phone Now

You can build a workflow from your phone now. Not just open one. Not check whether a run finished. Not make one tiny config change and then give up because the interface is fighting you. You can build it, test it, and publish it. Mobile support was one of the most consistent pieces of feedback I kept hearing from creators. A surprising number of people do most of their work from their phones, especially outside the kind of setup where you have a laptop permanently open beside you. For them, needing a desktop every time they wanted to create or edit a workflow was not a minor inconvenience. It was a real blocker. The obvious solution would have been to take Workflow Studio, make everything smaller, add touch support, and call it mobile. That would have been terrible. Workflow builders are naturally desktop-heavy interfaces. You have a canvas, nodes, edges, inspectors, configuration panels, block libraries, and usually a lot happening at once. That works well when you have a large screen and a precise pointer. On a six-inch display, dragging nodes around and trying to connect tiny handles is less "visual programming" and more a test of hand-eye coordination. So we did not make the canvas the primary mobile interface. We made Composer the primary interface instead. On mobile, you can describe the workflow you want in chat and Composer builds it directly. If you want another step added, ask for it. If something is wrong, tell Composer what to change. If you want a branch, a model call, a transformation, or another part of the workflow edited, you can continue the conversation instead of manually reconstructing the graph with your thumbs. That changes the role of mobile quite a bit. The phone is no longer trying to imitate the desktop builder badly. It becomes a different way of operating the same workflow system. The graph is still there when you need it. You can open it and inspect what Composer built. You can select steps, use the inspector, change configuration manually, test the workflow, and make sure the execution behaves the way you expect. Once it is ready, you can publish it to the marketplace from the same device. The entire loop can happen without opening a laptop. You might have an idea while commuting, describe it to Composer, test the generated workflow, make a few changes, and publish it before you get home. Or you might already have a workflow live and realize one step needs changing. You can open Studio, ask Composer to modify it, run a test, and ship the update instead of writing yourself a note saying "fix this later when I'm at my computer," which is where good ideas occasionally go to die. There is also a broader product direction behind this. AI changes what a mobile creation interface can look like. Historically, complex creation tools were difficult to bring to phones because the interface itself had to expose every action. If a product had fifty different operations, you somehow had to fit access to those fifty operations onto a small screen without making the whole thing unusable. With Composer, much of that interaction can move into language. The underlying workflow can still be complex. The controls do not all have to be visible simultaneously. That does not mean chat replaces the visual builder. It should not. Visual structure is extremely useful when you are trying to understand a complicated workflow, debug execution, or make precise changes. Desktop Workflow Studio remains the better environment for deeply working through large graphs. But you should not need the best possible setup every time you want to create something. Mobile Studio is designed around that idea. Use Composer for the high-level work, drop into the graph and inspector when you need precision, test the actual workflow, and publish it when it is ready. It is also still in beta. There will be rough edges. Mobile browsers have their own collection of creative ways to make complex interfaces behave strangely, and we are still finding the places where Studio needs to adapt better. If something breaks or feels unnecessarily difficult, send it to me. I would rather hear about the ugly parts now than pretend the beta label is decorative. The goal is simple: if you have an idea for a workflow and the only computer near you happens to be the one in your pocket, that should be enough.