Skip to main content
Fieldwork teaches itself in the app, one small tip at a time, instead of through a guide you read somewhere else. The founder set the shape on 2026-08-21: “a small batch of simple onboarding-flow fieldwork app suggestions (like all apps have), that are easily closed out.”

​
The tip design

On 2026-08-22 the founder ruled the design for every tip in the app, and likely the whole platform (Tooltip guides in Fieldwork App, FILD-100):
Tipkit iOS clone. That’s what we use for our tooltips/design/guides throughout the entire app (and probably the entire platform). Literally copy/mimic/steal the exact designs… Same concept. Similar sizes. Use current structure. No spike.
What that means on screen:
  • A frosted-glass card with Lucia’s round headshot, a bold title over a grey body line, and a ✕ in the top-right corner. No numbering, no “Next”, no “Skip”.
  • A small notch that points at the words it teaches, not at the middle of a wide row.
  • It floats; it never pushes. The card is placed off the element it points at and never covers that element. Nothing underneath moves when it appears or leaves.
  • One tip on screen at a time. The turn goes to the first tip you have not seen whose anchor is actually visible. Opening the drawer over an undismissed composer tip retracts it and hands the turn to the drawer’s tip; closing the drawer hands it back.
  • The clean home stays clean. No tip decorates the empty chat on launch, and no tip fights the cold-open Lucia Orbit.

​
The six tips

Read from the app’s tip layer at main@692a71c. Titles and bodies are the app’s own words. The composer tip is a small pulsing chip inside the composer that opens on tap, never on hover. The other five hang off the element they teach. The manual page’s tip sits over the page header and points at “What’s the issue?”; it only shows on a fresh, empty form that did not come from a chat.

​
How a tip goes away

  • Tap the ✕. The tip collapses back toward its notch. It counts as seen and does not return on its own.
  • Scroll the page. On a scrollable page such as Log Issues Manually, a real finger scroll dismisses the tip quietly. The founder’s ruling of 2026-08-28 (Tips dismiss on scroll, FILD-127): scrolling is engagement, the tip’s job is done. Scrolls the app performs itself, such as following the transcript or making room for the keyboard, never dismiss a tip.
  • Start using what it points at. Focusing the field under a tip dismisses it the same way; the founder ratified engagement dismissal on the 2026-08-29 testing pass.
Seen-state is kept per signed-in account on the device. A dismissed tip stays dismissed on that device; the app does not claim a dismissal it could not store.

​
Replay the guides

The drawer’s Replay the guides row (“Show the Fieldwork tips again.”) forgets every tip’s seen-state for the current account, so each tip presents again at its next first moment. It is a plain reset, not a tour: the tips come back one at a time, in the same order, at the same places.

​
Learn about Lucia Fieldwork

Beside it, the drawer’s Learn about Lucia Fieldwork row (“A short tour of what the app does.”) opens a short in-app sheet that walks through what the app is for. It is separate from the tips and does not change tip state.

​
Status

The tip layer is on the served build with all six tips enabled. Its parent record (Tooltip guides in Fieldwork App, FILD-100) is Finalizing, and the manual page’s tip closed as Completed on 2026-09-08 (Manual page gets a tip, FILD-108). Anything beyond these six, or any platform-wide adoption outside Fieldwork, is not claimed here.

​
See also

​
Verification basis

Verified on September 10, 2026 against the app source at 692a71c, the build the served bundle carried on that date, and the founder’s rulings on the cited records. Copy is quoted from the source; behavior claims are bounded to that build.