The ones that actually decide it.

No, and that is the point of there being no scripting language. What you do need is the way of thinking that comes with objects and events — this button, when it is tapped, does these things in this order. If you have ever built anything in Access, FileMaker, Delphi, Visual Basic or a low-code tool, you already have it.

What you cannot do is express an arbitrary rule. There are about forty verbs, a branch, one loop and a case. If your app needs something outside that, the honest answer is the export: take the Xcode project and write it in Swift.

For the Simulator, no. Design, preview and run on a simulated iPhone with nothing but a Mac.

For a real phone, yes — a free account is enough for your own device, and a paid one (99 $ a year, paid to Apple, not to us) for handing the app to other people or putting it in the App Store. That is Apple's rule for everybody who builds for iOS, and there is no way round it for anyone.

It is a real iOS app, and it is your app: before it is installed it is given your project's name, your icon and your bundle identifier, and signed again. So several apps you have built sit side by side on one phone, each with its own name under its own icon, and none of them says Neuridion anywhere.

What it shares with a viewer is that it reads your project folder rather than having your design compiled into it — which is exactly what makes Live possible. If you want a fully independent binary with nothing of ours in it, that is what the export is for.

A folder with an .xcodeproj, an asset catalogue and a Sources directory: one Swift file per screen with its view and its handlers, a model, a database, the modules, and any support files the design actually needs. Plus a README that describes every flow in English sentences, and how it was tested.

No package to add, no framework to link, no Neuridion code at all. Open it in Xcode, pick your team, press build.

Your project already is out. It is a folder: JSON for the design, CSV for the large tables, your pictures as pictures. Open it in a text editor, put it in git, read it in ten years with anything that speaks JSON. There is no invented binary format anywhere in the product.

Anything you have exported is unaffected, for ever — it contains no licence check, never expires and never contacts us.

The designer goes back to what it is for everybody: design and preview, in full. Your projects open and your data is yours.

An app running on a phone through our player is the part that depends on the subscription — it is signed by us and carries our player. If you want it to run regardless of us, export it and ship it under your own Apple account.

159 € a year is one price for one person, with no per-app and no per-device fee and nothing to count. The line is drawn where the app leaves the Mac, because that is where the usefulness starts and where our work actually goes: getting a signed, branded app onto real hardware.

The export is the same border crossed the other way — the app leaving and not coming back. It stays in the product because a way out you cannot take is not a promise; it is on the paid side because handing over a finished application is not the free tier's job.

Yes — on 1 January 2027. Every version below 1.0 stops that day, the designer and the player alike. That is deliberate: a beta with no end is not a beta, it is an unpaid product, and an app running on somebody's phone through our player is exactly the thing the price is for.

The beta changes nothing about what a licence buys. Designing and previewing are free now and after 1.0; running on a real device and exporting the Xcode project need a key from the first day. A licence you could ignore until 1.0 would be a button with nothing behind it — and it would lock somebody out of their own workflow the day the version changed.

And you can buy one now, cheaper. The code I2NZMWMG takes 30 % off the first year — 111,30 € instead of 159 €, then 159 € a year afterwards. It is available until 1 January 2027, when the beta ends.

Nothing of yours stops. Your projects are folders of JSON and CSV on your own disk. Anything you exported is an Xcode project with no licence check, no expiry and no way of reaching us — it goes on being yours whatever happens to us.

And winding the clock back does not help: the program remembers the furthest date it has ever seen, so a machine claiming an earlier one counts as expired rather than as having time left.

That is the intention, and every model property is written to read back with a default so an older file keeps opening. But it is beta software and the format is still moving: keep backups, and do not put a year of a real customer's data through it yet.

iPad: yes — it is an iOS app, and that is why the product is called Mobile rather than iPhone.

Mac: separately. Neuridion for the Mac is the sister product — database applications for macOS, same house, same ideas about types and money, its own tool.

Android: not for 1.0. There is a concept written for it. It is not a port — it is a second generator and a second player.

Web: no. The whole argument of this product is that the result is native.

No, and neither does an exported one. An app makes a network request only if you put one in it — a web table you loaded, an endpoint you wrote back to, an iCloud table you turned on. There is no telemetry, no licence call and no back channel of ours anywhere in it. The privacy page lists every request the designer itself can make, one by one.

One person, one repository — Oliver Schellhammer, at SOFTrobots GbR in Villingen-Schwenningen. It is written with an AI as a working partner and decided by a person, which is stated here rather than hidden because it changes how fast things move and how much a test suite has to carry. See Contact.