Build for the phone in your hand.
Describe a touch-first mobile app, review it in Uvilno's isolated phone simulator and export supported PWA or hybrid app source after unlock.
Review the prepared brief in Studio. A build starts when you send it.
Start with a mobile journey
A useful mobile brief names the first screen, primary action and the next visible state. Specify a single-screen flow when tabs add no value. For multi-screen work, define what each tab owns, how Back works and where a form's validation appears. Ask for generous touch controls, readable type and empty, loading and error states that fit a small display.
Inspect the hardware and the application separately
Studio's phone simulator frames an isolated application viewport with status, camera and home hardware outside the app content. Check portrait, landscape and relevant tablet sizes. Companion projects can connect to a website's records through Ecosystem Wire. Exported native shells still need platform-specific configuration, device testing and a verified system-browser authorization return for managed OAuth.
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.
iOS & Android
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
An optional customer website or management portal connected to the same records.
Mobile
Touch-first views with purposeful tabs, forms, safe-area review and responsive composition.
Desktop
An optional wider administration workspace for the same service.
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 |
|---|---|---|
habits | title, owner, schedule, archived | Self-only habit access for a personal productivity app. |
checkins | owner, habit_id, completed_at | Each signed-in person reads and updates only their own history. |
Verify the outcome, then expand.
- Use the primary action with touch and keyboard and verify the resulting state.
- Check fixed controls against simulated safe areas in portrait and landscape.
- Reload a saved record and verify that another user cannot retrieve it.
- Test sign-in on the actual deployment and native shell before distribution.
From this brief to your first version.
Review the proposed workflow
Start with this editable feature brief. Confirm the primary action, target platform, actual business information and declared collection permissions before approving a plan.
Build and check the result
Review the isolated preview and execute the checks listed on this page. Begin with An optional customer website or management portal connected to the same records. Resolve missing service setup and save verified progress before expanding the scope.
Connect or export when ready
Use App connections to review owned companions and shared backend changes. Unlock source when ready to export, then verify the target deployment, packaging and hosted-service configuration.
Make the starting point your own.
Questions before you build.
Does Uvilno generate native React Native widgets?
The supported workflow generates the web application and offers supported hybrid shells, including Expo-related packaging. Treat native widgets and native-only APIs as additional platform work.
Can the mobile app share data with my website?
Yes. Owned companion projects can use the managed ecosystem backend and account realm after the connection and schema requirements are satisfied.