docs(requirements): split workout release scope
Split oversized examples/006 into command-surface, generated-helper, and mobile-boundary requirements. req: examples/006 req: examples/010 req: examples/011
This commit is contained in:
@@ -3,7 +3,7 @@
|
||||
The Workout exemplar is the production-shaped mobile path for hemx. It stays
|
||||
boring on purpose: hemx builds the server app and writes mobile shell metadata;
|
||||
Android/iOS SDKs, store signing, provisioning, and submission remain external
|
||||
vendor work. req: examples/006
|
||||
vendor work. req: examples/011
|
||||
|
||||
## Command surface
|
||||
|
||||
@@ -26,7 +26,7 @@ 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
|
||||
ceremony/006 req: examples/011
|
||||
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user