Saved records. Real sign-in. Clear ownership.

Plan managed app records, email and configured Google, Discord or GitHub sign-in with project-scoped authorization and a shared ecosystem account realm.

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

Name the records and their permissions

A useful collection definition includes actual fields, relationships and who can read or update each record. A personal task app should keep tasks private to their owner. A public catalog and a private order history need different scopes. The App Data manager helps the creator inspect managed collections, while the application SDK exposes only the account's authorized operations.

Request the provider and verify its readiness

Ask for Google login explicitly when that is part of the experience. Provider availability, callback registration and email delivery are configuration requirements. A prompt cannot supply missing credentials. Confirm a real session after sign-in, test refresh and logout, and verify a different project or user cannot access the private data. The creator's Uvilno session and app visitor identity are separate.

Verify a private task tracker with two visitors.

Use a sign-in screen, a task list and a task detail view. The task tracker gives you a concrete way to check a database save, a fresh read and an access refusal before adding more screens.

  1. Define the smallest usable app

    Prepare the editable brief. Use one private tasks collection with a required title and status options Todo, In progress and Done. Start with an empty collection. The managed service associates a record with its authenticated visitor, so the form does not submit an owner field.

  2. Sign in and confirm a saved row

    Resolve setup for the visitor login method you requested. Sign in as the first test visitor and create “Review proposal” with status Todo. Wait for the save to succeed, change the status to Done, then reload the app. Confirm the same task appears as Done in the list and its detail view. The creator can check the saved row in App Data.

  3. Try the same record from a separate session

    Keep the first session open and use another browser profile for the second test visitor. Confirm the second visitor has an empty task list. Open the first visitor's task detail URL and confirm the record is unavailable. Create an unrelated task as the second visitor and confirm that it stays out of the first visitor's list.

  4. Repeat on the published version

    After the saved version passes verification and its services are ready, enable its live URL in Publish Studio. Repeat sign-in, the acknowledged write and the second-visitor check on that origin. If the provider reports missing setup or a write fails, keep the input available and surface the error before inviting users.

Give each screen its own job.

These are proposed interfaces for your brief. Build and verify the core workflow before adding connected companions.

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.

CollectionSuggested fieldsAccess to decide
taskstitle (required string), status (string option)Self-only reads and writes for each signed-in app user.
profilesdisplay_name (string), notifications_enabled (boolean)Optional private profile settings. Ownership is assigned by the service.

Verify the outcome, then expand.

Make the starting point your own.

Name your project and review the brief. Building starts when you send it.

Start at $0. Source unlock $4.99 once per project.Compare $10 Plus, $20 Pro and $60 Ultra monthly plans

Questions before you build.

Does saying Add Google login configure the provider automatically?

The request can select the capability and generated interface. Real sign-in still depends on provider readiness, credentials and a registered callback. Review the reported setup state and test a real login.

Will exporting my app also export the managed identity service?

Frontend source unlock includes the authored application. Hosted database and identity services remain dependencies unless you separately migrate them or configure the documented deployment adapter.

Read the public Markdown reference