Build excellent task UX

Nomos generates a typed application from the task law. That application is the service layer and the local state your UI needs—not another transport object to wrap in repositories and caches.

const { todoList } = await application.createList({
  title: "Launch the docs",
});

const { todo } = await application.addTodo({
  listId: todoList,
  text: "Write the offline chapter",
});

const stop = application.watchTodosByList(
  { listId: todoList },
  (tasks) => renderTaskList(tasks),
);

The write is local. The watch re-emits as the participant’s lawful world changes. Network transport is not on the interaction path, so the UI can remain useful on a train, in a tunnel or during an outage.

Product features, not framework plumbing

The generated surface already corresponds to recognizable task-app interactions:

await application.renameTodo({ todoId: todo, text: "Explain offline work" });
await application.tagTodo({ todoId: todo, tags: ["docs", "launch"] });
await application.toggleTodo({ todoId: todo, done: true });

const open = await application.openTodosByList(todoList);
const history = await application.describeHistory(todo);

The application also exposes point-in-time reads, activity, undo and redo through the same generated business surface. A task detail panel can therefore show its timeline; an activity view can explain who changed what; an undo interaction can correct accepted work without inventing a separate history model.

Collaboration remains business language

Sharing a list or one task is still a typed business action:

await application.shareList({
  listId: todoList,
  userId: collaborator,
  role: "editor",
});

await application.shareTodo({
  listId: todoList,
  todoId: todo,
  userId: reviewer,
  role: "viewer",
});

The list hierarchy and per-task exception are enforced by installed law at every door. The frontend may hide a disabled control for good UX, but that control is not the authority boundary.

Where the UX advantage comes from

A competitive task application lives or dies on interaction quality: keyboard speed, instant updates, useful views, trustworthy collaboration, history that answers questions and upgrades that do not strand old work.

Nomos does not design those interactions for you. It removes the distributed-systems tax that so often makes them unreliable or expensive to add. The product team can spend its complexity budget on a better task experience while the generated application keeps the underlying model, history and authority coherent.

Return to One last to-do list to see how those pieces become one progressive tutorial.