News · October 17, 2026
Exotool for professional developers: write what needs you, generate the rest
Exotool is usually introduced as a way to build an app without writing code. For a professional developer it is something else: a way to write only the code that needs your hand, and to have the rest of the stack generated and knitted together around it.
Where the time goes in a client/server app
Most of the effort in a web app with a back end is not the interesting logic. It is the plumbing: the API between the browser and the server, the request and response shapes, the validation on both sides, the session, the storage layer, the error paths, and keeping all of that in step when something changes. A new field on a form touches a template, a client handler, an endpoint, a query and a schema. The logic that makes the app yours is a fraction of what gets written.
What Exotool generates, and what you write
In Exotool the app is a diagram: screens, how they connect, the data, and the activities behind the elements, written in the Exotool language. The patented engine decides which statement runs on the device and which on the server, generates both sides, and generates the APIs between them. That is the plumbing, done the same way every time.
When a statement needs the target language, you drop into it. A JS< >JS block embeds JavaScript on the device, as an expression or a statement; a PHP< >PHP block embeds PHP on the server, with the values of the surrounding Exotool scope available inside it. if_on_client and if_on_server override the engine's placement when you know better. Pages and the app carry their own extra JavaScript, CSS and PHP. Templates are Handlebars-style HTML that you can replace element by element. So the parts that need you are written by you, in the language they belong in, and everything round them is generated.
A front end in minutes
The first use most developers find is the front end. Lay out the screens, bind lists and forms to data, and the progressive web app exists, installable from the browser on iOS and Android alike, with its server side and storage already behind it. Then write the activities that make it yours. Ask Claude for the tedious parts through the Exotool connector: Claude edits the diagram, the engine builds, and you read the diagram to see what changed.
Debug both ends at once
The visual debugger follows a step from the device to the server and back in one session, with breakpoints and variables on either side. In a hand-built client/server app that means two debuggers, two sets of logs and a guess about which side went wrong. Here it is one step, wherever it ran.
What you keep
The generated source is yours. While you build, the app runs in Exotool's sandbox with a preview address; to ship, deploy the source on a host of your choice with your own database. There is no runtime to license and no platform to leave the app behind on.
The language reference, with the explicit blocks and the client/server statements, is in the Help Center.