Mobile Launchpad Product Direction

Role

Mobile Launchpad is the early mobile product surface for Prox OS. It should feel like a high-frequency pocket entry, not a desktop clone.

The Launchpad home is a compact control surface for recent work, capture, AI chat, notifications, approvals, and dynamic view previews. It should help users enter or resume work quickly, then move heavier creation back to the Web Studio when needed.

Early Product Shape

Area	Direction
Today / Launchpad home	A single mobile home with pinned Studios, recent activity, AI entry, capture entry, and pending approvals.
Pinned Studios	User-selected Studios, Spaces, or Hubs that are safe to open quickly.
Recent apps / recent views	Lightweight recents list for app views, Studio cards, and approval surfaces.
App activity feed	Compact feed from Activity, Notifications, AI runs, and connector status.
AI chat entry	One-tap AI entry with visible context boundary and permission mode.
Capture entry	Note, image, link, voice, and file capture candidates, starting as mock or web-safe flows.
Notifications	Digest-style inbox before real push; priority and permission context stay visible.
Dynamic view previews	Render Studio View JSON cards, lists, summaries, forms, and approval blocks.
Open on desktop	Deep link into the Web Studio or current OS Shell route.
Continue on web	Resume a mobile preview in the full browser Studio.
Quick actions	Small action set with permission descriptions and confirmation where needed.
Lightweight permission review	Read requested scope, approve/reject suggestions, and audit high-impact actions later.

Five-second Actions

Mobile Launchpad should optimize for actions that can complete in one short session:

open Launchpad;
ask AI;
capture a note, image, link, or voice memo;
preview a Studio card;
approve or reject an AI-generated change;
continue on desktop.

Anything that needs deep layout editing, app composition, complex dashboard building, connector configuration, or public publishing should hand off to the Web Studio.

Feature Matrix

Capability	Now / mock only	Next / PWA candidate	Later / native candidate	Not now / risky
Mobile Launchpad route mock	Useful as a responsive UI prototype.	Can become PWA home.	Native shell may point to it.	Do not make it a second OS runtime.
Pinned Studios	Static mock data or local preference.	Persist with account or local PWA state.	Sync recents and pins through native shell.	Do not imply multi-user backend until shipped.
Recent apps / views	Read current registry and mock recents.	Store recent route/view refs.	Native deep-link history.	Do not keep large app state in mobile shell.
AI chat entry	UI entry with mock or existing Alma concepts.	Web AI session with visible permission mode.	Native notifications and secure context prompts.	Do not allow silent tool execution.
Capture	Mock capture cards and web-safe file input.	Link, note, image upload candidate.	Camera, photo library, voice, share extension, background upload.	Do not ingest sensitive data without consent and retention policy.
Notifications	In-app mock or activity feed.	Web notification design and preference model.	Push notifications and badges.	Do not ship push before privacy and permission copy exist.
Dynamic views	Render static examples from Studio View JSON.	Contract-driven renderer for trusted blocks.	Native renderer for the same schema.	Do not execute arbitrary remote bundles.
Approvals	Mock approval cards.	Approve/reject AI suggestions with explicit scopes.	Biometric confirmation for high-impact approvals.	Do not approve publish, deploy, payment, or external write actions without audit.
Studio Gallery	Static templates and verified view previews.	PWA discovery of official templates.	Native browsing of verified views.	Do not call it App Store or allow third-party execution early.
Continue on desktop	Link to Web Studio route.	Cross-device handoff when backend session exists.	Native deep links and universal links.	Do not claim seamless handoff before session model exists.

Interaction Rules

Keep mobile surfaces short, scannable, and action-oriented.
Prefer cards, feeds, segmented filters, and bottom-sheet style review flows over desktop windows.
Show provenance for AI summaries and connector-derived data.
Put permission descriptions near actions, not hidden in settings.
Treat publish, deploy, payment, sharing, destructive edits, and external writes as high-impact actions.