Skip to content
John CEOJohn CEOJohn CEO Docs

Apps

John can build a simple public site or tool and host it on a *.johnceo.app address. You still talk to him on Slack or Telegram; the Apps page is where you open the link, review versions, download source, or take a site down.

Apps vs Connections

Section titled “Apps vs Connections”

John CEO uses “app” in more than one way. They solve different jobs.

Apps (sites on johnceo.app)

Section titled “Apps (sites on johnceo.app)”

Sites and tools John builds and hosts for you. He publishes a public link under johnceo.app. This guide is about those Apps.

Connections / app library

Section titled “Connections / app library”

Through Connections, you connect tools you already use (mail, calendar, CRM, and more). John then works inside those accounts. That is the app library, not a site on johnceo.app.

Setup for Connections: Connections.

Skills (playbooks) are separate again: they teach John how to work in a domain. A default playbook helps him build Apps; the playbook is not the hosted site itself.

How it works

Section titled “How it works”

Ask John to build

Section titled “Ask John to build”

There is no “New app” button that creates a blank site. On Slack or Telegram, ask John to build a landing page, tool, or site and put it online. He builds it in your private workspace, publishes it, and shares the public link.

Your public address

Section titled “Your public address”

Each App gets a system-assigned address on johnceo.app (for example a short phrase plus a unique code). You do not pick a custom domain or a vanity subdomain in v1.

Public by design

Section titled “Public by design”

The live site is public. Anyone with the link can open it. Treat it like anything else you would put on the open web. Your private workspace and private chats stay separate from that public surface.

Static sites only

Section titled “Static sites only”

Apps are static: HTML, CSS, and JavaScript (including simple client-side tools). They are not full server apps with databases, logins, or custom backends in v1.

Versions and source

Section titled “Versions and source”

John can publish updates over time. One version is live at a time. On the Apps page you can review versions and activate an earlier ready version when you need to roll back.

The source belongs to you. Download it from the Apps page when you want a copy.

Get one and manage it in the John CEO app

Section titled “Get one and manage it in the John CEO app”

Apps may not be available in every environment yet. If you do not see Apps in the product, the feature is still rolling out for your account. After it is enabled, you may need Update John so your private workspace can build and publish.

When it is available:

  1. On Slack or Telegram, ask John to build a landing page, tool, or site and put it online.
  2. Wait for John to share the public *.johnceo.app link when it is ready.
  3. Open Apps in the john.ceo app to see status and URL for each site.
  4. From there you can open the live site, review versions, activate a prior version, download source, or delete the App (it stops being public).
  5. Ask John again when you want changes; he republishes a new version.

Use cases

Section titled “Use cases”

Concrete ways people use Apps:

  • Landing or marketing page - “Build a one-page site for this offer and put it online.”
  • Campaign or partner microsite - Share a clean public URL without standing up your own hosting.
  • Small client-side tools - Calculators, checklists, or simple interactive pages that run in the browser.
  • Shareable demos - Prototype a page, iterate with John in chat, keep the link handy for stakeholders.

Good first asks are concrete: audience, tone, what to include, and that you want it public on johnceo.app.

Good habits and limits

Section titled “Good habits and limits”
  • Treat everything on the site as public. Do not put secrets, private files, or credentials on an App.
  • Static only for now: no custom domain, no per-App login or database, no rename of the assigned hostname.
  • There is a practical cap on how many Apps you can keep (about 10), how large a published site can be (about 50 MB), and how often you can republish. If John hits a limit, he will say so.
  • Apps are a preview-style capability: availability can vary by environment, and these docs do not promise uptime or a fixed feature set forever.
  • To report abuse of a public App, email [email protected] and put [Apps abuse] in the subject.
Section titled “Related”