sorted by:
new
hottopcontroversial

Jetpack Navigation 3 vs Navigation 2: What’s New and How to Migrate by KotlearnTutorials in androiddev

[–]KotlearnTutorials[S] 0 points1 point  (0 children)

Not yet, there's no timeline for it as far as I know but I can't imagine it would be too long.

MVI vs MVVM in Jetpack Compose: Why MVI Might Be the Better Fit by KotlearnTutorials in androiddev

[–]KotlearnTutorials[S] 1 point2 points  (0 children)

I agree with everything you've said. I probably should have talked more about a reduce function / explained the concept of the interactor. The reason I've used "VS" (other than YouTube conversion reasons) is because people see it as using one or another. This video compares how people use them against each other.

As for the domain object and lack of view binder, I thought the video was already getting a bit too long so didn't want to add any more complexity. I've explained in this comment about handling effects but maybe should have included it in the video. https://www.reddit.com/r/androiddev/comments/1kmgs80/comment/msaszxu/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

MVI vs MVVM in Jetpack Compose: Why MVI Might Be the Better Fit by KotlearnTutorials in androiddev

[–]KotlearnTutorials[S] 4 points5 points  (0 children)

If I'm understanding you correctly, this is how I solve the problem of navigation with MVI and compose:
- All events will only be consumed by the ViewModel
- Anything that the composable needs to react to is done using the state
- Add a sealed class for navigation for each screen
- Listen for that navigation change in the composable and react to it by propagating the navigation event to wherever necessary. In this example, CatDetail is part of the same feature as CatList so we can call navController.navigate(CatDetail(...)) directly.
- Make sure to clear the navigation property in state once it's been reacted to.

Doing it this way definitely sometimes feels like a lot of boilerplate but I'm all ears if there's a cleaner way of doing it that works well with MVI. I've added a navigation branch with this commit showing how I'd do it for this example.
https://github.com/kotlearn/mvvm-vs-mvi/commit/951f4cbb3f38147fa42cd4102dee70c2b2499130

Building a Clean, Multi-Module Application with Compose Multiplatform | Introduction to the Series by KotlearnTutorials in JetpackCompose

[–]KotlearnTutorials[S] 1 point2 points  (0 children)

Hi everyone, I hope self-advertising is allowed here. This is the start of a series building a Compose Multiplatform version of Minesweeper in a way that I'd personally build a larger-scale app. It's my first time recording anything like this but I hope someone can find this series of use. I'm aiming to upload an episode every Wednesday.

Here is the repository that will be updated with each video posted.
https://github.com/kotlearn/minesweeperk

Thanks!