Terms
Description
After merging #586 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 framework*, 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 a framework. This would help us in making changes within the project in a more uniform way.
The use of framework for this purpose would have to be discussed as this is one of the approach I found quite interesting. Further research would have to be done of how other apps approach this.
Contribution
Happy to look into it and help others as well.
Terms
Description
After merging #586 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 framework*, 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 a framework. This would help us in making changes within the project in a more uniform way.
The use of framework for this purpose would have to be discussed as this is one of the approach I found quite interesting. Further research would have to be done of how other apps approach this.
Contribution
Happy to look into it and help others as well.