iOS App Build

iOS builds require a Mac or a cloud Mac service, an Apple Developer account and careful certificate management. Start earlier than you think; App Store review is the longest dependency.

Before you build

• A Mac with a current Xcode, or a cloud macOS build service.
• An Apple Developer Program membership in your legal entity.
• Unique bundle IDs for customer, vendor and rider apps.
• An App Store Connect record and a privacy policy URL.
• An APNs key or certificate for push notifications.
• The production API URL and HTTPS.

Configure and sign

1. Set the bundle ID, display name, version and build number.
2. Set the API URL and production keys for maps, payments and push.
3. Add the Firebase GoogleService-Info.plist.
4. Enable the capabilities the app uses: push, associated domains, background modes if required.
5. Use automatic signing with your team, or create certificates and provisioning profiles manually.
6. Archive and upload to TestFlight.

TestFlight

Test on a real iPhone, not only the simulator. Check login, menu, cart, payment redirect, order tracking, push and the vendor/rider flows. Test a clean install and an upgrade over the previous build. Add internal testers first, then a small external group.

App Store review

• Provide a demo account with an active test environment and clear instructions.
• Explain any physical-goods payment flow; digital goods rules are different.
• Complete the privacy nutrition labels and tracking permission if applicable.
• Do not use placeholder content, broken links or a “demo only” screen.
• Respond to review notes with a screen recording if the flow is not obvious.

Updates

Apple requires a new build for code changes; server-side configuration changes do not need a release. Keep the certificates, APNs key and App Store Connect access in the company's ownership, not the developer's personal account. A missing key can block push or updates after a handover.