Skip to content

0027 own components first

github-actions[bot] edited this page Nov 18, 2026 · 1 revision

The app's first components are its own

Status: accepted · Implementation: done · Date: 2026-11-18 · Supersedes: 0013

Partly supersedes 0013, which said the app's components come from React Native Reusables: they will, once a component needs behaviour worth borrowing. The rest of 0013 stands. Built 2026-11-18: Button, ConfirmButton, Screen, Section, Card, Note, TextField, NumberField and SetRow.

Context

0013 said that in the app, components come from React Native Reusables, added when the first real screens need them. The first real screens are here (0006), and what they need is small: a button, a number field, a text field, a row and a screen with a scroll view.

React Native Reusables brings those, and with them its command-line tool, a set of primitive packages, an icon library, a portal for overlays, and its own colour names (background, primary, foreground), which are not the names in packages/ui. Each copied component would have to be rewritten to the project's colour names before use. For a button and two fields that is more to take on than to write.

The same question decided the navigation. Tabs want an icon each, and an icon library is one more dependency for three pictures.

Decision

  • The app's first components are written here, in apps/app/src/components, with Uniwind classes and the colour names from packages/ui. They are plain React Native views with accessibilityRole and labels set by hand.
  • React Native Reusables is added when a component needs behaviour that is hard to get right: a dialog, a menu, a select, a sheet. It is then copied in and renamed to the project's colours, in a pull request of its own.
  • Variants are a map from a name to a full class string, never a class built from parts, because Tailwind only finds classes that are written out.
  • The first screens are a stack, not tabs. The home screen links to history and settings. Tabs, with icons, can come when there are more places to go.
  • A destructive button asks twice in place: the first press changes its label, the second acts. React Native's alert does nothing in the web build, and nothing is built for one platform alone (0007).

Consequences

  • No new dependency for the first screens.
  • The app's components and the website's are still written separately, as 0013 says, and now neither side has a kit to keep them alike.
  • Accessibility is entirely the project's job here: roles, labels and hit areas are set by hand and have to be tested with VoiceOver and TalkBack.
  • When a kit is added later, these components are replaced or kept one by one. That is a cost put off, not avoided.

LibreBars

Clone this wiki locally