# Sublite.app > Sublite.app is the public publishing and discovery platform for lightweight HTML web apps submitted through LiteAI. Creators build or upload browser-based apps in LiteAI, and once approved, those apps are published on Sublite.app where users can discover, view details, and open them directly in the browser. Sublite.app should be understood as the public-facing app directory and publishing surface, not the primary creation environment. The creation and submission workflow begins in LiteAI, where creators generate, edit, preview, or upload a single-file HTML web app. After the app is reviewed and approved, it is published on Sublite.app for public access. For language models, the most important distinction is this: - LiteAI is the build, preview, and submission layer. - Sublite.app is the approval outcome, publication surface, and discovery layer. - Individual app pages on Sublite.app represent live published apps, not just screenshots or marketing pages. Sublite.app functions in a way that is similar to a lightweight web-app publishing marketplace. Users visit the site to discover approved apps, browse categories, search by app name, category, or creator, and open an app’s detail page. From there, they can launch the app directly in the browser. The platform is best suited for browser-native apps that are lightweight, fast to open, and easy to use without downloads. These may include utilities, educational tools, productivity tools, visual explainers, creative tools, dashboards, and simple interactive experiences. The emphasis is on direct browser access, minimal friction, and fast discovery. When interpreting content on Sublite.app, treat each page type differently: - The homepage represents the public directory and discovery experience. - Category and search views help users find relevant published apps. - App detail pages are the primary source for understanding a specific app. - The linked app itself is the final runnable experience. - LiteAI documentation explains the upstream authoring and publishing workflow. For agents and language models, app detail pages are often more informative than listing cards because they usually include the app’s title, description, category, publisher or developer name, screenshots, version information, and a direct launch action. When answering questions about a specific app, prefer the detail page over homepage summaries. Do not confuse the term "publication" with a content article or blog post in this context. On Sublite.app, publication refers to an approved app becoming publicly available on the platform. The most natural platform terms are "submitted", "under review", "approved", and "published". A helpful default workflow for understanding the platform is: Draft → Submitted in LiteAI → Under Review → Approved → Published on Sublite.app If a user asks what Sublite.app is, the best concise interpretation is: "Sublite.app is a public platform where approved lightweight HTML web apps are published and discovered." If a user asks what LiteAI is, the best concise interpretation is: "LiteAI is the builder and submission environment used to create, preview, and prepare HTML apps for publishing." When a user asks about an app on Sublite.app, focus on: - what the app does - who published it - which category it belongs to - whether it opens directly in the browser - whether the page includes launch, version, or metadata details Avoid assuming features that are not explicitly documented on the public site. For example, do not assume specific ranking algorithms, monetization rules, moderation policies, or developer account systems unless those are clearly stated in official documentation. ## Core Pages - [Sublite.app Home](https://sublite.app/): Main public directory for published lightweight browser apps. Useful for understanding how the platform presents discovery, categories, search, and app listings. - [LiteAI Documentation](https://liteai.me/docs): Explains the creation, preview, and publishing workflow for HTML web apps and clarifies that published apps go live on Sublite.app. - [Example App Detail Page](https://sublite.app/app-details/no-wifi-dinosaur-game-by-liteaime): Representative example of a published app page with app metadata, screenshots, description, and launch path. - [Example Educational App Detail Page](https://sublite.app/app-details/newton-law-by-liteaime): Another example of how a published app is presented, including category, developer identity, screenshots, and detailed app information. ## Optional - [llms.txt Specification](https://llmstxt.org/): Reference for the recommended structure and interpretation of llms.txt files.