Mobile App Project Management | iOS & Android Guide
Manage mobile app projects across iOS and Android platforms. GitScrum tracks device testing, app store submissions, and coordinated releases.
8 min read
Mobile development brings unique challenges—app store reviews, multiple platforms, device fragmentation, and offline capabilities. GitScrum helps mobile teams coordinate iOS and Android development, track feature parity, and manage release cycles that sync with app store timelines. The key is planning for platform-specific work while maximizing shared effort.
Mobile vs Web Project Differences
| Aspect | Mobile | Web |
|---|---|---|
| Deployment | App store review | Instant |
| Updates | User must update | Automatic |
| Testing | Device matrix | Browser matrix |
| Offline | Critical consideration | Optional |
| Performance | Device constraints | Server scaling |
| Guidelines | Platform rules | More flexible |
Mobile Project Structure
PROJECT ORGANIZATION
OPTION 1: SINGLE PROJECT WITH PLATFORM LABELS
┌─────────────────────────────────────────────────┐
│ Project: MyApp Mobile │
│ │
│ Labels: │
│ ├── [platform:ios] │
│ ├── [platform:android] │
│ ├── [platform:both] │
│ ├── [type:feature] │
│ ├── [type:bug] │
│ └── [type:store-requirement] │
│ │
│ Epics: │
│ ├── User Authentication [both] │
│ ├── Push Notifications [both] │
│ ├── iOS Widget [ios] │
│ └── Android Widget [android] │
│ │
│ Best for: Small team, cross-platform framework │
└─────────────────────────────────────────────────┘
OPTION 2: SEPARATE PROJECTS
┌─────────────────────────────────────────────────┐
│ Project: MyApp iOS │
│ └── iOS-specific work only │
│ │
│ Project: MyApp Android │
│ └── Android-specific work only │
│ │
│ Project: MyApp Shared │
│ └── Backend, APIs, shared logic │
│ │
│ Best for: Separate native teams │
└─────────────────────────────────────────────────┘
Mobile Development Workflow
MOBILE APP DEVELOPMENT LIFECYCLE
1. FEATURE DEVELOPMENT
┌─────────────────────────────────────────────────┐
│ Feature: Dark Mode Support │
│ │
│ Sub-tasks: │
│ ☐ Design: Dark mode color palette │
│ ☐ iOS: Implement dark mode switching │
│ ☐ iOS: Test on devices (iPhone 12-15) │
│ ☐ Android: Implement dark mode switching │
│ ☐ Android: Test on devices (Pixel, Samsung) │
│ ☐ Both: Persistence of preference │
│ ☐ Both: QA sign-off │
└─────────────────────────────────────────────────┘
│
▼
2. INTERNAL TESTING
┌─────────────────────────────────────────────────┐
│ iOS: TestFlight internal testing │
│ ├── Build uploaded: v2.3.0 (build 456) │
│ ├── Internal testers: 15 users │
│ └── Duration: 3-5 days │
│ │
│ Android: Internal testing track │
│ ├── Build uploaded: v2.3.0 (456) │
│ ├── Internal testers: 15 users │
│ └── Duration: 3-5 days │
└─────────────────────────────────────────────────┘
│
▼
3. BETA TESTING
┌─────────────────────────────────────────────────┐
│ iOS: TestFlight external testing │
│ ├── Requires App Store review (24-48 hrs) │
│ ├── External testers: 100 users │
│ └── Duration: 1-2 weeks │
│ │
│ Android: Closed/Open testing track │
│ ├── Rolled out incrementally │
│ ├── External testers: 100 users │
│ └── Duration: 1-2 weeks │
└─────────────────────────────────────────────────┘
│
▼
4. STORE SUBMISSION
┌─────────────────────────────────────────────────┐
│ iOS App Store: │
│ ├── Review time: 1-7 days (usually 24-48 hrs) │
│ ├── May require fixes and resubmission │
│ └── Plan for rejection contingency │
│ │
│ Google Play Store: │
│ ├── Review time: Hours to 3 days │
│ ├── Staged rollout available │
│ └── Can halt rollout if issues found │
└─────────────────────────────────────────────────┘
Release Planning
MOBILE RELEASE CALENDAR
RELEASE: v2.3.0 - Dark Mode + Performance
Target Public Date: March 15
TIMELINE:
┌─────────────────────────────────────────────────────────────────┐
│ Feb 17 Feb 24 Mar 3 Mar 10 Mar 15 Mar 22 │
│ │ │ │ │ │ │ │
│ ├────────┼────────┼────────┼────────┼────────┤ │
│ │ │ │ │ │ │ │
│ ▼ ▼ ▼ ▼ ▼ ▼ │
│ ┌────┐ ┌────┐ ┌────┐ ┌────┐ ┌────┐ ┌────┐ │
│ │Code│ │Int │ │Beta│ │Store│ │Launch│ │Monitor│ │
│ │Done│ │Test│ │Test│ │Submit│ │ │ │ │ │
│ └────┘ └────┘ └────┘ └────┘ └────┘ └────┘ │
│ │
│ Code Freeze: Feb 17 │
│ Internal Test: Feb 17-24 │
│ Beta Test: Feb 24 - Mar 7 │
│ Store Submit: Mar 7 │
│ Buffer for Review: Mar 7-14 │
│ Public Launch: Mar 15 │
│ Post-Launch Monitor: Mar 15-22 │
└─────────────────────────────────────────────────────────────────┘
CHECKLIST BEFORE STORE SUBMISSION:
┌─────────────────────────────────────────────────┐
│ ☐ All features complete and tested │
│ ☐ Beta feedback addressed │
│ ☐ Crash rate < 0.1% │
│ ☐ Performance benchmarks met │
│ ☐ Screenshots updated for new features │
│ ☐ Release notes written │
│ ☐ Privacy policy updated if needed │
│ ☐ New permissions documented │
│ ☐ Accessibility tested │
└─────────────────────────────────────────────────┘
Device Testing Matrix
DEVICE TESTING STRATEGY
iOS DEVICE MATRIX:
┌─────────────────────────────────────────────────┐
│ Priority 1 (Must Test): │
│ ├── iPhone 15 Pro - iOS 17 (latest) │
│ ├── iPhone 13 - iOS 17 (popular) │
│ └── iPhone 11 - iOS 16 (oldest supported) │
│ │
│ Priority 2 (Should Test): │
│ ├── iPhone 15 - iOS 17 │
│ ├── iPhone 14 - iOS 16 │
│ ├── iPhone SE 3 - iOS 17 (small screen) │
│ └── iPad Pro - iOS 17 (if iPad supported) │
│ │
│ Priority 3 (Automated Only): │
│ └── Older devices via CI/CD │
└─────────────────────────────────────────────────┘
ANDROID DEVICE MATRIX:
┌─────────────────────────────────────────────────┐
│ Priority 1 (Must Test): │
│ ├── Pixel 8 - Android 14 (reference) │
│ ├── Samsung S23 - Android 14 (popular) │
│ └── Samsung A54 - Android 13 (mid-range) │
│ │
│ Priority 2 (Should Test): │
│ ├── Pixel 7 - Android 13 │
│ ├── OnePlus 11 - Android 14 │
│ └── Xiaomi 13 - Android 13 (market share) │
│ │
│ Priority 3 (Automated + Firebase Test Lab): │
│ └── Broader device coverage │
└─────────────────────────────────────────────────┘
TESTING LABELS:
┌─────────────────────────────────────────────────┐
│ [tested:pixel-8] │
│ [tested:iphone-15] │
│ [needs-testing:samsung] │
│ [device-specific-bug:iphone-se] │
└─────────────────────────────────────────────────┘
App Store Considerations
STORE COMPLIANCE TRACKING
APP STORE GUIDELINES CHECKLIST:
┌─────────────────────────────────────────────────┐
│ iOS (Apple Guidelines): │
│ ☐ No references to other platforms │
│ ☐ Sign in with Apple if social login exists │
│ ☐ In-app purchases for digital goods │
│ ☐ App Tracking Transparency implemented │
│ ☐ Privacy nutrition labels accurate │
│ ☐ No hidden features │
│ ☐ Minimum functionality standards met │
│ │
│ Android (Play Store Policies): │
│ ☐ Target API level requirements met │
│ ☐ Data safety section accurate │
│ ☐ Permission usage explained │
│ ☐ Billing library for in-app purchases │
│ ☐ Content ratings accurate │
└─────────────────────────────────────────────────┘
REJECTION CONTINGENCY:
┌─────────────────────────────────────────────────┐
│ If rejected: │
│ 1. Review rejection reason immediately │
│ 2. Assess fix complexity (hours vs days) │
│ 3. If simple: fix, retest, resubmit │
│ 4. If complex: communicate delay to stakeholders│
│ 5. Update timeline with new buffer │
│ 6. Consider expedited review if available │
│ │
│ Common rejection reasons to preempt: │
│ ├── Metadata/screenshot mismatch │
│ ├── Crashes during review │
│ ├── Missing login credentials │
│ └── Guideline violations │
└─────────────────────────────────────────────────┘
Best Practices
Anti-Patterns
✗ Submitting to stores without buffer time
✗ Testing only on latest devices
✗ Ignoring platform guidelines until rejection
✗ No staged rollout strategy
✗ Forcing updates without grace period
✗ Not tracking device-specific bugs