🔧 Day 32. API calls

I found an interesting topic in this podcast episode. Nowadays, you can deliver a product even if you don't know how to write code. AI tools make this process much easier. As developers, we need to have broader skills if we want to stay on top.

What I did:

Once again, I noticed that some important APIs were not exposed in the official documentation. I tried to write logic to fetch data for the search screen. I discovered an interesting API call by inspection of a web page. Since I am currently using API calls from different sources, I decided to collect them in a Postman collection to share with other developers or create tests to check functionality. I think this functionality could be very useful if it's free. I should add this as a separate task for my challenge, as it involves infrastructure development.

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

See you tomorrow.