Expand description
QappManifest — the transport-neutral definition of a companion qapp.
A qapp is a person-defined mini-application (a cooperative front, a health tracker, a journal, a directory, …) that is ultimately delivered to a phone as an installable PWA wrapping a WebAssembly bundle. This module defines what a qapp is: its identity, the least-privilege capabilities it requests, a content-addressed reference to its wasm bundle, and the presentation metadata a PWA needs (icons, colours, display mode).
It does not build wasm and it does not deliver anything — it only describes. The wasm
bundle is referenced by path + SHA-256 hash + size (see WasmRef); producing that bundle
and serving it over a secure origin are separate, later pieces (see the module doc in
qapp_package/mod.rs).
Structs§
- IconRef
- An icon reference for the PWA manifest / home-screen install.
- Qapp
Manifest - The transport-neutral definition of a qapp. Everything a PWA generator or a delivery layer needs to describe, present, and integrity-check the qapp — without knowing how it is served.
- WasmRef
- A content-addressed reference to the qapp’s compiled wasm bundle. This module references the
bundle; it does not produce it.
sha256_hexbinds the manifest to an exact artifact so a later delivery layer can verify integrity.
Enums§
- Capability
- A least-privilege scope a qapp requests. An empty
capabilitieslist is the safest default (the qapp is granted nothing). Extensible viaCapability::Custom. - Qapp
Kind - The kind of qapp. Extensible:
QappKind::Customcarries an arbitrary id so new kinds need no code change. Serializes insnake_case;Custom("x")serializes as its inner string.