Follow-Up Stack Packs
The decision ladder should stay compact. Put stack-specific commands, starters, packaging, and traps into capability packs.
Priority Order
| Priority | Pack | Why |
|---|---|---|
| 1 | learn/stacks/android-kotlin-compose/ | Strongest near-term app opportunity and SMS finance research already points native Android |
| 2 | learn/stacks/distribution/ | Signing, stores, installers, and update channels are the hidden hard part |
| 3 | learn/stacks/local-first-data/ | Local SQLite/files/export/sync boundaries recur across app ideas |
| 4 | learn/stacks/tauri-2/ | Good default for small local-first desktop tools |
| 5 | learn/stacks/windows-app-sdk-winui/ | Needed for modern Windows-native apps and Microsoft Store work |
| 6 | learn/stacks/pwa/ | Many civic, education, SME, and workflow ideas should start web-first |
| 7 | learn/stacks/react-native-expo/ | Best when Android+iOS launch is required with React/TypeScript velocity |
| 8 | learn/stacks/flutter/ | Useful for custom branded cross-platform UI |
| 9 | learn/stacks/cli-tools/ | Useful for lab automation and developer products |
| 10 | learn/stacks/ai-native-apps/ | Turns existing AI research into operational app guidance |
| 11 | learn/stacks/backend-api/ | Add only around concrete app needs |
Pack Rule
Each pack should start from Stack Capability Pack Template and include docs index, decision guide, starter, commands, quality gates, pitfalls, reference apps, and agent guardrails.
Do Not Build Yet
- Apple-native pack until an Apple-first idea appears.
- Games/3D pack until a real game/app idea appears.
- Enterprise stack pack until there is an enterprise buyer or integration requirement.