playablelabs-platform-compat
PlayableLabs: Record Platform Compatibility When Adding or Upgrading a Tech or Lib
Section titled “PlayableLabs: Record Platform Compatibility When Adding or Upgrading a Tech or Lib”Advisory (a kit ships no hooks; the real gate is a device smoke, below). A playable runs inside ad-network webviews on old and low-end phones, so “works in my desktop Chrome” proves nothing. Whenever you add a library, framework, API, language feature or build target, or bump one across a major/minor, write down its compatibility limits in the SAME change and check them against the target devices.
- Record the limits. In the PR description (and the skill or doc that owns the stack, if one exists) list:
minimum browser/webview versions (Android System WebView, Chrome, iOS Safari/WKWebView), required web APIs
(WebGL1 vs WebGL2, WebAssembly,
SharedArrayBuffer/cross-origin isolation,OffscreenCanvas, Web Audio,fetch, ES target such as ES2017 vs ES2020+), and any device-class limit (GPU/texture size, memory, no hardware acceleration). Cite the source (MDN, caniuse, the lib’s own docs or release notes, with the version read), never memory. Unknown limit: writeunverified, do not omit it. The standing record for the techs and libs already in use is skillt1k-playablelabs-base-engine-hosts,references/compat-ledger.md: update its row in the same change, and replace aMISSINGonly with a sourced value. - Compare with the target floor. Check the limits against the supported floor of the packer and of each
network adapter (
t1k-playablelabs-base-networks) and the build ceiling (t1k-playablelabs-base-pack). Anything above the floor needs a feature-detect plus a fallback, or an explicit decision to raise the floor made by the user, not by you. - Match the transpile target. A lib or syntax newer than the build’s ES target must be transpiled or rejected; a bundled dependency that ships untranspiled modern syntax breaks old webviews at parse time with no visible error.
- Respect the network constraints. No dependency may need network access at runtime, a service worker, or APIs a network sandbox blocks; check the extra bytes against the size ceiling.
- Prove it on a device class. Pass the smoke (
t1k-playablelabs-base-smoke) and, for anything touching rendering, audio, wasm or input, run one low-end Android and one iOS device or emulator profile. Record which devices ran. Not run: saynot device-tested. - Cocos zero-change still applies: gate anything new to the web host path; see rule
playablelabs-cocos-zero-change.md.