Where this is going.

Several languages — and a runtime that speaks German

Your captions and button titles per language, filled in automatically where they are empty and never touched again once a human has translated them. And Neuridion's own windows in a built application — the backup window, the standard dialogs — are English today in front of a German customer's customers. About sixty strings.

Decided in full: translations are data with provenance, the file lives in the project, and the build bakes in only the languages you tick.

A filter for very large schema diagrams

Eighty tables on one canvas is a picture of nothing. Show a table and what it touches, one step out or two.

The “this loads everything” warning, done properly

.all() on four thousand invoices is a mistake the editor can see coming. The warning exists and is too eager — a checker that puts a mark under correct code is a checker nobody reads twice.

Undo — the price of “nothing is saved, because everything already is”

Neuridion has no Save button: leaving a field writes it. That is right, and it costs exactly one thing — there is no way back from a mistake. Until it exists, the nets are the ones already built: automatic backups, the read-before-write rule on everything destructive, and the revision counter that refuses silent overwrites.

Hard, and honestly so: an undo that only covers the last field is a lie, and one that covers everything has to know what a transaction was. Moved from 1.0 on 22 August 2026 — done right rather than done rushed.

An App Store build for the applications you make

A second kind of build, sandboxed to Apple's rules, so an application you made with Neuridion can be sold in the Mac App Store under your own name.

The honest part: a sandboxed application cannot write wherever your scripts say. That has to be found out by building one and clicking through everything, not by reading the rules — and the build sheet will say plainly what such a build cannot do, rather than flattering it.

Remote debugging

Breakpoints in the code that is actually running on the server, from the IDE on your desk. Same debugger, one hop further away.

Forms that scroll — so a long record is not capped at one screen

Today a form is exactly as tall as its window. From 2.0 a form can be taller than the window it opens in and scroll: the window keeps its size, the content moves beneath it, so a record with many fields is no longer limited to what fits on a laptop screen.

The point is the person filling it in. A soft fade at the bottom edge and a visible scrollbar say there is more below, so nobody misses the last fields; the designer shows a line marking the window's edge while you build. One rule keeps it honest — one scroller per form, the form or a large list inside it, never both fighting the wheel.

Rendered on the server, not shipped to the browser

The tempting route is to send the forms and the scripts to the browser, since the scripts are JavaScript already. It would even work technically. It is still wrong: your source code would then sit in your customer's browser, which undoes the reason the payload is encrypted in the first place.

So: the server runs the real thing and the browser shows the result and sends back clicks. One implementation of the API, one set of rules, and for the first time genuine read protection — the browser only ever sees what was drawn for it.

Two findings from the study worth knowing: the browser is the one client that cannot be paired without a real certificate, unlike our own; and the list alone is a bigger job than the rest of an HTML renderer put together. It would be a version of its own, larger than the server tier — and deliberately a companion to the Mac application, never a replacement.

Windows, Linux, iPad

Mac only is what lets us use the newest of everything and carry no compatibility baggage. It is why the tool feels like a Mac application rather than a portable one.

Per-seat licensing of what you build

Considered seriously and dropped. It does not hold technically, and it puts the first number from our licence inside your application.

An assistant that sits in the IDE while you work

Removed on purpose. An AI that helps with development belongs on the project folder — which is exactly what the plain-text project format was designed for — with the whole thing in view. The one exception is the moment a project does not exist yet, and that is in the beta.