We use Google Analytics to see which pages help people. No ads, no profiles. Privacy Policy
122 posts
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.
A durable source of truth and an in-memory one give the same answers until a process dies. Deciding which is authoritative is a design act, not a default.
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.
A stub is not an empty function. It returns plausible values, satisfies its interface and does no work, which is why emptiness checks never find it.
A failed-sync flag is not a retry mechanism. Three parts are needed: a connectivity signal, an enumeration of what failed, and backoff with a ceiling.
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.
When two writes reach one record and no code decides between them, the policy is whichever ran last. Name the resolver so the choice becomes reviewable.
