What Can the Workspace Do?

The workspace is where HappySeeds turns conversation into a working project. It brings AI chat, preview, assets, code, analytics, cloud services, app settings, auth, and payment setup into one place.

How it works

The left side is where you talk to AI. The right side is where you inspect the project.

When you ask for a change, AI updates the project. You then use the workspace tools to check the result, inspect generated files, review code, configure services, and prepare the app for publishing.

A good rhythm is:

Describe one change in chat.
Review the result in Preview.
Use PC, tablet, or mobile viewports to check the layout.
Open Assets or Code only when you need to inspect files or implementation details.
Configure App, Cloud, Auth, or Payment when the project is ready for those settings.
Publish the project and test the live URL.

Key capabilities

Preview: Review the current app visually while you iterate. Use PC, tablet, and mobile viewports to check responsive behavior.
Prompt-based editing: Ask for changes in natural language, then refine the result in small passes.
Assets: Inspect uploaded or generated files, images, and other project resources.
Code: Review the generated implementation when you need to understand what changed or diagnose a technical issue.
Analytics: Check traffic and usage signals after the project has been deployed and analytics are available.
Cloud: Manage backend services such as database, custom domains, secrets, and logs.
App settings: Update the project icon, title, SEO metadata, and preview image before sharing.
Auth: Set up sign-in providers such as Google or Brevo when your app needs user accounts.
Payment: Connect checkout, subscriptions, webhooks, or customer portals when your app needs paid flows.

What to use first

Start with Preview and chat for visual or copy changes. Open other tools only when the task needs them:

use Preview to review screens, routes, and responsive behavior
use Assets when the problem involves files, images, or uploaded resources
use Code when you need implementation details
use Analytics after deployment to check visits and page activity
use Cloud when the app needs data, domains, secrets, or logs
use App before publishing or sharing
use Auth and Payment when the project depends on external accounts or credentials

What each feature is for

Preview is for checking what users will see. Use it before asking AI for another visual change, and before publishing.

Assets is for project files. Use it when an image is missing, a file needs to be uploaded, or you want to confirm which resources exist in the project.

Code is for technical inspection. Use it when you need to understand generated files, investigate why a feature behaves a certain way, or share details with a developer.

Analytics is for live usage data. It is most useful after a project is published and real users have visited the site.

Cloud is for production services. Use it when the app needs a database, custom domain, environment variables, auth provider, payment provider, or logs.

Limits and user control

The workspace can help build and connect many parts of an app, but it does not replace your control over external services.

You still control:

third-party accounts
API keys and secrets
domain DNS records
payment provider settings
what gets published publicly

AI can guide setup and wire the app, but you should review sensitive settings before launch.

Preview URLs are temporary and expire after 30 minutes. If you need to share something stable, publish the project and send the published URL.

Analytics also depends on a published project and real traffic. A new or unpublished project may show no data.

Which tab should I open when the preview looks wrong?
Why does the public page look different from Preview?
Do I need Cloud for every project?
Where should I put API keys?
Should I test Auth and Payment from Preview or the published URL?