移动应用
android-compose-migration
更新于 2026-07-19
Android Compose · 迁移规则
Migration rules for Android Compose: expand/contract phases, idempotent steps and rehearsed rollback.
- 技术栈
- Android Compose
- 主题
- 迁移
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Split every breaking change into expand, migrate and contract phases
- ✓ Make the migration idempotent so a re-run is a no-op
- ✓ Rehearse on a production-shaped copy and record the rollback path
✕ 常见反模式
- ✕ Irreversible destructive steps in the same release as code removal
- ✕ Big-bang cutovers with no parallel running period
- ✕ Migrations that depend on manual console steps
◎ 交付前验证
- ◎ Verified on both target platforms, not just the emulator
- ◎ Cold-start time and frame budget re-measured on a mid-range device
- ◎ Accessibility labels present on interactive elements
同分类条目
26 篇移动应用
Flutter 工程规则
Flutter rules: adapter-separated platform code and rebuild-scope discipline
移动应用
React Native 工程规则
React Native rules: native module boundaries and release-mode measurement
移动应用
Android Compose 工程规则
Jetpack Compose rules: stateless composables and stable remember keys
移动应用
SwiftUI 工程规则
SwiftUI rules: single source of truth state and MainActor UI updates
移动应用
HarmonyOS ArkTS 工程规则
ArkTS rules: declarative state decorators and ability lifecycle handling
移动应用
WeChat Mini Program 工程规则
Mini Program rules: setData payload discipline and package-size budget