Compose Design System
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.1k
- Forks
- 124
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 51
Description
With Compose for iOS, we may want to create a unified set of components that may be shared between all compose clients. That would include:
- Android
- Desktop
- iOS
The idea would be:
- Create a compose-only module.
- The module will be used by all clients.
- Extract modules from Android (most mature UI we have) and make it available as multiplatform components).
Wear OS and Auto will not be included.
Alternatively, we can include those components to the shared module but that would include them available to all platforms and may be wasted for platforms that won't use it.
Contributor guide
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.
Research direction
Start by reviewing the existing Android UI modules and the current Android, Desktop, and iOS client structure. Determine how a Compose-only module could be shared by those clients while excluding Wear OS and Auto; done means the component-sharing scope and module placement are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- desktop, frontend, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100