C++ SCHX ยท rev 4
Web Bro ยท current

Web Bro installation internals

How an immutable release becomes verified local app storage without fake installation progress.

currentstatus
Runtime developers ยท App developersaudience
School-GIT docssource
SCHX nativeruntime
SCHX / FEATURE LAYER

System flow

1

Download manifest

2

Stream files

3

Measure real bytes

4

SHA-256 verify

5

Write OPFS/IndexedDB

6

Save metadata

7

Install receipt

SCHX / FEATURE LAYER

Source map

  • lib/cdn/apps/client-installer.ts
  • lib/cdn/apps/client-installed-store.ts
SCHX / FEATURE LAYER

Manifest-driven install

The client starts from the immutable install manifest, streams each runtime file from the server and checks the received bytes against the expected SHA-256 digest.

SCHX / FEATURE LAYER

Local persistence

Runtime files are written to OPFS when available. App-package storage can fall back to IndexedDB when OPFS is unavailable. Installed-app metadata is stored separately so the desktop can enumerate and launch installed applications.

SCHX / FEATURE LAYER

Observable install completion

After installation the client emits the app-change event and records an install receipt. Progress is based on real received bytes rather than a decorative timeout.

SCHX / FEATURE LAYER

Related documentation