4 min read • Guide 509 of 877
How to Use GitScrum for Mobile App Development Projects?
How to use GitScrum for mobile app development projects?
GitScrum supports mobile development with columns for app-specific phases: development, testing, beta, and app store submission. Configure platform labels (iOS, Android), track release versions, and document in NoteVault. Mobile teams using structured PM release 25% more frequently with fewer bugs [Source: Mobile DevOps Report 2024].
Mobile development setup:
- Create project - App name
- Configure columns - Mobile workflow
- Add platform labels - iOS, Android, Both
- Version labels - v1.0, v1.1, etc.
- Configure beta column - TestFlight/Play
- Document in NoteVault - Release process
Mobile development columns
| Column | WIP Limit | Purpose |
|---|---|---|
| Backlog | 15 | All features/bugs |
| Sprint | 10 | Current sprint |
| Development | Team size | Active coding |
| Code Review | 3 | PR review |
| QA | 5 | Device testing |
| Beta | 3 | TestFlight/Play Console |
| Store Review | 2 | Apple/Google review |
| Released | None | In production |
Mobile-specific labels
| Category | Labels |
|---|---|
| Platform | ios, android, both, cross-platform |
| Version | v1.0, v1.1, v2.0 |
| Type | feature, bugfix, hotfix, crash |
| Priority | critical, high, medium, low |
| Store | app-store, play-store |
Cross-platform workflow
| Framework | Approach |
|---|---|
| React Native | Shared codebase, platform labels |
| Flutter | Single board, platform-specific testing |
| Native (iOS + Android) | Separate columns or projects |
| Hybrid | Platform labels for native modules |
Mobile testing workflow
| Stage | Testing Type |
|---|---|
| Development | Unit tests |
| Code Review | Code quality |
| QA | Manual device testing |
| Beta | Real user testing |
| Store Review | Apple/Google automated |
| Production | Crash monitoring |
Beta release tracking
| Platform | Beta Tool | Column |
|---|---|---|
| iOS | TestFlight | Beta (iOS) |
| Android | Play Console Internal | Beta (Android) |
| Both | Combined | Beta |
Store submission workflow
| Step | GitScrum Action |
|---|---|
| Ready for submission | Move to Store Review |
| Submitted | Add "submitted" label |
| In review | Add "in-review" label |
| Approved | Move to Released |
| Rejected | Move to Development, add "rejected" |
Mobile documentation in NoteVault
| Document | Content |
|---|---|
| Release Process | Step-by-step store submission |
| Version History | Changelog |
| Device Testing | Test device matrix |
| Store Guidelines | Apple/Google requirements |
| Certificates | Provisioning, signing info |
Mobile-specific challenges
| Challenge | GitScrum Solution |
|---|---|
| Store rejection | Blocked column, rejection label |
| Multi-platform sync | Platform labels, filters |
| Version tracking | Version labels |
| Device testing | QA column, device labels |
| Release coordination | Release label, NoteVault |
Release management
| Release Type | Workflow |
|---|---|
| Major release | Full workflow, extended beta |
| Minor update | Shorter QA, normal beta |
| Hotfix | Fast-track, critical label |
| Patch | Normal flow, patch label |