What I did:
I worked on the comments feed today. I think it is one of the most important parts of the application. We want not only to read the article but also to interact with each other. Before starting, I thought a little about the structure of the view component. Comments have a nested structure, logic for hiding selected threads, and the ability to write and react to comments. The last is optional now because authentication hasn't been implemented yet. I added the base UI implementation for comments. It works fine now but requires additional tuning.
Additionally, I will modify the models to display all the information the screen requires.
Today, I started a sub-challenge - a month-long learning task. I use several LLMs during the development process on a daily basis. I want to learn more about the capabilities of GitHub Copilot as they apply to me as a mobile developer. I plan to spend November, during my account's free trial period, investigating the usefulness of this tool. I started today and will finish on December 2.
During this month, I plan to find answers to the following questions:
How useful is Copilot?
For which tasks is it most applicable?
What are the best practices for using Copilot?
What are its advantages and disadvantages?
Am I ready to pay $10 per month for this tool?
I will report my progress and weekly and write posts about my experience with Copilot.
Let's start.
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
Day 33. Generic response
Day 34. Response
Day 35. Coderabbit
Day 36. What is the power of Pull Request?
Day 37. Search challenge
Day 38. Search items
Day 39. A party
Day 40. Fixing UI
Day 41. Surpassed record
Day 42. Monday
Day 43. Composition
Day 44. Timestamp
Day 45. Time manipulation
Day 46. Broken pipelines
Days 47-48. Broken API
Day 49. Organization card
Day 50. GitHub Universe
Day 51. Article Screen
Day 52. Collapsing Toolbar
Day 53. Plan
Day 54. Voyager issue
You can find more useful content on my LinkedIn page, on X, in Medium or Mastodon.
See you tomorrow.
Top comments (0)