# Build a Website, Mobile App and Desktop App Sharing One Database

Canonical: https://uvilno.com/features/ecosystem-wire
Updated: 2026-11-13

Ecosystem Wire connects projects you own to a shared managed backend and generated-app account realm. Build a website first, then create mobile or desktop companions from its context. Review existing-project connections before merging schemas. Source entitlements, payment settings and generation usage remain attached to each project.

Create a free Uvilno account, name your project and review this brief. Generation starts when you send it.

[Decide whether your app needs a companion](https://uvilno.com/guides/connected-apps-vs-standalone)

## Connect the workflow you already have

Open App connections or Link projects to see the current app, shared cloud and available platform slots. A companion request carries the existing project's context into its normal build workflow. Linking an existing app presents a review of collections, records, accounts and conflicts before committing the connection. A matching email address alone never merges private accounts.

## Follow an actual saved change

A committed write sends a private notification through the authenticated mesh bridge. Authorized clients refetch the records they can access. Reconnect refreshes their state, with bounded polling available during interruptions. The interactive illustration runs in your browser and uses example data. Follow the walkthrough to verify an actual shared record.

## Carry one drawing review from web to mobile.

Start with a website and one private review record. Use the same authorized visitor on both surfaces to check persistence and access before building a staff queue or distributing a native app.

1. **Build and save the web workflow** — Create the review website from the editable brief. Ask for a private projects collection with title and review_state fields. Sign in with a configured app account, create “Courtyard drawings” in In review, and refresh after the save is acknowledged. Check that the saved record still appears.
2. **Create the mobile companion from App connections** — Open App connections on the saved web project and start a mobile companion. Build a review list and detail view against the existing projects collection. When linking a separate existing project, use Review connection to inspect proposed collections, records and account conflicts before approving the link.
3. **Read and change the same record across apps** — Use the trusted app sign-in flow for the same visitor in both projects. Open Courtyard drawings on mobile and change the state to Changes requested. Refresh the website and confirm the original record shows that state. In App Data, confirm the update belongs to the existing row rather than a second copy.
4. **Check access with a second visitor** — Sign in with a different test account in a separate browser profile. The first visitor's review must be absent from the list and unavailable through its detail link. If a collaborator needs access, design and verify an explicit authorization policy before expanding this owner-scoped example.

### Reproduce the checks

**Observed in local database fixtures**

The local database fixture moved one existing record to the shared host after approval, returned it through the linked app's saved version, and kept the repeated connection request from creating a duplicate. Separate cases rejected a cross-owner connection and guest access to private data.

**Verify on your deployment**

Use the actual published origins to exercise both sign-in flows and the review update. Confirm the provider configuration and check reconnect behavior on the target devices.

Run with repository access:

```sh
pnpm --filter @wb/web exec vitest run src/server/ecosystem/mesh-db.test.ts
```

## Continue this workflow

- [Decide whether to build connected or standalone apps](https://uvilno.com/guides/connected-apps-vs-standalone)
- [Verify private data with two visitors](https://uvilno.com/features/database-and-auth#workflow)
- [Scope an operations dashboard](https://uvilno.com/use-cases/crm-and-internal-desktop-tools)
- [Publish the verified web version](https://uvilno.com/features#publishing)

## Platform plan

| Platform | Generated experience |
| --- | --- |
| web | A public project portal where a client reviews a drawing. |
| mobile | A touch-first companion that reads the same authorized project and approval state. |
| desktop | An operations workspace for reviewing the same record, with a wider work queue. |

## Declared collections

| Collection | Fields | Access |
| --- | --- | --- |
| projects | title (required string), review_state (string option) | Private to the signed-in visitor. Record ownership is assigned by the service. |
| reviews | project_id (reference to projects), decision (string option), comment (string) | Private to the same visitor. Add this collection if the workflow needs a review history. |

## Acceptance checks

- Update a review in one app and verify it after refetch in the companion.
- Sign in through each app and verify that a different user cannot read the record.
- Disconnect and reconnect the network, then confirm the latest committed state appears.
- Review a schema conflict before linking an existing project.

## Setup and launch boundaries

- Shared data does not share creator source entitlements, provider secrets or payment receipts.
- Connection reviews can expire. Existing record, schema and request quotas apply to the combined backend.
- A companion build consumes the normal generation allowance. Connecting apps does not promise a fixed synchronization latency.

## Editable starting brief

Plan a client drawing-review website with a project list, project details and an approval status. Start with a private projects collection containing a required title and a review_state field with In review, Changes requested and Approved options. Scope records to each signed-in visitor and leave the collection empty until that visitor creates a project. Use a configured sign-in method, acknowledge writes before showing success, and handle loading, empty results and errors. After I test the website, I will create a mobile companion from App connections and verify that the same authorized visitor can read the saved record across both apps. Keep separate source entitlements and payments. Do not use the preview role as an authorization grant.

## Common questions

### Does connecting apps merge every user's account automatically?

No. Accounts and private data retain their authorization boundaries. Shared accounts use the managed realm, and overlapping identities require the user's proof of control through the trusted account-link flow.

### Can I detach a companion later?

Supported detach workflows create an independent snapshot while preserving reference and ownership integrity. Sessions, payment receipts and provider secrets are not copied. Review the resulting service setup before publishing it.
