Projects

A project in Mosayic represents one app you’re building. Each project gets:

• Its own pair of GitHub repos (<project>-app and <project>-api)
• Its own local folder structure
• Its own bundle ID, version number, and build history
• Its own Google Cloud project for deployment

Most users have one project. If you’re shipping multiple apps from the same Mosayic account, just create one project per app.

Creating a project

You’re prompted to create a project the first time you sign in. After that, the + New project button is in the top bar.

The form is one field: a project name. This is purely a label inside Mosayic — it doesn’t have to match your app’s display name, your bundle ID, or your repo names. You can rename it later. Pick something short and memorable.

When you click Create project, you’re dropped straight into the Setup Guide for that project.

Switching projects

The project switcher is in the top-left of the dashboard, next to the Mosayic logo. It’s a dropdown with all your projects; click one to switch.

Switching is instantaneous — projects are independent state, so you can flip between them without affecting either one’s setup or build status.

Project Info

Every project has a Project Info screen at /projects/<id>/project. It’s where you see and edit:

Field	Editable?	Notes
Project name	Yes	Internal label; safe to change
Bundle ID	Locked once set	Changing this would break update channels and store listings — Mosayic enforces this with a database trigger
Local folder path	Yes	Where the code lives on this machine. Useful if you move the folder.
Mobile repo path	Yes	Relative to local folder. Default: mobile/
API repo path	Yes	Relative to local folder. Default: api/
GCloud project ID	Yes	The Google Cloud project where your API is deployed

Deleting a project

The Project Info screen has a Delete project button at the bottom. It pops up a confirmation modal before doing anything.

Deleting a project removes it from Mosayic’s database. It does not delete:

• Your local folder or files
• Your GitHub repos
• Your Google Cloud project or deployed services
• Your Supabase project
• Your Expo project

Those are yours and Mosayic doesn’t touch them. If you want a full cleanup after deleting from Mosayic, you’ll need to delete each of those manually.

Caution

Deletion in Mosayic is permanent — there’s no undo. We don’t soft-delete project records. If you need to keep the metadata, export anything you care about first (or just don’t delete it; idle projects don’t cost anything).

Multiple machines

You can work on the same project from multiple machines. The state that lives in Mosayic (project metadata, GitHub URLs, etc.) is the same everywhere. The state that lives on your machine (local folder, .env files, installed dependencies) needs to be set up per-machine.

To bring an existing project to a new machine:

1. Sign in to the dashboard on the new machine.
2. Install and sign in to the VS Code extension.
3. Clone your <project>-app and <project>-api repos manually into a folder.
4. Update the Local folder path on the Project Info screen to point at the new location.
5. Re-run Configure Supabase to create new local .env files.

The dashboard doesn’t currently re-scaffold from existing repos automatically — that’s on the roadmap.