Say once that there is no phone

Three statements disagreed. §1.2's platform table said "phone
supported"; §3.5 said phones were out of scope and cited §1.3, which
does not mention them; D15 said "no phone" and gave the reason. D15 is
the decision, so the other two now point at it and say the same thing:
the build runs on a phone, and nothing is designed for one.
This commit is contained in:
2026-09-19 12:25:03 +02:00
parent c826fed605
commit 3692306fd3
+2 -2
View File
@@ -22,7 +22,7 @@ metadata, and exports finished images.
| Platform | Priority | Notes |
|---|---|---|
| Linux desktop | Primary | X11 and Wayland. Development and reference platform. |
| Android | Primary | Tablet-first; phone supported. Shares the image core. |
| Android | Primary | A 12-inch tablet (D15). Phones are not a target: the build runs on one, and nothing is designed for one. Shares the image core. |
Other platforms (Windows, macOS, iOS) are explicitly out of scope for v1, but the architecture
must not foreclose them. In practice this means the GPU abstraction and the image core must not
@@ -601,7 +601,7 @@ colours on the second display is a correctness defect, not a polish item.
DarkRoom ships **one adaptive interface**, not separate touch and desktop applications. A single
Slint codebase reflows by available space and input modality, guaranteeing feature parity by
construction. Phones are out of scope for v1 (§1.3); the layout family spans tablet and desktop.
construction. Phones are not a target (D15); the layout family spans tablet and desktop.
**FR-UI-1 — Layout breakpoints.** The interface adapts across at least two layout classes: