Magic Deploy
Where do you want to deploy?
Pick your target. LingCode handles the build, signing, and upload — each guide shows the exact one-time setup you'll do on the platform's side.
App Store (iOS + macOS)
Archive, export, and upload to App Store Connect with an API key. Platform is auto-detected from your Xcode scheme. Auto-bump build number, preflight checks for Xcode + signing cert, clickable fix links when something's wrong.
Google Play (Android)
Build a signed AAB with ./gradlew bundleRelease and upload via the Play Developer API. Remote preflight verifies access before gradle runs, so auth failures surface in one second instead of two minutes.
Web platforms
One-click deploy to Vercel, Netlify, Railway, Fly.io, or Heroku. LingCode invokes each platform's CLI; you just install it and authenticate once. Token-paste shortcuts for every platform.
Your own server (scripts cookbook)
Custom rsync deploys to a VPS, droplet, or bare-metal box. Copy-paste starters for Next.js, Vite, Node, Python, Go, Ruby, PHP, Rails — plus post-deploy scripts for nginx, pm2, systemd, Docker, and more.
Not sure which to pick? For most web apps, start with Vercel or Netlify — zero infra, works in minutes. For mobile, the App Store guide covers both iOS and macOS. For full control over your server, use the scripts cookbook. You can also mix — LingCode lets you configure multiple deploy targets per project and run whichever you need.
Learn the concepts
Deploy fundamentals. You don't need to read any of these to ship — but they'll save you hours of debugging when something does break.
How App Store code signing works
The trust chain from Apple's root CA down to the signature on your .ipa. Why there are four layers, what each one proves, and how xcodebuild ties them together.
JWT auth in 5 minutes
What a JSON Web Token is physically, why deploy tools use it everywhere, and how Apple and Google use it differently.
Why versionCode breaks your second deploy
The #1 most-Googled deploy error. What build numbers actually do for the stores, and two strategies that make you stop tripping over them.
What a service account really is
Google's identity for machines. Why it's strictly better than an API key, and what minimum privilege looks like for a deploy service account.
Annotated file examples
Side-by-side views of the three files LingCode hands to Apple and Google — the .p8, the service-account JSON, and ExportOptions.plist — with every field explained.
Glossary
Every term from the deploy guides in plain English. AAB, .ipa, provisioning profile, service account, JWT, App Sandbox, versionCode, and 20+ more.
Deploy FAQ
The real questions devs actually ask — Apple Developer fees, TestFlight processing times, lost keystores, rollbacks, CI integration, what happens when a deploy fails mid-way, and more.
Before you deploy — build the app first
Setting up LingCode and your dev stack.
Getting Started
Install LingCode, connect Claude, open your first project, try a slash command. Fresh download to working AI session in ~10 minutes.
Development setup
Backend, database, frontend, env vars. Postgres / MySQL / Redis locally, migrations, .env patterns, common stacks end-to-end, and how LingCode's AI speeds up each step.