Android Modernization Feasibility Matrix
Evaluate legacy Android app modernization paths into Jetpack Compose and Kotlin Multiplatform for client engagements.
Use this template when planning large-scale client refactoring engagements from legacy XML/Java to modern declarative architectures. It produces a comprehensive evaluation matrix comparing migration trade-offs, risks, and phased delivery milestones.
Role: Principal Android Systems Architect with 12+ years of enterprise mobile modernization experience.
Context
- Client Baseline Stack: {{client_legacy_stack}}
- Target Architectural Goals: {{target_architecture_goals}}
- Reported Performance Bottlenecks: {{performance_bottlenecks}}
- Regulatory & Compliance Standards: {{compliance_standards}}
- Engagement Delivery Timeline: {{consulting_timeline}}
- Client Engineering Skill Profile: {{team_skill_profile}}
Task
Synthesize the client's current codebase constraints and delivery requirements into an actionable Android Architectural Modernization Feasibility Matrix that scores candidate migration strategies against organizational feasibility and technical debt.
Method
- Analyze {{client_legacy_stack}} to identify foundational coupling, legacy threading models, and deprecated dependency chains.
- Cross-reference {{target_architecture_goals}} against Android Jetpack guidelines and Kotlin Multiplatform enterprise readiness.
- Map identified {{performance_bottlenecks}} across rendering passes, cold-start lifecycles, and memory churn.
- Define candidate modernization patterns: Strangler Fig incremental refactoring, clean-slate module replacement, and hybrid multiplatform integration.
- Score each pattern across engineering velocity, regression probability, testability, and alignment with {{team_skill_profile}}.
- Audit compliance constraints imposed by {{compliance_standards}} against third-party dependency migrations.
- Map migration steps onto {{consulting_timeline}} to highlight critical path dependencies and rollback trigger conditions.
Constraints
- MUST structure the primary deliverable as a multi-column comparative matrix using Markdown tables.
- MUST evaluate specific Android components (Room, Coroutines/Flow, Jetpack Compose, Koin/Hilt, WorkManager).
- MUST NOT recommend greenfield rewrites without explicit evidence of irrecoverable architectural debt.
- Analysis MUST remain strictly tailored to professional services client advisory standards.
Output format
- Executive Summary (150-200 words)
- Architectural Comparison Matrix (Markdown table with columns: Modernization Strategy, Velocity Score (1-5), Risk Index (Low/Med/High), Dependency Impact, Regression Surface, Skill Alignment)
- Phased Migration Sequencing Table (Phase, Key Milestones, Rollback Criteria)
- Final Recommended Strategy & Advisory Justification
Self-review
- Verify all 6 context variables are deeply integrated into the analysis.
- Ensure the matrix scoring accurately contrasts against {{team_skill_profile}} and {{consulting_timeline}}.
- Confirm every recommendation satisfies {{compliance_standards}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.