The phone app
What it is meant to show
Section titled “What it is meant to show”The same as the dashboard, for the pocket: the verdict, the Ledger Line, what needs you and what comes due; a thing; money; and the Brief, to copy or share.
The pictures below are design mock-ups, drawn from the app’s design specification. They are not screenshots of an app.






The widget
Section titled “The widget”A home-screen widget is planned in a small and a medium size: the verdict, the line and the month’s amount. It can be set up per scope, so several can lie side by side — one per client, for example. The widget has room for one amount and shows cost only.


“You know about”
Section titled ““You know about””In the app you set something that needs you aside with a swipe: until tomorrow, or for a week. It stays open and is listed under “You know about”, but no longer counts as news — an overdue invoice need not strike you again every morning. This applies on that phone only, and the item comes back by itself when the day is there or when it gets worse.
Pairing
Section titled “Pairing”Pairing is the part that exists on the core’s side today.
./nota pair operateThis prints a code that is valid once, for ten minutes. The app redeems it and gets a token of its own; the role (read or operate) is fixed when the code is created.
./nota device list./nota device revoke <id>Unpairing deletes the device’s key and push token; it does not merely disable them.
Push, as designed
Section titled “Push, as designed”Notifications are encrypted between your core and the phone. The relay that delivers them, and Apple, cannot read them: the relay sees a push token, a ciphertext, whether it is urgent, and an opaque id. This is built, but the relay is not running, so no push arrives today. Until then: ntfy or a webhook.