Day 68-70. Theme switcher

day-68-70.-theme-switcher

What I did:

It is my Monday report about my challenge and the progress I made over the weekend. I didn’t report on the weekend because I didn’t make any progress. I tried again to implement bookmarking logic, but I failed as had previously. I couldn’t bookmark an article, either through the official API or a web API call using a token. Almost every time, I encountered an error related to an authentication issue. So, I will skip this step for now.

I thought about a library for theme switching for the KMM project, but I only started working on it today. I’ve created a separate repository for it, and I placed a simple class inside. I want to implement this logic not only for mobile platforms but also for other platforms, such as desktop and web. I used the KMM library wizard to generate a base template for that. I committed this project with my simple class and tried to retrieve the dependencies through Jitpack. When I tried to retrieve the dependencies, I encountered several errors during  the artifact build process. I think I should correctly configure the Maven Publish plugin first. I will try to do this tomorrow, and only after successfully completing this step will I continue transferring the logic to the library. 

I’m not sure if I will complete the project before the end of my challenge, but this subtask is very interesting and allows me to build something useful for the community. 

What I will do:

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
Day 55. Copilot
Day 56. Collapsing logic
Day 57. Replies
Day 58. Comments screen
Day 59. Comments
Day 60. Markdown
Days 61-65. Dark theme
Day 66. Theme switcher
Day 67. Follow as in the System

You can find more useful content on my LinkedIn page, on X, in Medium or Mastodon.

See you tomorrow.

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post
a-eye-web-chat-assistant:-voice-and-vision-web-ai-chrome-extension-for-inclusive-browsing

A-Eye Web Chat Assistant: Voice and Vision Web AI Chrome Extension for Inclusive Browsing

Next Post
how-to-crush-audience-engagement-in-2025

How to Crush Audience Engagement in 2025

Related Posts