From Code to Users
Building a great app is only half the battle. Getting it into users' hands reliably and repeatedly is where deployment skills matter.
Android Deployment
Signing & Keystores Generate your upload keystore once and guard it with your life. Lose it, and you can never update your app.
Play Store Console The review process typically takes 1-3 days for new apps. Common rejection reasons: missing privacy policy, unclear permissions usage, and content policy violations.
App Bundle vs APK Always use App Bundles (.aab) — they're smaller, optimized per device, and required by Google since 2021.
iOS Deployment
Certificates & Provisioning Apple's signing process is more complex. You need a Developer Certificate, App ID, and Provisioning Profile. Xcode handles most of this, but understanding the concepts prevents debugging nightmares.
App Store Connect Apple's review is stricter and takes 1-7 days. They check for crashes, broken links, placeholder content, and guideline compliance.
TestFlight Use TestFlight for beta testing before submission. It's invaluable for catching device-specific issues.
Flutter Web Deployment
For web apps, I recommend Vercel or Firebase Hosting: - Build with flutter build web --release - Deploy the build/web directory - Configure proper caching headers for .js and .wasm files
CI/CD with GitHub Actions
Automate your builds and deployments. A basic pipeline: lint → test → build → deploy. Tools like Codemagic and Fastlane simplify the process significantly.
Lessons Learned
- Always test on real devices before submission
- Keep release notes professional and descriptive
- Monitor crash reports immediately after each release
- Have a rollback plan for critical bugs