Table of contents
Defining success metrics
This weeks sprint
My app on the Google play store
Current state of Modderz Android app
Modderz has successfully released version 1.0 of the ModView feature for Android. With the finalization of this feature it is time to iterate. This will come with considerate growing pains, such as but not limited to, Compose rewrites, design system implementation, adoption of Jenkins, code standardization, feature modularization, user acquisition/retention, more rigorous testing, server implementation, monetization and as always delivering on a weekly feature train.
The main and only metric we will be focusing on is Developer Productivity. Which can be defined as the number of GitHub issues completed in a weekly code sprint
Goals :
The sole emphasis on Developer productivity is to optimize one thing and one thing only. GETTING STUFF DONE QUICKER
Theme: Triage
This weeks code sprint is focused entirely on fixing the pain points in the code base. The main pain points can be characterized into two sections:
1) Compose pain points
2) Kotlin pain points
Compose pain points
Compose pain points consists entire of issues related to the Jetpack Compose UI layer. Examples being, the current lack of a internal design system and unnecessary recompositions
Kotlin pain points
Kotlin pain points consist of issues that plague the entire code base of the application. Of the two sections, this is the more general of the two. Examples being, lack of documentation, code standardization and flimsy tests
Goals :
Decrease unnecessary Jetpack Compose recompositions
Create coding standards across the entire code base
Increase developer productivity
Conclusion
Thank you for taking the time out of your day to read this blog post of mine. If you have any questions or concerns please comment below or reach out to me on Twitter.
