Back to Eliza

Eliza App Remaining Launch Work

packages/homepage/docs/eliza-app-remaining-launch-work.md

2.0.16.9 KB
Original Source

Eliza App Remaining Launch Work

This is the actionable remainder of the Eliza App plan after the homepage, release-data fallback, installer-script, and CI-gate work in this branch.

Status terms:

  • Repo-ready: code or docs exist in this repo and local verification passes.
  • Repo TODO: implementation can be completed in this repo without external accounts, hardware, or production credentials.
  • External blocker: launch depends on hardware, app-store review, production credentials, phone numbers, release signing, or deployed cloud services.

Product And Brand

RequirementStatusRemaining work
Eliza App homepage tagline: "Your Eliza, everywhere."Repo-readyKeep the first viewport focused on app download and one personal agent.
Shared product switcher: ElizaOS, App, Cloud, Docs, GitHubRepo-readyUpdate URLs if final domains differ.
One taxonomy: ElizaOS, Eliza App, Eliza CloudRepo-readyKeep docs and public copy aligned when Cloud/OS branches land.
One account identity across app, cloud, and OSRepo TODOEnforce account/session linking in Cloud and OS onboarding routes; fix identity projection reads/writes before messaging launch.
One agent per userRepo TODOAdd a durable one-agent uniqueness gate at provisioning and make duplicate webhook/onboarding calls idempotent.

Downloads And Stores

RequirementStatusRemaining work
macOS .dmg direct downloadExternal blockerPublish signed/notarized Apple Silicon and Intel DMGs to the GitHub release.
Windows .exe direct downloadExternal blockerPublish signed ElizaOSApp-Setup*.exe to the GitHub release.
Linux .deb direct downloadExternal blockerPublish release .deb to the GitHub release.
Linux .rpm, AppImage, .tar.gzRepo TODO / external blockerEnsure release jobs actually produce and attach the promised formats. The launch gate now requires all claimed desktop formats.
No dead fallback installer URLsRepo-readyFallback cards open the GitHub releases page instead of guessed filenames.
Public deploy blocks without release assetsRepo-readybun run check:release-data fails until required artifacts exist.
App Store, Play Store, Mac App Store, Microsoft StoreExternal blockerCreate store listings, finish review, then replace disabled cards with real URLs and review status.
TestFlight first iOS pathExternal blockerConfigure Apple credentials, upload a beta build, and publish TestFlight status.
Android APK bridgeRepo-ready / external blockerbun run --cwd packages/app install:android:adb -- --build handles local ADB installs. Android release CI now produces and attaches a signed QA APK beside the Play AAB when release signing credentials are available.

iOS Developer Install

RequirementStatusRemaining work
Honest sideload copyRepo-readyHomepage warns that App Store/TestFlight is the normal path.
Developer sideload helperRepo-readybun run --cwd packages/app install:ios:sideload checks Xcode/device prerequisites and opens the workspace; pass -- --build-device or -- --build-sim to build first.
Sideload smoke verificationExternal blockerCI runs the developer-install preflight, but real install validation still requires a real iPhone or configured simulator with signing credentials.
Public iOS installer without Apple reviewNot supportedDo not ship this. Use TestFlight/App Store for normal users.

Messaging Onboarding

RequirementStatusRemaining work
Homepage entrypoints for iMessage, Discord, Telegram, WhatsAppRepo-readyCards link into /get-started?method=....
Shared stateless onboarding workerRepo TODOFinish structural handoff checks and route all unlinked messaging identities through the same worker.
Cerebras gpt-oss-120b onboarding modelExternal blockerConfigure production Cerebras credentials and verify worker routing.
Discord bot invite/onboardingRepo TODO / external blockerbun run --cwd packages/cloud-shared preflight:messaging-gateways exposes missing credentials; still need production OAuth/gateway deployment.
Telegram bot onboardingRepo TODO / external blockerGateway preflight checks BotFather token and webhook secret; still need signed identity-link completion.
WhatsApp onboardingExternal blockerGateway preflight checks Meta env; still need official WhatsApp Business Platform account, templates, and opt-in compliance.
iMessage blue-text gatewayExternal blockerGateway preflight checks relay/headscale env; still need user-owned Mac, spare iPhone, BlueBubbles, Headscale node, relay credentials, and health checks.
Transcript handoff into real agentRepo TODOPersist source platform, setup session, target agent, and copied transcript state.

Cloud Console And One-Agent Admin

RequirementStatusRemaining work
"My Agent" tab in CloudOwned by Cloud streamVerify in cloud-ui branch; homepage points to /dashboard/my-agents.
Remove consumer generation studio/character chat from cloud consoleOwned by Cloud streamVerify route removals and sidebar state in Cloud PR.
API keys, docs, billing, settings, paymentOwned by Cloud streamVerify developer dashboard routes after Cloud stream merges.
App connects to provisioned Cloud agentRepo TODO / external blockerEnd-to-end provision, auth link, and bridge URL smoke in deployed Cloud.

Release And CI

RequirementStatusRemaining work
Homepage typecheck/build/e2eRepo-readyCI now runs homepage e2e in homepage quality gates.
Release-data contractRepo-readycheck:release-data blocks deploy when metadata/artifacts are missing.
Release orchestrator waits for desktop artifactsRepo-readyrelease-orchestrator.yml can call the desktop release workflow before homepage deploy when publish_desktop is enabled.
ChecksumsRepo-ready / external blockerAndroid release jobs now attach checksums for AAB/APK outputs. Desktop release assets still need consistently published checksums before check:release-data can require them globally.
Actual GitHub release assetsExternal blockerCut a release tag and run signed desktop/mobile jobs.
Store rollout metadata in homepageRepo-ready / external blockerGenerated release data now carries store target status/review fields. Add real URLs only after store review approves them.

Verification Before Public Launch

Run these locally and in CI:

bash
bun run --cwd packages/homepage typecheck
bun run --cwd packages/homepage build
bun run --cwd packages/homepage test:e2e
bun run --cwd packages/homepage check:release-data

Expected current state: the first three pass; check:release-data fails until real release assets exist. That failure is the correct public-launch blocker.