Landing Pages for Generated Apps

Applies to: App Generation projects that use the SaaS Engine template

The current App Generation flow does not create a separate landing website by default.

Request a landing page as part of the generated application. The AI Engineer can implement it in the same source code and environment.

Request the landing page during creation

Include these details in your initial requirements:

  • the intended audience.
  • the main problem and value statement.
  • the required sections.
  • the primary action.
  • the sign-in and registration links.
  • brand colors, tone, and visual references.
  • required public data.
  • page title and search description.

State whether the root URL must show the landing page. Also state where authenticated users must go after sign-in.

The initial SaaS Engine delivery can include a public landing page when your requirements call for one.

Add a landing page after creation

  1. Open Edit via Chat.
  2. Describe the landing-page audience and goal.
  3. List the required sections and actions.
  4. Provide brand references or images.
  5. State which application data can be public.
  6. Ask the AI Engineer to implement the page.
  7. Test the public and authenticated paths.
  8. Save a version after approval.

Use a separate request for large content changes. This keeps design work and application behavior easier to review.

Protect application access

A public landing page does not require public application data. Keep private API routes and records behind authentication.

If the page needs live data, identify the exact public fields. Review the related API access before publication.

Keep a clear sign-in link. Test sign-in, sign-out, registration, and return paths after the page changes.

Review the result

Test these items before release:

  • the main action works.
  • the page works on mobile and desktop screens.
  • public visitors cannot access private records.
  • page titles and descriptions match the content.
  • images load from public locations.
  • authentication links remain available.
  • keyboard focus and text contrast are usable.

The landing page uses the generated application's deployment. It is not a separate AppWizzy project or automatic static-site product.

Read Generated App Editor for the current editing workflow.