OCES · iOS PWA and Legacy Port

Problem

Initial situation

A modern iOS PWA and older browsers require different runtime, offline and distribution concepts. A shared version or device acceptance would obscure those differences.

Constraints

Boundary conditions

• Version and test the modern iOS PWA separately from the standalone legacy port
• Legacy port: trusted own code only; frame restart is not a security sandbox
• Device acceptance applies only to the confirmed variant and configuration, not all browsers; cache identifier is not the product version

Solution

Solution

The modern OCES PWA targets iOS and provides an editor, preview, console, import and demos with service-worker-backed offline delivery. The independent legacy port uses ES5 and direct local file execution without a service worker or web server. Both variants serve local JavaScript experiments but have separate runtime and test statuses.

Architecture

Architecture

• Modern iOS PWA: web app manifest / standalone display / service worker and versioned offline shell
• Modern iOS PWA: editor / preview / console / import / messaging contract and run association
• Standalone legacy port: ES5 / direct file:// execution without service worker or server
• Legacy port: frame lifecycle / storage fallback / manual export / separate test session

Result

Result

Modern iOS PWA: successful iOS acceptance under iOS 27.2 confirmed by the user on October 29, 2026; not rerun here. Standalone legacy port 1.0.0-rc1: error-free execution on an HTC with custom ROM / Android 4.1 in Firefox was tested and documented, also confirmed by the user. The legacy report additionally lists 14/14 assertions, 7/7 self-tests, an ES5 gate and manifest check; not repeated here. No blanket approval for all iOS/Android versions or browsers. Exact hardware/browser builds and iOS test mode were not specified in this overview.