Mobile Experience Overview

Field capture surface

The mobile app is the frontline Builder Insights experience. It is designed for fast capture during live conversations, dependable local recovery, and sync behavior that preserves user trust in unpredictable network conditions.

The mobile app succeeds when

• capture feels quick enough for event-floor use
• users can save confidently even when connectivity is poor
• context and metadata stay accurate enough for downstream reporting

Experience map

Product pillars

Fast capture

The core flow should be usable in the middle of events, meetings, and travel without demanding long setup or perfect focus.

Offline resilience

Local persistence happens before remote sync so the user can keep moving when the network is unreliable.

Context-rich input

Event, session, sentiment, product area, and priority data make the captured insight valuable later.

Small-screen clarity

The UI should stay obvious and low-friction on a phone, not feel like a compressed admin tool.

Core workflow

1. Re-enter quickly

Home should restore session state and orient the user without making them think about system internals.

2. Confirm context

The user chooses or confirms the event context that will shape attribution, filtering, and later analysis.

3. Capture the signal

The app collects text or voice input, then adds enough structure to make the record useful across the platform.

4. Save locally first

The user gets immediate confidence that the insight is safe, even if remote sync is delayed.

5. Sync in the background

Queued items should reconcile safely when connectivity returns, without duplicates or confusing status changes.

6. Reflect value back

Dashboards and activity views should show users that field work becomes visible, measurable signal.

Technology stack

Area	Current choices	Why it matters
App framework	Expo SDK 54, React Native 0.81	supports cross-platform mobile delivery and native device workflows
Language and state	TypeScript, Zustand	keeps state management lightweight around capture and sync logic
Navigation	React Navigation v7	structures the major product surfaces and user flow
UI layer	UI Kitten, React Native Paper	balances mobile-friendly components with speed of implementation

Change-risk areas

Auth and session restore

This is risky because it affects both first-run access and whether queued work survives the next app launch.

Capture form state

Interruptions during input should not drop drafts, mislabel metadata, or create confusing half-saved records.

Offline queue behavior

Retry logic must stay predictable so the app does not lose writes or create duplicate records on reconnect.

Context selection

Small mistakes here ripple into admin filters, dashboards, and executive reporting later.

Best companion docs

Offline and sync

Use this for the save model, failure states, and QA verification path around reconnect behavior.

Mobile screenshots

Use this for a guided visual tour of the app and what to notice on each major screen.

Workflow walkthrough

Use this when you need to understand how mobile capture becomes admin-visible reporting output.

Repo-local references

For deeper implementation guidance, keep the repo-local docs in the mobile app repo as the closest source of truth for code-adjacent detail.