These pages document the 18 AUP cross-device primitives from AUP_PRIMITIVES. Each name has its own page. They are not Web Device layout components and not the 42 Web-only widgets.
| Rule | Meaning |
|---|---|
| One page per primitive | Capability and sample boundary stay scoped to a single type |
| Document vs full-web | Document capability comes from DEVICE_CAPS_DOCUMENT, not from Showcase success |
| Sample honesty | Docs-safe samples show source + real render; unsupported types say so |
| Not widgets | frame, terminal, breadcrumb, … belong to the Web-only widget set |
Basic interface
| Primitive | Document (current) | Page |
|---|---|---|
view | native | view |
text | native | text |
media | native | media |
input | native | input |
action | native | action |
overlay | unsupported | overlay |
Structure and time
| Primitive | Document (current) | Page |
|---|---|---|
table | native | table |
time | partial | time |
chart | unsupported (no live chart) | chart |
map | unsupported | map |
calendar | unsupported | calendar |
Interactive surface
| Primitive | Document (current) | Page |
|---|---|---|
chat | unsupported | chat |
rtc | unsupported | rtc |
explorer | unsupported | explorer |
editor | native (no writable IDE promise) | editor |
canvas | unsupported | canvas |
surface | unsupported | surface |
afs-list | native renderer; data contract open | afs-list |
Read next
- Primitive taxonomy and evidence — 18 vs 42 widgets
- Device capabilities and degradation — chains and chart boundary
- Custom primitives and Web widgets — portability vs Web-only
- Live examples: scope and contract — what a docs sample may claim