App Home
Home is the main screen for an app. It answers one question: what still stands between you and an app store submission?
Everything on this screen is built around a single idea - each page gets one primary action at a time, so there's never a decision about what to click next.
App header
The card at the top shows your app identity and live address:
| Element | What it does |
|---|---|
| App icon | Click it to pick or upload a new icon from your media library |
| App name | The display name of your app |
| Live URL | Your public microsite address, with a copy button next to it |
| View site | Opens your public microsite in a new tab |
Changing the icon requires permission to update the app.
Store-readiness
Two tiles summarise where you stand:
- Store-readiness - how many of the six compliance pages (Privacy Policy, Terms of Service, Data Deletion, EULA, Cookie Policy, Refund Policy) are published
- Needs review - how many compliance pages have generated content sitting in draft, waiting for you to review and publish
Below them, a progress bar shows the same score as a percentage. When every compliance page is live, the message changes to Store-ready - all compliance pages are live.
Note: Not every app needs all six pages. Privacy Policy and Terms of Service are required by both stores; the rest depend on what your app does. The score is a checklist, not a requirement.
Needs attention
If users have submitted deletion requests or support tickets that are still open, an amber strip appears with a count for each. Click a chip to jump straight to that queue. The strip disappears once everything is resolved.
The same counts appear as a badge on the Home item in the sidebar.
Compliance pages
The main checklist lists the six compliance page types in the order most apps need them. Each row shows the page type, why it matters, its current status, and one action.
Status
| Status | Meaning |
|---|---|
| Not created | The page doesn't exist yet |
| Draft | The page exists but has never been published |
| Published | Live on your public microsite |
| Unpublished | Previously published, currently taken offline |
Row actions
| Action | When it appears | What it does |
|---|---|---|
| Add page | The page doesn't exist | Opens the generation wizard for that page type - it creates the page for you |
| Generate | The page exists but has no content | Opens the wizard to draft the content |
| Review draft | Content exists but isn't published | Opens the content editor |
| Edit | The page is published | Opens the content editor to make changes |
There's no separate "create the page, then generate content" step any more. On the five wizard-backed types - Privacy Policy, Terms of Service, EULA, Cookie Policy, Refund Policy - Add page takes you straight into the questionnaire, and the page is created behind the scenes when you finish. See AI Wizards.
If a page type isn't included in your plan, Add page opens an upgrade prompt instead. See Plans & Limits.
Extra controls
Two icon buttons sit at the end of each row once a page exists:
- Eye - take a published page offline, or put an offline page back online. The public URL returns a 404 while the page is offline, and your draft content is untouched.
- External link - open the live page in a new tab.
Toggling visibility requires publish permission. See Roles & Permissions.
Site pages
The second list covers the non-legal pages of your microsite:
| Page | What it's for |
|---|---|
| Landing | Your public homepage - designed in the visual builder |
| Waitlist | Collect early-access signups |
| Support | Let users open support tickets |
These open in the visual builder rather than the content editor, because they're layout-driven rather than text-driven. The landing page row shows Open designer; the others show Edit.
Use Add page in the top-right of this list to create other page types.
Data Deletion pages
Data Deletion is the one compliance page with no questionnaire. Add page opens the standard page dialog, where you describe your deletion process, and VOTLI publishes a working deletion request form immediately from the app template - there's nothing to generate or review.
Because it's a form rather than a legal text, its row action is Edit, which opens the visual builder instead of the content editor. Submissions land in Settings → Deletion requests.
