Hola App
Hola is the first-run welcome surface for Próx OS at /app-os/hola. It lives in
Hola is the first-run welcome surface for Próx OS at /app-os/hola. It lives in
packages/apps/system-apps/src/apps/growth/hola/ and is exported through
@prox-os/os-apps/hola.
Early Access Email Capture
Hola includes an Early Access email capture card before the What works today
section. The card posts directly to Web3Forms from the browser so the project can
validate real interest before a first-party waitlist API exists.
The form sends:
- Email address.
- Form metadata such as source, product, page path, page URL, referrer, user agent, timezone, language, and submission timestamp.
- Static subject and sender labels for the Web3Forms notification.
The card handles empty email, basic email validation, missing access key, loading, success, and failure states in the UI. It does not store email addresses in localStorage.
Configuration
Use this environment variable in the OS Shell app:
PUBLIC_WEB3FORMS_ACCESS_KEY=For local development, copy apps/os-shell/.env.example to
apps/os-shell/.env.local and set the real value there. Do not commit
.env.local or put a real Web3Forms access key in tracked source.
For production builds that run inside Cloudflare Pages, configure
PUBLIC_WEB3FORMS_ACCESS_KEY in the hosting provider, for example Cloudflare
Pages environment variables, then rebuild and redeploy the OS Shell.
For local direct uploads with pnpm deploy:os, the OS Shell is built on the
local machine before wrangler pages deploy dist uploads static assets. In that
flow, Cloudflare Dashboard variables do not rewrite an already-built JavaScript
bundle. Put the value in apps/os-shell/.env.local or export it in the local
shell before running pnpm deploy:os.
Current Boundary
This is intentionally a static form integration. Hola should not introduce a new backend, database table, auth flow, or CRM dependency just to capture early interest. When the real conversion funnel needs ownership, migration can move the submission path to a Próx OS API, Worker, D1 or Neon-backed waitlist, and a provider-approved analytics pipeline.
Startup Pairing
Signed-in demo sessions open Timeline with Hola after the shell boot flow. Timeline opens first and Hola opens in front, leaving part of Timeline visible behind the welcome window. This uses the existing local demo session state and does not add a full auth system.