The manuall way of publishing apps to app store and play store ?

Overview

Manual app publishing (without CI/CD) involves building a signed release binary locally and submitting it through each platform's developer portal.

Android — Manual Publish to Google Play Store

Step 1: Build Signed App Bundle

bashCopy
# Build release AAB
flutter build appbundle --release
# Output: build/app/outputs/bundle/release/app-release.aab

Step 2: Upload via Play Console

1. Go to play.google.com/console
2. Select your app
3. Release → Production (or Internal/Alpha/Beta for staged rollout)
4. Click "Create new release"
5. Upload
   textCopy

   app-release.aab

6. Fill in Release notes (what's new)
7. Review → Save → Start rollout to Production

iOS — Manual Publish to App Store

Step 1: Archive in Xcode

bashCopy
# Open Xcode workspace
open ios/Runner.xcworkspace

In Xcode:

1. Product menu → Archive
2. Wait for archive to complete
3. Xcode Organizer opens automatically

Step 2: Upload to App Store Connect

In Xcode Organizer:

1. Select your archive
2. Click "Distribute App"
3. Choose "App Store Connect"
4. Click "Upload"
5. Wait for upload to complete (~5–10 min)

Step 3: Submit for Review in App Store Connect

1. Go to appstoreconnect.apple.com
2. My Apps → Select your app
3. Click "+" to create a new version
4. Fill in What's New, screenshots, description
5. Select the Build uploaded from Xcode
6. Click "Submit for Review"

Staged Rollout (Android)

textCopy
Instead of releasing to all users at once:
- Start with 10% rollout
- Monitor crash rate and ANR rate in Play Console
- Expand to 50% → 100% if metrics are good

Pre-release Tracks (Android)

TestFlight (iOS Pre-release Testing)

textCopy
Upload build to App Store Connect
  → TestFlight section
  → Internal Testing (up to 100 testers, no review needed)
  → External Testing (up to 10,000, basic review needed)
  → Gather feedback before App Store submission

Tip: For teams without CI/CD, establish a clear release checklist — bump version, run tests, build signed release, test the release build, then submit. Automate with CI/CD when the manual process becomes a bottleneck.