🔧 Day 33. Generic response

I think being only an Android developer is too narrow today. You need to have broader knowledge and skills to solve tasks outside single-platform development. AI tools push us in this direction, but at the same time, they help us gain this expertise. 

What I did:

Today, I worked on a search endpoint. I planned to complete it, but I only implemented the search logic for articles. I found that the article, user, and organization models were different from those I had used before. I decided to extract a separate model for it and simply add a mapper to the domain article model. Additionally, I set all fields to nullable to avoid the situation where a value doesn't pass through. It's a good strategy to protect yourself, especially when you're unsure of the response model.

Another problem is that I can't specify a generic type for the response model in Ktor. I received error indicating that generic aren't allowed. I think there should be a solution for this problem because it's a very common scenario. It's a good topic for investigation, and it would be interesting to find a solution for how to serialize objects based on the response.

What I will do:

• Update README file with description of project.
• Fix comment element
• Implementation of WebView to display stub content
• Theme configuration for Lottie animation
• Create public collection of API calls in Postman

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
Day 28. Opportunity for growth
Day 29. Hard work
Day 30. Old code
Day 31. Technical debt
Day 32. API calls

See you tomorrow.