Roadmap
What is built, what is coming, and what deliberately is not.
The third list is the one worth reading. A roadmap that only ever adds things says nothing about what the product is — and every item below that we have decided against was decided against for a reason we can write down.
Built and running today
0.9.0 is not a demo.
Everything here works in the designer, on a real phone, and in the exported Xcode project — the three renderings are twins, and a suite of about 850 tests exists mostly to catch the day one of them quietly stops agreeing with the others.
| State | ||
|---|---|---|
| The designer | running | Canvas, palette, inspector, the flow board, the class overview, undo, several windows on several projects. |
| The player | running | A real iOS app that reads your project and wears its identity — your name, your icon, your bundle id. Simulator and cabled iPhone. |
| Live | running | Every edit in your hand within a second or two, and you keep your place. |
| The Xcode export | running | Clean SwiftUI, an asset catalogue, a project file, a README in sentences. Compiled by the real compiler on every test run. |
| Two dozen kinds of control | running | Including the map, the canvas, the 3D model, the Gantt chart, the camera and the document viewer. |
| Import | running | CSV, TSV, Excel, SQLite and JSON, with the column types guessed, shown and changeable first. |
| Large tables | running | A window of rows with an honest count; search and sort read the file on disk. |
| Write-back | running | To a web endpoint and to the phone's own calendar. A refusal puts the change back and stops the flow. |
| iCloud | in the export | Built on 10 September 2026. Real CloudKit in an exported app; staged in the designer and the player, because a wildcard provisioning profile cannot hold a container. |
| On-device intelligence | on the Mac | Eleven steps, running against Apple's real models on macOS. Not yet run on a phone that has Apple Intelligence — see below. |
| Papers, tests in sentences, the assistant | running | PDFs the app makes itself, tests written as English sentences, and a first project designed from a description. |
Honest about what has not been held
Some of it has met a simulator and not a hand.
Neither a Mac nor a simulator has one, so both play a staged scene — a poster with a QR code, a parcel with a barcode, a business card. Every flow can be built and driven without a phone, and the recognition itself has not yet been pointed at a real receipt.
The canvas and the Gantt chart are driven through a scripting channel, not with a thumb. The arithmetic is tested; how it feels to drag a bar across a fortnight on a moving train is not something a test can tell us.
The staged location is a square in Munich. NFC in particular cannot be tested through the player at all: a wildcard provisioning profile is not allowed to hold the NFC entitlement, so a real tag needs an export.
Same wall as NFC, and for the same reason. In the designer and the player a cloud table is served by a staged store that behaves like the real one; the exported app talks to CloudKit for real.
Coming
What is being built next.
Today a screen is the template: the app makes a paper out of what is on the page, which is why an invoice with line items needs nothing designing. What is missing is a placeholder inside a paragraph — the sentence “Dear Mrs Meier, your boiler is due for service on 14 March” — and that needs blocks, head and foot bands, and named sources. It is written down and not yet built.
An app that reads and writes real e-mail: an inbox as a table, a message as a record, a reply as a flow. The intelligence steps that summarise and translate one already exist; what does not is the connection to an actual mail account.
A cloud write while the phone is in a lift currently fails and says so. Queueing it and sending it when the network comes back is the obvious next step, and it is the last piece of the cloud work.
Kontor has nine areas and every control lives in one of them, which is what makes a chapter per area possible. Writing those chapters is a job of weeks, not an afternoon, and it is deliberately after 1.0.
Deliberately not
The list that says what this product is.
| Not doing | Why |
|---|---|
| A scripting language | There was one, and it was removed. A text somebody can hand-edit becomes a second source of truth that nothing can read back into the design. The steps are the program. |
| A loop with a condition, or a jump | “For each row” walks a finite set, so it cannot run for ever — and that is precisely why it is safe to have. A while is where a flow stops being something the narrator, the phone and the export can all say. |
| Ranges or a group-by in a case | A case looks at one value and its arms stand side by side. The moment an arm can say > 100 it is a language again, and there is already an If … otherwise for that. |
| Areas inside areas, folders inside folders | Hub → area → tab → pushed screen is already four deep. Every one of these is the next thing anybody asks for and the same wrong answer. |
| Absolute X/Y layout | It would fight the promise the Sizes check rests on — that a screen fits every iPhone. A control may fill the leftover height; that is the one degree of freedom. |
| A merge for two people editing one row | Last writer wins, and a refusal from the other side is honoured and explained. Version vectors are a distributed-systems answer to a question a no-code tool should not be asking. |
| Animation files (Lottie and the like) | Decided against on 8 September 2026: a third-party runtime in every exported app, for decoration. The export is meant to be code somebody else can pick up. |
| A licence check inside anything you export | Not a trade-off. It is the sentence in this product that will never be revised. |
| Android — for now | There is a concept written for it. It is not a port; it is a second generator and a second player, and it is not what 1.0 is about. |