Where this starts

Every app we have built had the same shape. A database. An API in front of it. A UI in front of that. And between each pair, a layer of glue that restated what the layer beside it already knew: the fields, the rules, who may see what.

FrontierJS starts from the other end. You write the schema — one .lite file — and the rest is derived from it. The model knows its fields, so the API validates them. The model knows who may read a row, so every query is filtered before it runs. The UI asks the same schema what a form needs, so the form is already right.

Three realms, one seed

• Data — the Model, declared in the schema, with access on it.
• API — the Service, which a model gets for free and you extend.
• UI — the Resource, the same data in the browser, live.

What this journal is

FrontierJS is not released yet. It is pre-alpha, and we would rather show the work than announce it. These entries are the decisions, the dead ends and the things that broke — written while they are still fresh.

It is coming soon. Until then, this is where you can follow along.