We use Google Analytics to see which pages help people. No ads, no profiles. Privacy Policy
138 posts
MaterialTheme provides three CompositionLocals and a handful of defaults. Understanding its actual shape explains how components pick up styling, why hardcoded values break dark mode, and what a custom theme has to replace.
Material 3's SearchBar transitions into a full-screen suggestion surface, which makes it a navigation concern. Chips come in four semantic variants, and the assist/filter/input/suggestion split matters.
Compose's date and time pickers are straightforward components hiding a genuine trap: the selected value is UTC-midnight epoch millis, and converting it naively shifts dates by one in most of the world.
Compose gives you progress indicators; it doesn't tell you when to show one. Duration decides: under 300ms show nothing, over a second show progress, and never let an indicator replace content that could be a skeleton.
NavigationBar, NavigationRail and the drawer are three presentations of the same destination list. Window size decides which, and NavigationSuiteScaffold does the switching — with rules about how many destinations belong there at all.
Dialogs and bottom sheets are composables that exist conditionally, not imperative calls. Modelling them as state fixes the rotation bug, the double-show bug, and the question of where the result goes.
Compose has two TextField APIs. The String + onValueChange pair has real problems with cursor position and asynchronous updates; the TextFieldState overload solves them and is now the recommended one.
Checkboxes, radio buttons and switches encode different semantics — multiple choice, exclusive choice, and immediate effect. Choosing by appearance produces interfaces that mislead, and the accessibility story differs too.
Material 3 ships five button styles plus the FAB. They form an emphasis hierarchy, and the selection rule is about how many actions compete on a screen rather than about how each one looks.
A structural shell passes an AST scan and a unit test while rendering nothing the mockup specified. Only a rendered check can tell the difference.
A route with no caller compiles, registers and never runs. Reachability is a graph property, so no per-file check can see it and nothing fails.
A literal spacing value is a token nobody named. The cost is not inconsistency now but that a redesign cannot distinguish values that happen to match.
