@oxy.so/bloom 3.0.0 → 3.0.1

package/docs/glass.mdx

@@ -138,3 +138,18 @@ Gate: `src/theme/__tests__/chrome-glass.test.ts`, which pins the two floors to t
 An island also mounts a `ControlSurface` with `material: 'glass'`, so controls inside it paint flush. That is the material's rule rather than a preference: a translucent pane inside a translucent pane composites two alphas and two blurs for one pane's worth of depth, and on Android the second blur is not available at all.
 
 Internal (`glass/` is not a published subpath). It is reached through `ButtonGroup`'s `glass` variant and `PageHeader`'s floating presentation.
+
+### On a device: tint, and no blur
+
+Measured on a **Pixel 8a** over a hard 10dp stripe pattern, sampling the same rows inside a chrome island and on the bare stripes beside it:
+
+| backdrop stripe | bare | inside the island |
+| --- | --- | --- |
+| white | 255 | 254 |
+| black | 0 | 210 |
+
+The backdrop contributes **44 of 255** — the pane is translucent — and the stripe **edge stays sharp**, where a blur would smear a 26px transition. That is the Android behaviour this file describes: `expo-blur` is asked for no blur method, so it paints its tint and nothing else. Nothing in `logcat` asked for one or reported a crash.
+
+The composite works out at ≈**0.83** opacity against the web pane's 0.72 plus sheen. The difference is `expo-blur`'s own tint — one `intensity` drives it together with the radius and a caller cannot decline it — which is the platform gap `GLASS_BLUR_INTENSITY` documents, appearing exactly where it said it would.
+
+The ramp `PageHeader` draws over the same material was checked for the `stopColor` alpha trap at the same time: **0 achromatic rows of 311** in both modes, so the hue survives the SVG renderer.

package/docs/page-header.mdx

@@ -215,7 +215,52 @@ And the island fill in light mode is the card fill over a near-white page — th
 
 ![The islands over a photograph, title held back](./page-header-islands-photo.png)
 
-**Not verified on a device.** Every number above is Chrome on Linux. iOS and Android have not been run for this change: the material is `expo-blur` on both and is unchanged from the `GlassSurface` the library already shipped, but the geometry, the safe-area padding, the top-edge claim and the scroll linkage have only been exercised in jest and in a browser. Android additionally paints **no blur at all** here, by the design described above, so what a device would show is the tint, the hairline, the sheen and the rim.
+### Android, on a device
+
+Run on a **Pixel 8a** (Android, `akita`) through Expo Go SDK 56, against the
+**published** `@oxy.so/bloom@3.0.0` from npm rather than a local build — which is
+what makes it a consumer's result rather than a rehearsal of one.
+
+| property | result |
+| --- | --- |
+| the edge ramp, light | rgb(231,224,231) → rgb(29,59,83), travelled **202** of 255 |
+| the edge ramp, dark | rgb(18,17,22) → rgb(29,59,83), travelled **61** of 255 |
+| no horizontal cut | largest single-row step **1**, monotonic, in both modes |
+| the ramp is CHROMATIC | **0 achromatic rows of 311**, in both modes |
+| a matched `scrimColor` | travelled **1** over its own page colour |
+| the island is translucent | the back capsule reads 244 over the page, **215** over a photograph |
+| the island does NOT blur | see below |
+
+The third row is the one worth having. `react-native-svg` reads `stopColor` for
+its RGB and **discards any alpha inside it**, which once painted an Android pane
+as a white-to-black wipe with R=G=B on every row while every gate stayed green
+(the mechanism is on `GLASS_SHEEN` in `theme/glass-colors.ts`). Counting
+achromatic rows is the direct refutation, and there are none: the ramp carries
+the page's hue all the way down.
+
+**No blur, measured rather than asserted.** Over a hard 10dp stripe pattern,
+sampled at the same rows inside the back capsule and on the bare stripes beside
+it:
+
+| backdrop stripe | bare | inside the island |
+| --- | --- | --- |
+| white | 255 | **254** |
+| black | 0 | **210** |
+
+Two things follow. The backdrop contributes **44 of 255** — about 17%, so the
+pane really is translucent. And the stripe EDGE stays sharp inside the island: a
+blur would smear a 26px transition, and there is none. That is tint only, which
+is the documented Android behaviour, and nothing in `logcat` asked for a blur
+method or reported a crash across five screens in both modes.
+
+The native pane is slightly more opaque than the web one (≈0.83 against 0.72),
+and that is `expo-blur`'s own tint, which one `intensity` drives together with
+the radius and which a caller cannot decline — the difference
+`GLASS_BLUR_INTENSITY` documents, showing up where it said it would.
+
+**iOS is still not verified on a device.** The material is `expo-blur` there
+too and unchanged from the `GlassSurface` the library already shipped, but
+nothing in this change has been run on an iPhone.
 
 ## Not included
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oxy.so/bloom",
-  "version": "3.0.0",
+  "version": "3.0.1",
   "packageManager": "bun@1.3.14",
   "description": "Bloom UI — Oxy ecosystem component library for React Native + Expo + Web",
   "main": "lib/commonjs/index.js",