diff --git a/README.md b/README.md index d992f0e..54d5432 100644 --- a/README.md +++ b/README.md @@ -100,7 +100,9 @@ and integrate at explicit boundaries. req: laws/002 req: auth/001 hemx-xtask -- app new --mobile PATH`. The starter carries a real app flow, typed host capabilities, command/event/projection recovery truth, and inspectable mobile release-kit commands without adding a native UI framework. - req: ceremony/006 + Use it for Rust-owned hypermedia apps; use explicit native shells/islands for + heavy native UI, games, camera-heavy flows, deep OS integration, or complex + offline sync. req: ceremony/006 req: host/002 - **PWA/offline/sync:** optional adapters may reuse generated targets/effects, but core hemx must not gain a mandatory client state graph or local app runtime. Local truth is commands/events/projections, not stored DOM patches or diff --git a/docs/recipes/mobile-release.md b/docs/recipes/mobile-release.md index 1b675e0..8d024e2 100644 --- a/docs/recipes/mobile-release.md +++ b/docs/recipes/mobile-release.md @@ -18,6 +18,22 @@ The created app includes the same `hemx-workout mobile-release` and `hemx-workout mobile-verify` commands, plus `MOBILE_STARTER.md` naming the host, recovery, and release-kit boundary. req: ceremony/006 +## When to use this path + +Use hemx mobile when the app is still a Rust-owned hypermedia product: forms, +lists, keyed partial updates, server-verified actions, installability, offline or +host recovery from app-owned command/event/projection truth, and a few explicit +host capabilities such as share, haptics, clipboard, notifications, or file +picking. The payoff is fewer moving parts: no client component runtime, no native +UI abstraction, no plugin marketplace, and no hidden mobile state graph. req: +ceremony/006 req: examples/006 + +Do not use hemx mobile as a replacement for apps whose product center is heavy +native UI, games, deep OS integration, camera-heavy capture/editing, complex +native navigation stacks, background services, or complex multi-device offline +sync. For those, keep hemx as a server/API surface or use an explicit native +shell/island where the browser should not own the interaction. req: host/002 + For the in-repository exemplar: ```sh