Working with multiple apps

Patterns for managing several apps at once — organization, naming, sharing components.

Once you've built one or two apps, you may want more. Maybe one per client. Or different products. Here's how to stay organized.

Your app dashboard

Your OverSkill dashboard shows all your apps in one place:

• Sort by recently edited, alphabetical, or status
• Filter by team member, by integration used, or by published/draft status
• Search by name

Each card shows the app's name, custom domain, status, and last activity.

Naming conventions

A few patterns that work well when you have 10+ apps:

• By client: acme-corp-internal, acme-corp-public, betacorp-dashboard
• By function: crm-sales, crm-support, crm-analytics
• By environment: myapp, myapp-staging, myapp-experiments

Names appear in URLs, so keep them short and predictable.

Tagging apps

Tag apps for grouping:

Tag this app with client-work and production

Tags show up as filters in your dashboard.

Sharing components between apps

If you build the same login flow or settings page in multiple apps, you can save it as a reusable template:

Save the current login screen as a template called Standard Login

Then in another app:

Use the Standard Login template

The AI copies the structure. Each instance is still independent — changes in one don't affect the others.

Sharing data between apps

If you want two apps to share data (e.g. a customer-facing app and an internal admin app both reading from the same customer database):

Connect this app to the same customer database as my ClientCRM app.

Both apps now see and edit the same data.

Warning: shared data means changes in one app immediately show up in the other. Plan accordingly.

Cloning an app

Want to start a new app from an existing one as a template?

Clone MyApp as the starting point for a new app called MyApp v2

You get a fresh app with all the same pages, data structure, and styling — but it's separate. Edits won't affect the original.

Team collaboration on multiple apps

Each team member can have different access levels in different apps. By default, Editors can edit all apps; but you can lock down specific apps:

Make Acme Corp Production admin-only.

Editors lose edit access to that one app while keeping it on all the others.

What to read next

• Inviting team members
• Using OverSkill from AI agents