docs: surface the 1.1.0 features the README never listed - #87
Merged
Conversation
ScrollEdgeBlurView and accessibilityMode both shipped in 1.1.0 and neither appeared in the Features list, so anyone scanning the README missed them entirely. llms.txt was worse — it still announced a single component, which is what LLM ingestion reads first. Also notes zero runtime dependencies. Deliberately NOT a row in the comparison table: every competitor checked (expo-blur, @react-native-community/blur, expo-glass-effect, @callstack/liquid-glass, @uginy, react-native-android-liquid-glass) also ships zero runtime deps. It is table stakes for a native module, not a differentiator, and a table row where all four columns are a tick reads as padding. It stands as a plain trust signal instead. Adds llms.txt to the CI docs gate — it is a docs file but was forcing lint and build-library to run on every edit.
LiquidGlassContainer shipped in 1.1.0 as the headline feature and had no docs page — it appeared in llms.txt and nowhere else under docs/. Every other feature has one; there is even a page for the tab bar. The merging claim is what the README, the comparison table and every outreach draft now lead with, so the one thing a reader could not do was read how to use it. Documents what the summary elides: spacing=0 is the off switch AND the unsupported-platform behaviour, so there is nothing to feature-detect; any glass descendant merges, not just direct children; the merge is analytic, so a moving child costs a uniform upload rather than a distance-field rebuild, which is why this animates and secondaryShape does not; and position comes from getLocationInWindow, so transform-driven animation works. Also the three Android limits, each with its reason — bodies are rounded rects from size and borderRadius (a custom shape merges as its bounding rect), at most 8 children merge and the rest keep drawing their own glass rather than vanishing, and the merged surface adopts the first child's material because one surface can only have one. Wires it into the curated nav, the docs index (whose feature list did not mention merging either), and both llms.txt files.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #86. Three gaps found while checking whether the zero-runtime-deps claim was documented.
ScrollEdgeBlurViewandaccessibilityModewere missing from FeaturesBoth shipped in 1.1.0. Neither appeared in the README's Features list, so anyone scanning it missed them.
llms.txtwas worse — it still announcedComponent: <LiquidGlassView>, a single component, which is the first thing LLM ingestion reads. It now names all three.Zero runtime dependencies — mentioned, but deliberately not in the comparison table
I checked every competitor:
All of them ship zero runtime dependencies. It's table stakes for a native module, not a differentiator, and a comparison row where all four columns are a tick reads as padding. It's in the Features line as a plain trust signal instead.
CI gate
llms.txtis a docs file but wasn't in the docs gate, so editing it forcedlintandbuild-libraryto run. Added.