When I'm working with KMM, I very often stumble upon expect/actual implementations. At this point, you should go to platform-specific code, and implement it for both platforms. I'm not sure, but it looks like in Flutter you do that very rarely. Sometimes, a third-party package exists, or the standard library provides this functionality. In this case, development in Flutter happens more smoothly.
What I did:
I worked on the tag composable. I created a simple implementation and added logic to handle different state sand parameters. But I stabled over parsing hex color and transforming it to a Color object that the Tag composable consumes. I implemented only the Android part; for iOS, I added a TODO. Additionally, I slightly changed the package structure of files, extracted Tag composable into a separate file, and created a preview for it in the Android module.
What I will do:
I have an idea of how to add basic functionality without implementation. If you need to open a screen that isn't implemented yet, you can simply redirect to a Web View to display a web version of the screen. Late, you can replace this screen with native implementation. I think this is a good way to release the application faster. So, I am going to investigate this approach.
- Add Detekt(a static code analysis tool) to the project.
- Added day/night theme support.
- Update README file with description of project.
- Create a GitHub project to manage the tasks for future collaboration.
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.
You can buy coffee me here :+)
See you tomorrow.
Top comments (0)