24. Platform Strategy
Platform Strategy requirements from the authoritative Glitchpad Technical Specification.
All four target families are Tier 1 for v0.1.4. A Tier 1 platform requires an official artifact, native build host, automated shared suite, adapter tests, installation smoke tests, core user-flow evidence, version and license evidence, and a named support baseline.
| Platform | Runtime baseline | Architectures | Official v0.1.4 artifacts | Native WebView |
|---|---|---|---|---|
| Windows | Windows 11 | x86_64 | NSIS installer, portable ZIP | WebView2 Evergreen |
| macOS | macOS 13+ | arm64 and x86_64 universal | Ad-hoc-signed application in a non-notarized DMG | WKWebView |
| Linux | glibc baseline built on Ubuntu 22.04 | x86_64 | AppImage, Debian package | WebKitGTK 4.1 |
| Android | Android 7.0+, min API 24, target API 36 | arm64-v8a and x86_64 required; universal package | Universal APK, split ARM64 APK, AAB | Android System WebView |
Windows file associations and command-line delivery route to the running instance. macOS handles open-document application events. Linux follows freedesktop MIME registration and desktop-entry conventions. Android registers only released format MIME types and extensions and accepts view/open/share intents according to provider grants. .mmd and .mermaid associations and intent filters activate only when the standalone Mermaid capability reaches stable status on the complete Tier 1 matrix.
Windows ARM64 and Linux ARM64 are planned platform expansions after v0.1.4 and require their own build, package, and device evidence. iOS is outside the current platform boundary.
System WebView versions are recorded in diagnostics and test evidence. Glitchpad does not bundle a browser engine to mask obsolete or broken system WebViews; unsupported runtimes receive a precise prerequisite error.