Skip to content
Text size
Text size

Introduction

Nomos is an offline-first application framework. It provides a local workspace for your app’s data and business rules, so people can keep working without a connection and synchronise changes when they reconnect.

You define your domain in TypeScript: the data, relationships, permitted actions and rules for combining concurrent changes. Nomos generates typed clients for TypeScript and Dart that your UI uses to read and update that data.

New to Nomos? Run the quickstart to create a project, compile its domain and check the local runtime. You do not need a hosted account.

Nomos is intended for apps where offline work is a requirement and the domain involves more than storing a few records. For example, an inspection app may need to relate sites, assets and observations, restrict who can change them, and let several people work independently.

The same business rules need to apply while a device is disconnected. Changes made on different devices also need a defined way to come together later.

A workspace holds the data your app needs, the rules for using it, and a history of changes. A local runtime checks permissions and business rules when the app reads or changes data.

Your UI calls the generated client. Accepted changes update the local state without waiting for a network request, and the app can subscribe to reads to keep its screens up to date.

Offline work uses the data and permissions available on the device. A local change does not mean another device has received it yet.

When devices reconnect, Nomos exchanges changes and applies the merge rules defined in your domain. For example, concurrent additions to a set of tags can be kept together, while a text field can use a last-write-wins policy.

Devices may show different states while disconnected. Once they have the same relevant history and rules, they calculate the same result. You choose the policies that make sense for your app.

You write the domain model and the user interface. Nomos supplies the generated client and the runtime for local reads and changes, permission checks, change history and synchronisation.

Your domain describes business actions such as adding an observation or completing a task. The generated client exposes those actions as typed calls, along with the reads your screens need.