Any problem that you struggle with is an opportunity for growth. If you write code as fluent as you speak, it means you have reached a stable level of knowledge. Only by solving problems do we improve.
What I did:
I decided to start preparing to fetch data for the article screen. After a short investigation, I found that I need at least two API calls to get data: loading the article by ID and loading the comments for this article. The comments are received in a threaded structure. In other words, any comment can include child comments. I created a simple use case for fetching the article and comments in parallel. One problem that I haven't covered yet is error handling for networking. This question constantly bothers me, so it's a good opportunity for growth and a worthwhile problem to solve.
What I will do:
- Add Detekt(a static code analysis tool) to the project.
- Update README file with description of project.
- Create a GitHub project to manage the tasks for future collaboration.
- Fix comment element
- Implementation of WebView to display stub content
- Theme configuration for Lottie animation
If you want to join the project, just leave a comment here, or write a message in LinkedIn.
What help I'm looking for:
Designer (create design of application in Figma)
Android/KMM developer
Any other help related to the project.
My timeline:
Day 1. Deep breath and dive.
Day 2. Networking layer.
Day 3. Loading of articles.
Day 4. ArticleItem.
Day 5. Localization.
Day 6. Work on Sunday.
Day 7. First week.
Day 8. Enjoying coding.
Day 9. Expect/actual.
Day 10. TODOs.
Day 11. Friday evening.
Day 12. Frustration.
Day 13. Blocker
Day 14. Monday
Day 15. Reactions
Day 16. Feed
Day 17. stringWithFormat
Day 18. Comment
Day 19. 1 percent
Day 20. A bit of progress
Day 21. Pagination
Day 22. Lottie animation
Day 23. Sorting of articles
Day 24. Step by step
Day 25. Broken endpoint?
Day 26. After party
Day 27. Burnout
See you tomorrow.
Top comments (0)