The Switzerland Field Lesson

"On a cable car, in the rain, with cold hands, you have about five seconds and one thumb. Design for that, or you get nothing."

What the Field Actually Demands

The whole mobile design rests on one hard-won observation: travel logging cannot assume time, posture, attention, or keyboard tolerance. The desktop fantasy of writing a thoughtful daily entry does not survive contact with an actual trip. You are walking, tired, managing luggage and a companion, and the moment worth remembering is happening right now and will be gone in seconds. If capturing it takes more than a few taps, you will not do it — and the memory the engine was built to hold simply never gets created.

A Capture Surface, Not a Dashboard

So the mobile home is not a shrunken desktop dashboard. It is a purpose-built capture surface with a different information density, a different interaction budget, and a different failure model. The rule is that leaving a breadcrumb must cost almost nothing: capture must not require a title, tags, categories, or a Pippa response. You type a fragment (or dictate it — voice arrives as text through the phone's dictation, so it earned no separate kind), optionally attach a photo, and you are done. The active journey, the schedule date, the capture time, the time zone, and the location are all attached automatically. You bring the thought; the engine brings the metadata.

Pippa Stays Quiet Here

There is one more discipline that protects the field moment: Pippa is normally silent during capture. A breadcrumb appearing in the local feed is success — model latency must never interrupt motion. If Dad wants help, he can explicitly invoke a small macro (correct this, translate it), but the response is a preview beside the untouched draft, and the plain Crumb action never waits for a model call. The engine's most important job while you are moving is to get out of the way. Interpretation is for the hotel; capture is for now.

Code

The capture contract: what it must NOT require·text

To leave a breadcrumb, you must NOT be forced to provide:
  - a title
  - tags or categories
  - a place name (location is captured automatically when allowed)
  - a Pippa response (she stays quiet; latency never blocks capture)

Attached automatically, so you don't have to:
  - active journey            - capture time + time zone
  - schedule / capture date   - location (foreground, when permitted)

# You bring the fragment. The engine brings the metadata.
# Every required field you'd add is a field that loses the moment.

Exercise

Time yourself capturing a single thought in your usual notes or journaling app while pretending you're walking and distracted — no sitting down, one thumb. Count the taps and the required fields. Would you actually do this in the rain on a cable car? Every tap beyond the first two or three is a moment you'd lose in the field.

Hint

The brutal test is the five-second window with one thumb. If your capture flow needs a title, a category pick, or a two-hand keyboard, it was designed at a desk. Field capture is measured in taps-to-saved, and the target is 'almost none'.