Is Uber's current use of RIBs closer to the compose demo? Or the tutorials?
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 7.9k
- Forks
- 914
- PR merge metrics
- No merged PRs in 30d
Description
Is Uber's current use of RIBs for android closer to the compose demo? Or the tutorials? If we are starting a new project, do you recommend doing something closer to the compose demo? Also there are no deep links in the compose tutorial so that would be nice to add.
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
Compare the compose demo with the tutorials, focusing on how each represents a new Android project and whether Uber’s current RIBs usage aligns with either approach. Determine the recommended approach, then identify the compose tutorial’s missing deep links and document or add them; done means the guidance is clear and the tutorial links work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- documentation, mobile
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100