Q42 / Q42/Template.ComposeMultiplatform
Create and document strategies to implement the Design system with this CMP template
Open
@AnneKlapwijk is already working on this.
Since Mar 12, 2026.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 7d 15h
- Merged PRs (30d)
- 15
Description
The objective is to kickstart a new project with a clear strategy and optionally a default implementation for a Design System.
Starting point for this research
The two main options are using Material Design and Compose Unstyled
Why choose one over the other?
- Material Design if: You are building an MVP, a tool where utility beats brand-specific "vibe," or if your primary audience is Android-centric. It is the path of least resistance.
- Compose-Unstyled if: You are building a professional, brand-heavy product for both iOS and Android. It avoids the "cheap Android port" feeling on iOS and gives you a foundation that behaves correctly (accessibility-wise) without forcing a specific aesthetic.
Design System Comparison: Material Design vs. Compose-Unstyled
| Feature | Material Design (M3) | Compose-Unstyled |
|---|---|---|
| Design Control | Limited / Opinionated | Absolute / Unopinionated |
| iOS / Desktop Feel | Often feels like a "port" | Can be tailored to feel native |
| Accessibility | High (Google Standards) | High (Logic-driven blocks) |
| Dev Velocity | 🚀 Very Fast | 🛠️ Moderate (Setup required) |
| Bundle Impact | Heavier (Includes assets/styles) | Lightweight (Logic only) |
| Best For | Internal tools, MVPs, Android-first | Consumer apps, Strict Brand Guidelines |
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.