Mobile App

Mobile App

The mobile app package hosts the main user experience via Expo Router.

Primary routes

Route	URL	Auth required	Unauthenticated behavior
Landing	/	No	Public sign-in and onboarding entry
Onboarding	/onboarding	Yes	Redirected from landing when pairing is not yet verified
Feed	/feed	Yes	"Please sign in to view your feed."
Local Node	/local	Yes	"Sign in to join your Local Node."
Broadcast	/compose	Yes	Requires active session
Stream	/docustream	Yes	Requires active session for Pod-backed source management and stream ingest
Directory	/directory	Yes	Requires active session for community member discovery and Trust Circle actions
Backpack	/backpack	Yes	Requires active session for ACL updates
Profile	/profile	Yes	"Please sign in to view your profile."
Settings	/settings	No (partial)	Shows pod/wallet/prefs with signed-out state

Web navigation tabs

Authenticated web users see these tabs in the bottom navigation:

• Local
• Broadcast
• Stream
• Feed
• Directory
• Backpack
• Profile

Settings is intentionally excluded from tabs and accessed from Profile via the gear icon.

Landing page (/)

The landing page renders without authentication and includes:

• Canonical PWA entry on staging.nodezero.social
• Explicit wallet actions: Create a new identity or Restore from recovery bundle
• One-tap Sign In using a device Stellar challenge signature
• Create Your Node form: handle + notification email; no user-facing password
• Redirect logic:
  1. Signed-in + verified pairing attestation goes to /feed (or /local for seamless node sessions).
  2. Signed-in + unverified attestation goes to /onboarding.

New-user create flow (web)

1. User explicitly creates or restores the encrypted local device identity.
2. Wallet generates the ZK proof and encrypted claim on-device.
3. Provisioner creates the Pod/WebID, deploys and anchors the V3 lockb0x, and proves live Pod access before returning an inline NodeZero session.
4. Client derives the local commitment and compares it to the on-chain value; only a verified match enters Feed.

Session continuity note:

• Web bearer credentials remain memory-only. Browser restart restores through the host-only provisioner cookie, then repeats wallet and lockb0x checks.

Auth validation behavior (current implementation)

• Empty wallet: explicit Create/Restore choices; Sign In/Create Node remain disabled.
• Unknown Stellar identity: no_account guidance without fallback auth.
• Missing/corrupt encrypted wallet material: fail-closed recovery guidance.
• Lockb0x commitment mismatch: session is refused client-side.

UI navigation tabs and feature catalog

Local tab

• Purpose: local proximity messaging using H3 geo cells and relay-assisted P2P signaling.
• How it is used: user grants location, joins local node, selects recipient WebID, sends message.
• Data handling:
  • reads device location and converts coordinates into H3 cell state for UI and discovery context.
  • uses signaling relay plus peer channels for message exchange.
  • reads known peers from social graph connections.
  • raw GPS coordinates are not displayed or transmitted by this flow; H3 cell identity is used.

Broadcast tab

• Purpose: compose and target broadcasts by trust boundary.
• How it is used: user writes a post and selects one audience ring.
• Data handling:
  • FOAF audience reads social connections and writes JSON payloads to Pod outbox path via authenticated fetch.
  • Verified audience applies an additional verification gate before writes for recipient targets.
  • Local audience path initializes local channel targeting and currently does not persist post content to Pod from this screen.

Stream tab

• Purpose: aggregated downstream stream with filtering and save action.
• How it is used: user filters by source and saves selected items to Pod.
• Data handling:
  • supports RSS source registry actions (add source, enable/disable, delete source).
  • source configuration is persisted to the user's Pod and loaded on session resume.
  • source add flow can trigger Solid re-auth when write authorization is stale.
  • enabled RSS sources are ingested into the stream pipeline.
  • loads Pod-backed stream entries from JSON-LD and Turtle-compatible Pod container listings, with mock fallback content.
  • save action appends item payload as JSON-LD into public docustream container in the user Pod.

Feed tab

• Purpose: chronological timeline from followed users.
• How it is used: user opens feed and refreshes.
• Data handling:
  • reads social graph connections.
  • reads each connection profile and docustream activities.
  • maps items into feed cards and sorts newest-first by timestamp.
  • this screen aggregates reads and does not directly write feed content.

Directory tab

• Purpose: dedicated community discovery and trust-circle curation surface.
• How it is used: user refreshes discoverable members, connects to members, and adds/removes trust-circle state from the directory UI.
• Data handling:
  • reads provisioner-backed directory records and filters unlisted records.
  • merges results with connection-derived state for consistent connect actions.
  • trust-circle actions persist local state and do not auto-promote recipients for broadcast targeting.

Backpack tab

• Purpose: user-facing permission toggles for data containers.
• How it is used: user toggles Public Profile, Interest Graph, and Exact Location cards.
• Data handling:
  • updates UI state optimistically and reverts on ACL failure.
  • calls ACL update helper to write policy changes for relevant container targets.

Profile tab

• Purpose: edit and persist user profile metadata.
• How it is used: user edits display name, bio, avatar URL, external URL, and interests, then saves; user can also manage direct connections.
• Data handling:
  • reads profile from Pod into local form state.
  • writes profile back to Pod and re-reads after save.
  • save path uses effective session identity and can trigger Solid re-auth when write readiness is unavailable.
  • interest tags are normalized from comma-separated input.
  • NSFW modal and banners depend on Pod-backed profile NSFW flag.
  • peer view can compute shared semantic interest overlap.
  • social connections are loaded from the Pod-backed social graph and can be added/removed by WebID.
  • community directory interaction moved to dedicated /directory route.

Settings page (/settings)

Settings is partially accessible without authentication:

Section	Content	Auth state
Solid Pod	WebID	"Not signed in" when unauthenticated
Content Preferences	NSFW content toggle	Always visible
Embedded Wallet	Stellar public key + network status	Provisioning on load
Data Management	"Export & Erase Local Cache" button	Always visible
Account	"Sign Out" button	Always visible
Version	"NodeZero.social v0.2.0-testnet"	Always visible

Notes on data ownership model

• Pod-first application model:
  • profile, social graph, and stream content are read and written in the user-owned Solid Pod.
• Local application storage:
  • UX preferences and attestation/session artifacts are kept in local app storage mechanisms.
• Chain-linked identity context:
  • wallet and attestation flows bind Solid identity and Stellar-linked state while preserving environment-coherence constraints.

Contexts

• WalletContext: wallet lifecycle and registration.
• NodeZeroSessionContext: internal session lifecycle and Pod Access Proxy fetches.
• DiscoveryContext: location/discovery state.

Confirmed functionality

• Landing page renders hero and Solid sign-in flow.
• Route guards protect authenticated surfaces including feed, local, profile, and tab-only experiences.
• Feed screen now aggregates connections from Solid social graph and orders posts chronologically.
• Local Node screen uses relay-backed P2P signaling and supports target selection from known peers.
• Docustream screen supports RSS source add/toggle/delete and ingest into stream results.
• Docustream source add/ingest/render path is stable in staging after session continuity + Pod-listing compatibility hardening (2026-07-09).
• Directory tab is live between Feed and Backpack with refresh, connect, and Trust Circle actions.
• Profile flow now supports resilient save behavior during session restoration windows and exposes connection management actions.
• Settings renders wallet state, NSFW toggle, and account controls for signed-in and signed-out users.

Known gaps and resolution status

ID	Issue	Status	Fix
WR1	Wallet provisioning silently fails on web — expo-secure-store calls getValueWithKeyAsync (native-only bridge method); Settings shows "Provisioning…" forever	FIXED in testnet commit 778c37f	Platform.OS === 'web' guard in WalletContext.tsx skips SecureStore on web, using in-memory fallback
DS1	Stream ingest completed but no items rendered when Pod container listing returned JSON-LD	FIXED (2026-07-09)	DocustreamManager now parses JSON-LD + Turtle listings and normalizes/dedupes URLs before item fetch
PR1	Authenticated staging pass for Profile save + Connection List + Community Directory journeys	PARTIAL PASS (2026-07-09)	Save/readback + connection add/remove validated; keep rerunning profile rows as fixtures evolve.
J4	Blocking onboarding/authentication gate stability on latest staging workflow	PASS (2026-07-10)	qa:smoke:auth passed in staging workflow run #46 (step #28 success).

Notes

• Staging profile and chain settings are guarded for environment coherence.
• SWA deployment support is wired for the web build path.

Visual evidence

• Video: ../docs/videos/profile-and-settings.webm

Primary route files

• packages/mobile-app/app/index.tsx
• packages/mobile-app/app/onboarding.tsx
• packages/mobile-app/app/feed.tsx
• packages/mobile-app/app/directory.tsx
• packages/mobile-app/app/local.tsx
• packages/mobile-app/app/compose.tsx
• packages/mobile-app/app/docustream.tsx
• packages/mobile-app/app/backpack.tsx
• packages/mobile-app/app/profile.tsx
• packages/mobile-app/app/settings.tsx
• packages/mobile-app/app/_layout.tsx