Stone.jsDocs
Paradigm

Adapters

Mobile

Mobile is a planned adapter, not a shipped one. It earns a page because the reasoning is worth stating: since every other runtime is just an adapter, mobile will be too, and the domain you write today will reach it without a rewrite.

#Why it fits without a rewrite

A mobile app is another source of causes and sink of effects: a screen navigation, a tap, a background task. Under the Continuum that is a context, and the same pages and services that run on the web are what a mobile shell would drive, through use-view.

If the domain never named the web, it never has to un-name it to run on a phone.

#The intended shape

Expect the familiar move: install the adapter, add its decorator to the manifest, and the view dimension renders natively. The manifest gains one line; the domain gains nothing.

#Until then

Build your domain now, exactly as this manual describes. When the mobile adapter lands, it will collapse the domain you already have onto phones, the same way the edge and agent adapters did for their runtimes.


Stone.js

Your app exists in every runtime. Until you run it.

An open-source project by Stone Foundation
Created by Mr. Stone (Evens Pierre)