wordpress-mobile / wordpress-mobile/WordPress-Android
Bottom Navigation: Phase 3 (TBD)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Following the completion of #7667, we need to look into adding persistent bottom navigation to the app (ie: bottom nav remains visible throughout the app).
This will require "fragment-izing" all the activities so they can be displayed in a single host activity, which is a huge task. Because of this, it has not been decided yet whether we shall tackle this phase.
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 completed work in #7667 and the app's current activities. Determine the scope of fragment-izing those activities into a single host activity and keeping bottom navigation persistent throughout the app. The issue is not ready for implementation until this phase is approved and its scope is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100