Launchpad
Launchpad is the personal command center after login. It is an official Prox OS
Position
Launchpad is the personal command center after login. It is an official Prox OS surface, not a Studio. It can reuse Studio cards, activity timelines, app launch affordances, and dataset summaries, but it does not own Scenes and should not be described as a Studio Engine.
Why It Exists
Prox OS should not default to a social feed or a public community stream. The early product should help a user continue work, inspect their resources, review notifications, check connector health, and create or open Studios.
Launchpad answers:
- What should I continue?
- What is my Home workspace?
- Which Studios are recent or pinned?
- Which Datasets and Library assets matter now?
- Which connectors need attention?
- What did Alma or the system suggest?
- What changed recently?
- What usage or cost signal should I notice?
Home Workspace
Launchpad is the official default surface, but a user may choose a Home workspace. The default-after-login preference can be:
- Launchpad.
- Last opened Studio.
- Specific Studio.
Onboarding can generate a first Studio and offer to make it the Home workspace. This remains a user preference and should eventually be persisted per owner.
Tabs, Not Scenes
Launchpad uses tabs such as Overview, Studios, Activity, Library, Datasets, Connectors, and AI Suggestions. Scene switching belongs inside a Studio session. Launchpad should not create its own Scene model.
Reusable Activity
Launchpad Activity should reuse the platform activity timeline primitives so the same event model can later power Studio Activity, profile activity, and organization activity. It should not copy a second timeline implementation.