Smart Machines & Factories Editorial TeamAt Operations Calling 2026 on October 6, 2026, connected-worker platform Tulip announced a set of new build, run and scale capabilities aimed at the people who actually run the factory floor. Alongside a planning canvas called Projects and an AI "Authoring Agent" that drafts apps from a plain-language brief, the release that stands out for software teams is Code-Based Apps — a way to build the same frontline apps Tulip's low-code editor produces, but from a developer's own IDE and AI coding agent, with changes shipped through Git pull requests as frozen, audited versions.
Why a No-Code Platform Is Adding a Developer Path
Tulip built its reputation on letting operators and engineers assemble shop-floor apps — work instructions, quality checklists, andon triggers — without writing code. Code-Based Apps does not replace that; it sits next to it for the cases where a no-code canvas stops being the right tool: apps with complex conditional logic, apps that need to be version-controlled and code-reviewed the way the rest of a manufacturer's software already is, or apps a contracted development team is building to a spec rather than iterating live on the plant floor. CEO Natan Linder framed the broader release around the same idea applied to AI: "AI has one job, to unlock human potential" — in this case, the potential of a software team that was previously locked out of the platform because they wanted to work in their own tools.
Tulip Operations Calling 2026 — Key Facts
- Code-Based Apps — build frontline apps in an external IDE with AI coding agents, deploy via Git pull requests as frozen, audited versions (currently in preview);
- Projects — a unified canvas to plan and connect every app, automation, agent, table and connector across a deployment (in customer testing);
- Authoring Agent — an AI assistant that drafts apps inside project context and asks clarifying questions before building, rather than generating a finished app blind;
- Industrial Connectivity — ties machine-level data to the specific operator action taken, logging not just what happened but what the human decided and why;
- Scale layer — Enterprise Library for publishing a tested app to every site, plus a cross-site AI chat interface (OpsMoto) for operational questions spanning plants.
What "Frozen, Audited Versions" Signals for Regulated Plants
The detail worth pausing on is the deployment model: a pull request, once merged, becomes a frozen version of the app rather than a live document that keeps changing underneath the people using it. For a GxP-regulated plant or anywhere else change control matters, that is the difference between "the app changed and we're not sure when" and a diffable commit history that a quality team can actually audit. Tulip is pairing the feature with a Validation Accelerator service aimed squarely at life-sciences customers who need that audit trail to pass a validation review, which suggests the company sees compliance — not just developer convenience — as the real reason to add a code path to a no-code product.
The Build Gap This Actually Closes
Low-code shop-floor tools are good at letting a plant engineer assemble a checklist app in an afternoon. They are weaker once the app needs to talk to an existing MES, pull inventory data through an internal API, enforce logic that depends on a dozen edge cases, or get maintained by a software team under the same code-review discipline as the rest of the company's systems — work that benefits from being built by developers with source control, tests and a proper SDLC, not assembled block-by-block in a browser. That is a custom mobile and web development job as much as it is a manufacturing-software one, and it is exactly the gap YuSMP Group's mobile development team fills for manufacturers who need a frontline app connected to their own systems built properly from the start, rather than stretched out of a no-code editor until it breaks.
Sources: Tulip press release, October 6, 2026; IT Tech News, October 7, 2026.