Three interfaces. One set of records.
Link Uvilno web, mobile and desktop companion projects to the same managed records and app account realm, with reviewed schema changes and scoped access.
Create a free Uvilno account, name your project and review this brief. Generation starts when you send it.
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.
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.
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.
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.
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.
Cross-platform architecture
One prompt. Web, Mobile, and Desktop in sync.
Build each interface for its own screen and link companion projects to the same records and accounts.
Web App
Forma project desk.
Approve the drawing review, then switch views to see the change carry over.
Practice index
Project desk
- In review
PRJ-014Wren HouseResidential · Drawing review - In progress
PRJ-008Field LibraryCivic · Material selection - In progress
PRJ-003Atelier AnnexWorkplace · Concept design
Uvilno.db · shared recordsUvilno.auth · shared accountsSample records update in this browser.Give each screen its own job.
These are proposed interfaces for your brief. Build and verify the core workflow before adding connected companions.
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.
Plan the records and their owners.
Suggested collections for this editable blueprint. Opening this page creates no database records. The plan must declare supported field types, relationships and access rules before building.
| Collection | Suggested fields | Access to decide |
|---|---|---|
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. |
Verify the outcome, then expand.
- 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.
Make the starting point your own.
Questions before you build.
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.