Mobile writing + Capture Inbox — what belongs in a five-second WorldScript workflow?

[qnbs]

Why this exists

Issues #484 and #487 point toward a mobile writing and capture experience. This Discussion explores what belongs in a five-second WorldScript workflow without treating a phone as a compressed desktop screen.

Current state

A useful flow could begin at the OS or browser share target and land in a local Capture Inbox. From there, authors might make quick scene or note edits, open a distraction-free mobile editor, capture offline, and later organize the material in the wider project. Phone and tablet needs may overlap without being identical.

Product decision space

Please consider virtual keyboards and safe areas, phone versus tablet layouts, quick character/world references, offline capture guarantees, and an optional AI layer that is lazy-loaded rather than a startup requirement. The mobile MVP should preserve writing focus, reliable persistence, and clear handoff into the desktop-oriented project model.

Role perspectives

Role-perspective note: The viewpoints below are maintainer-curated, AI-assisted design lenses. They are not separate community members, votes, or evidence of consensus.

• 📱 Mobile writer: capture and continue writing in seconds with minimal navigation.
• ✍️ Author: preserve meaningful scene, note, character, and world context without breaking flow.
• ♿ Accessibility: keyboard, focus, touch target, screen reader, zoom, orientation, and safe-area behavior.
• ⚡ Low-memory/mobile performance: fast startup, bounded memory, offline resilience, and lazy loading.
• 🔐 Privacy for captured/shared content: local capture, sharing boundaries, and optional AI use must be visible and controlled.

Questions for the community

• Which capture sources and quick edits matter most?
• Should Capture Inbox items be notes, scenes, tasks, or an explicitly typed intermediate?
• What should differ between phone and tablet?
• Which references are essential while writing on mobile?
• When is optional AI useful, and when would it distract or threaten privacy?

Relationship to implementation

This is product and UX exploration for #484 and #487. Those Issues remain the implementation and acceptance trackers; this Discussion does not change priority, roadmap admission, acceptance criteria, or execution sequencing.