Compact Hub: design review
This review covers the customer-facing marketplace, account, connections and tool workflows. It is a prototype with fictional data. Google sign-in, generic token connections, custom MCP review and account recovery are proposed flows, not claims about deployed backend features. The existing live pilot is separate.
Open the interactive prototype. Use the screen selector to inspect states directly, or follow the ordinary navigation. Reload to reset sample state. Never enter real credentials.
Review tasks
| Task | Expected outcome |
|---|---|
| Return to an existing connection | Locate your account and selected profile; open the saved connection without entering a key again |
| Connect a new MCP | Inspect a sample result before sign-in; preserve the selected MCP through Google and Authenticator; approve credentials only for that connection |
| Switch profiles | See only the selected profile's connections, results and history; the Google account identity remains unchanged |
| Correct a provider failure | Distinguish unsaved credentials from a saved connection with a failed test; retry the test without creating a duplicate |
| Manage a secret | Approve access to metadata, then separately approve replacing credentials or revoking access; never reveal the saved key |
| Process audio or video | Choose a sample file, understand limits, follow processing and read the resulting transcript; revisit it through history |
| Add a custom MCP | Distinguish submitting a package for review from uploading media or running an approved server |
| Return after expiry | Reauthenticate and return to the intended tool or result; do not repeat enrollment or credential import |
Review boundaries
All buttons must either change the prototype state, open an informative panel, or navigate to a real prototype page. Unimplemented production capabilities are labelled as proposals or unavailable. Provider credentials and authenticator codes are disabled placeholders. Sample actions make no network requests and use no browser persistence.
The baseline is the previous compact six-screen version approved in this conversation. Preserve its font sizes, account/profile separation and direct Open action while extending screen coverage. A walkthrough can establish that a route is navigable and find errors; it does not measure a population-wide usability improvement.
Implementation decisions for public launch still include Google account linking, loss-of-factor recovery and review of user-supplied runtimes. No mockup may silently decide or bypass those controls.