One input. Paste a repo URL, drop a folder, or run @floom/cli deploy.
Floom auto-reads your code, auto-picks a slug, auto-publishes. The share link + a live preview appear on the same page.
Icon, description, visibility, BYOK, and pricing move to app settings (post-deploy).
One input, three paths. Paste a GitHub URL, drop a folder, or @floom/cli deploy. All three produce the same auto-deploy.
Auto-deploy on paste. No Deploy button, no Next button, no Configure step. The moment we recognise a valid source, we start. Input stays editable until deploy actually begins — one second of optimistic debounce.
Slug is auto-picked from the repo name. Collision → we append -2 silently. User can rename from Settings after.
Input schema auto-inferred. Priority order: (1) floom.yaml, (2) openapi.yaml, (3) exported function signatures (JS/TS/Python via AST), (4) single text input fallback. Bad inference → user fixes it on the live app page, not before.
Everything deferred. Icon, description, visibility (public by default), BYOK, pricing, auto-deploy-on-push, custom renderer → all in app Settings after deploy. Defaults are sensible so the first link works standalone.
Share link + live demo appear on the same page. No redirect. The app runs inline from the deploy page so the first click after "live" is the actual run, not navigation.
Click budget. Target: paste → live = 0 visible clicks (we hit Enter or auto-trigger). Folder drop = 1 click. Worst case (private repo, first-time GitHub connect) = 2 clicks.