Surfaces
An application is met on a surface. Today the web is the delivery path for business applications, and a declarative native interface is in construction, games first. The rest are directions, and the interface law judges all of them.
What exists today
The web (built)
The plan of record is plain: the web tier remains the delivery path for business applications. The applications that run use web-based tools, with a vendored toolkit and no build step, installed as an app on a phone, opened in a desktop shell or an Android shell.
The native interface (in construction)
An engine above graphics, with an interface authored declaratively as text, right-to-left writing and accessibility as its standouts. Its order of attack is in-scene and game surfaces first, and operator-facing business software only when accessibility and input methods are funded as multi-year work.
What are directions
- A terminal, for the people and the AI agents who work in one.
- Voice: speech synthesis exists in the engine; speech recognition and telephony do not.
- Messaging, the app already on a person's phone: told on the conversations page, designed and mostly absent.
- Devices: a machine declared as software first, on the sovereignty page.
The Softanza way The interface grammar is closed: a new surface adds renderings and never verbs. Every surface here is judged by the same interface law, whether it is a page, a window or a thread of messages.
in construction The native plane's renderer and its accessibility tree are read from the library's files and its eight guards; the plane was read and not seen on a screen for this page. The packaged phone shell and the desktop web view are absent from what the envelope generates today; the applications that run carry their own.