Mobile

Mobile is the next context on the roadmap, not a shipped one. This page is a promise with its reasoning shown: because every other runtime is already just an adapter, mobile will be too, and your domain will not change to reach it.

#Why it fits without a rewrite

A mobile app is another place a cause originates and an effect lands: a screen navigation, a tap, a background task. Under the Continuum that makes it a context like any other. The same handlers that render on the web and the same services that hold your logic are exactly what a mobile shell would drive.

#The intended shape

Mobile will follow the pattern you have already seen: a view layer on @stone-js/use-view(shared with the frontend), driven by a native adapter. The manifest gains one decorator; the domain gains nothing.

#Until then

Build your domain now, exactly as the rest of these docs describe. 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. Nothing you write today is waiting on it.