Manage projects, test results and choose how to share them

The project library shows the current account’s conversational development projects and real page thumbnails. Search projects, review recent items, add favorites, open a project or delete it; rename the project from the editor header.

Cloud projects load when you sign in with the same account on another device. After a large generation, allow synchronization to finish before closing the page. Deleting a project also deletes its business data, so preserve anything you still need first.

• Confirm that every page and navigation destination can be reached.
• Review desktop, tablet and phone widths.
• Use the primary buttons, forms and links.
• Remove internal sources or sensitive information from public pages.

Ordinary page projects use Publish or Share, with links such as /project/…. The first publication can be public or limited to internal access. Publish again after an update to move the latest version to the link. Legacy page publication does not automatically become an App Release with private-data access.

A Free account that has never held paid access receives one three-day public trial with Nemeow branding and a bottom-right countdown. Those public page links pause when the trial ends or paid access expires without a queued entitlement, while workspace projects remain available. The same links return automatically when paid access becomes active again; republishing or creating another project does not reset the Free trial. These page-link rules do not establish an App Release's access policy.

A controlled App shows Private App Release in the editor. After Build and preview approval, inspect the candidate frontend, backend operations, Schema and permission changes, then choose Publish Private App Release. This control is owner-only: it creates no public page and does not deploy the Nemeow website.

Publication saves an immutable Release and switches the active version and its approved permissions together. Unpublished draft changes do not directly replace it. History offers Roll back to this release only for compatible, available candidates. Rollback does not revive revoked access or restore business records to an earlier point in time.

An App with an existing public runtime policy and active public Release uses /public/apps/…. Anonymous access is limited to explicitly allowed public reads; anonymous writes are disabled by default and require separate approval. Signed-in App users remain constrained to their permitted records; knowing another record ID does not grant access.

App sessions are isolated from platform accounts and other Apps. A platform owner session does not automatically become an App user. The Private App Release panel currently provides owner-only publication, not a public App switch; actual public App availability depends on runtime configuration and the page.