scribe-org / scribe-org/Scribe-Android
[Epic] Modularise Project into Two Separate Apps
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 99
- Forks
- 121
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 16
Description
Terms
- I have searched open and closed feature requests
- I agree to follow Scribe-Android's Code of Conduct
Description
After merging #537 the current codebase consist of both the conjugate application and the keyboard application. This issue would consist of multiple sub issues which would eventually refactor the current codebase to support two independent apps built on top of a shared core, improving scalability, maintainability, and feature isolation.
The issue would be considered completed when we would have the conjugate and keyboard application present as 2 separate app modules and the core shared logic is present in another module. This would help us in making changes within the project in a more uniform way.
Contribution
Happy to look into it and help others work on it as well :)
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 current combined app structure and the changes from #537; no file or test is named in the issue. Define the conjugate and keyboard app modules plus a shared core, and consider the work complete when those three parts build as independent components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, mobile
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100