# One Responsive App or Two Connected Apps? A Practical Decision Guide

Canonical: https://uvilno.com/guides/connected-apps-vs-standalone
Updated: 2026-11-13

Decide whether a browser layout, a connected phone companion or an independent API fits your workflow. Define shared records, ownership and release checks first.

Written by the Uvilno team. Published: 2026-11-13

## Pick the smallest release boundary that fits the job

Use one responsive app when people do the same work on a large and a small screen. Add a connected companion when the second device has a distinct job and both jobs use the same authoritative records. Use separate apps with an explicit integration when permissions, organizations or release schedules need their own boundaries. Start with the work each person does and the records they need to finish it.

Consider an equipment inspection log. A browser view helps a visitor compare their previous inspections. A phone view helps that same visitor record a condition while standing beside the equipment. If both tasks work on the same URL, a second app adds another sign-in and release surface to test. A companion becomes a candidate when an installed experience, device interaction or separate distribution materially improves the field task.

Three ways to ship the inspection workflow

| Architecture | Choose it when | Prove before shipping |
| --- | --- | --- |
| One responsive app | One audience uses the same workflow on both screens | The same URL supports the phone task and the full review task |
| Connected companion | Different device jobs need the same account and records | A phone write appears in the browser under the same visitor identity |
| Independent apps with an API | A second organization or product has its own authority | The integration grants only the record fields and actions it needs |

## Write down what sharing means before generating either screen

A record can be shared through one backend, copied through an integration, or simply cached on a device. With one backend, both surfaces use the same record identifier and permission checks. With a copy, name which side owns the original, which fields move and how retries or conflicting edits behave. A device cache can make a screen load faster. A successful save still needs confirmation from the service that owns the record.

For the inspection example, start with one private inspections collection. Give each entry an ID, an equipment label, a condition, a note and a timestamp. The phone creates the entry, the browser reads and filters it, and both surface the same saved version. Decide which surface can update or delete an entry before adding buttons. Add a distinct permission case if a manager or an organization must see another visitor’s records.

- Name the person who owns each row and the service that decides access.
- List the allowed readers and writers for each surface.
- Describe how a successful write, denied write and stale view appear.
- Name the deployment and data environment for each surface.

## Test the handoff as a real visitor

Open the web view and phone view with the same disposable visitor identity. Create an inspection on the phone and wait for the save to be acknowledged. Refresh the browser view and open the exact inspection. Compare the record ID, condition, note and timestamp. Sign out and back in, then repeat the read. The test should use the deployment URLs or packages that will be distributed and the data environment they will share.

Sign in as a second visitor and attempt to open the first visitor’s private inspection from each surface. Test an invalid submission as well and confirm the browser list remains unchanged. If the companion can operate offline or both surfaces can edit the same entry, include reconnects and simultaneous edits in the release checks. Keep a short record of each outcome so you can rerun it after a schema or sign-in change.

- [Run the two-account database and login matrix](https://uvilno.com/guides/test-ai-app-database-and-auth#run-the-matrix)

## Check how your builder connects existing projects

In Uvilno, Ecosystem Wire links eligible owned projects through a primary project and a reviewed connection. Use that workflow to inspect collection definitions and existing records, then resolve account conflicts explicitly, including when emails match. The resulting projects keep separate source unlocks and publishing workflows. Open both previews with the intended visitor to verify the shared record, and recheck both published surfaces before distribution.

In a local database fixture, one incoming record kept its ID when it moved to the primary project. Submitting the same reviewed connection twice still left one record visible through the linked version. A request using the old topology revision was rejected. This exercises the record transfer and replay behavior in the database. Check login and the cross-device handoff against your own project and published origins.

Emergent documents a different starting point for its feature-flagged web-to-mobile conversion. For eligible web projects, conversion creates a new job with an Expo/React Native surface and a shared backend. Its current documentation excludes Next.js projects and calls for rechecking data, sign-in, assets and settings after the fork. If you already have two projects, verify how the tool handles existing records and identities before selecting a connection or conversion workflow.

Rerun the local Ecosystem Wire fixture from the repository

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

- [Uvilno Ecosystem Wire workflow](https://uvilno.com/features/ecosystem-wire#workflow)
- [Emergent web-to-mobile conversion documentation](https://help.emergent.sh/web-mobile-conversion-canonical)

## Decide how the two surfaces will change after launch

Write a short release note with the owner of the data contract, the first surface that will use a change, and the check that proves the other surface still works. Prefer adding an optional field over immediately making every installed companion send a new required field. Deploy a reader that tolerates both record shapes before asking the older surface to write the new shape. If a companion update can take longer to reach users, keep both versions in the acceptance test until the older version is retired.

A native package adds device, signing and store-release work to the shared-record checks. Choose the actual form of distribution separately from the decision to share a backend. Start with one complete handoff you can observe. Expand to more shared collections after the first one passes both its successful save and its denied access checks.

- [See a repair-shop portal built as one browser app](https://uvilno.com/guides/repair-shop-portal-example)
- [Uvilno export and hosting options](https://uvilno.com/guides/how-to-export-and-host-your-ai-website)

## Common questions

### Do web and mobile need the same framework to share records?

They need a compatible data contract and authorization boundary. Each surface can use the interface and runtime that fits its device while calling the same backend.

### Does a shared backend sign a visitor into both apps automatically?

A shared account can support access from both apps, while each origin or installed app still has its own session flow. Test sign-in, session restoration and logout on each surface with the real provider configuration.

### When should I keep the apps independent?

Keep distinct authorization boundaries when the apps belong to different organizations, expose different rights or need to evolve independently. Define a scoped integration around the minimum records and operations the second app actually uses.

## Prepare your own brief

Plan an equipment inspection workflow. A visitor reviews their own inspection history in a browser and records a condition and short note on a phone. Start by deciding whether a responsive app satisfies both jobs. If a phone companion is justified, name the shared inspections collection, its private owner, which surface can change each field, and how an acknowledged write becomes visible in the other surface. Include the same visitor on both surfaces, a denied read by a second visitor, a failed save, and a refreshed view as acceptance checks. Exclude team sharing, offline edits and push notifications from this release.
