Getting started
Understand the LaunchTower workflow and move a finished app into a launch workspace.
- Create a launch
- Connect a repository
- Run readiness
LaunchTower Docs
From finished app to store-ready launch.
The operating manual for LaunchTower: connect your source, understand what is missing, produce store assets, choose the right native path, and control submission from one launch system.
Repository & source
How LaunchTower reads project structure, detects capabilities, and turns source code into launch intelligence.
- GitHub connection
- Repository selection
- Source scanning
Launch readiness
Device coverage, privacy, accessibility, commerce, store-review risk, and technical preflight.
- Readiness scan
- Privacy & permissions
- Accessibility
Native deployment
Choose between Base44-native capabilities, Despia, Capacitor, or fully native paths without locking the app to one engine.
- Capability matrix
- Despia runtime
- Native upgrade plan
Integrations
Connect MCP services and launch infrastructure while keeping credentials and audit history centralized.
- MCP Hub
- Connections
- Audit logs
Store submission
Prepare metadata, assets, reviewer access, release strategy, submission packages, and store status.
- Apple App Store
- Google Play
- Submission control
Security & privacy
How LaunchTower handles launch data, credentials, access, and sensitive integration details.
- Launch data security
- Authentication
- Secrets handling
Documentation is now part of the product surface.
The public docs hub is backed by repository documentation so implementation notes, user guidance, launch policy, and technical references can evolve together. The next step is article-level routing and search rather than relying on one giant help page.