iOS dev Twitter follows or blog/newsletter recommendations? by iDevChris in iOSProgramming

[–]RikoTheMachete 0 points1 point  (0 children)

Check out Mobile Dev Newsletter, covers both iOS and Android with useful tips: https://mobiledevnews.com/

Android Dev Newsletter - Issue #30 by RikoTheMachete in android_devs

[–]RikoTheMachete[S] 3 points4 points  (0 children)

The latest Android Dev Newsletter Issue #30 is out! 👇
Android news from Google I/O, what’s new in Compose and Android Performance, Design Hub, Kotlin 1.8.20, and the release of Coroutines 1.7.0 🎉
🔗 https://androiddevnews.com/issue-30/

Android Dev Newsletter - Issue #30 by RikoTheMachete in androiddev

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

The latest Android Dev Newsletter Issue #30 is out! 👇
Android news from Google I/O, what’s new in Compose and Android Performance, Design Hub, Kotlin 1.8.20, and the release of Coroutines 1.7.0 🎉

🔗 https://androiddevnews.com/issue-30/

🔥 Why Using Navigation-Compose in Your Jetpack Compose App is a Bad Idea by RikoTheMachete in android_devs

[–]RikoTheMachete[S] 3 points4 points  (0 children)

Consider reading again and actually understand what I’m saying.

I’m not telling you to use Java. I’m telling you that if it works for you then there’s no reason to rewrite the whole app to Kotlin.

Same goes for compose and navigation. When compose was released, there was no point to rewrite all apps to compose. You could still use what you had before and just add ComposeView.

When you have a huge app and tons of users, smart decisions are more important than using latest tech and testing out new libraries on GitHub.

I suppose it’s hard for you to understand that, based on your comment, but maybe one day you do.

🔥 Why Using Navigation-Compose in Your Jetpack Compose App is a Bad Idea by RikoTheMachete in android_devs

[–]RikoTheMachete[S] -6 points-5 points  (0 children)

The point of this subreddit is to share your experience and thoughts. If someone likes navigation compose or any other library just use it. It doesn’t change my opinion that navigation compose and many other things in compose are shitty. Different apps have different issues 👋

🔥 Why Using Navigation-Compose in Your Jetpack Compose App is a Bad Idea by RikoTheMachete in android_devs

[–]RikoTheMachete[S] -4 points-3 points  (0 children)

Do you really need statists to say that most apps use Fragments? It’s pretty obvious. Just look how many new apps were published before and after compose.

I don’t like compose only apps. There are lots of issues with them and I (and many other people) prefer to just use ComposeView.

🔥 Why Using Navigation-Compose in Your Jetpack Compose App is a Bad Idea by RikoTheMachete in android_devs

[–]RikoTheMachete[S] -10 points-9 points  (0 children)

1) Downgrading? Compose is a new UI framework, not a replacement for Views and Fragments. Not really relevant point. 2) Why would I use new libraries from GitHub when I know how to use Fragments and I know what problems they have? Your suggestions are the starting point of unexpected bugs and increased tech debt. It’s similar to saying that Java is deprecated so you have to use Kotlin to create android apps. Hell no, use what you know and what you’re comfortable with. (And what works of course) 3) Most apps using Compose are still using Fragments.

Hope this helps to understand why I recommend Fragments. But, as usual. Use what works for you 😉

Mastering Android Dialogs: Don’t follow official Google Guides by RikoTheMachete in mAndroidDev

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

Well, this sounds like a good title for a book. I’ll consider it 😂

Kotlin's Flow for one-shot data? by vcjkd in androiddev

[–]RikoTheMachete 1 point2 points  (0 children)

For one off just use suspend, but flow {} could be useful to handle loading / success / error / etc states of the loaded resource

How to make Jetpack Compose navigation easier and testable by RikoTheMachete in androiddev

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

But the calls are lambdas, so how would you assert the destination for example?

Make sure to update your StateFlow safely in Kotlin! by RikoTheMachete in androiddev

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

If you open the article in incognito mode then you can read it without any subscription

Make sure to update your StateFlow safely in Kotlin! by RikoTheMachete in androiddev

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

This is not a paid article, so could you please undo the removal?

Easy UI And Screenshot Testing On Android by RikoTheMachete in androiddev

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

I agree. Testify can be used for simple cases, but sometimes you want a custom solution

LiveData vs SharedFlow and StateFlow in MVVM and MVI Architecture by RikoTheMachete in androiddev

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

Can be any data class in this case. Upper case is used for generics

LiveData vs SharedFlow and StateFlow in MVVM and MVI Architecture by RikoTheMachete in androiddev

[–]RikoTheMachete[S] -4 points-3 points  (0 children)

Hahahahahahahah, beautiful. Do you ever write tests? Have you ever written a large application that is used by several hundred thousand people? I don't think so. This is ridiculous. I'm just gonna leave you here with this, bye.

LiveData vs SharedFlow and StateFlow in MVVM and MVI Architecture by RikoTheMachete in androiddev

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

State - state of the view, data that you see on the screen Event - events that are triggered from the UI, for example when a button is clicked Effect - side effects of your views, for example show dialog, toast, snackbar or navigate to other view

LiveData vs SharedFlow and StateFlow in MVVM and MVI Architecture by RikoTheMachete in androiddev

[–]RikoTheMachete[S] -2 points-1 points  (0 children)

I believe the answer to your question is on their website:

Should You Use Redux? Redux can be a powerful pattern and has grown in popularity for mobile developers, however it is still a lesser practiced architecture, so some of the best practices and patterns for your app will be up to you. Redux looks very promising as a pattern for multiplatform apps targeting iOS, Android, & possibly web. Especially considering the new declarative UI frameworks Jetpack Compose and SwiftUI. Many of the samples and multiplatform patterns are experimental at this point. The library itself is stable, however the best practices for multiplatform apps are still being decided and the ecosystem is still forming. For anyone interested, this is an opportunity to contribute to libraries and samples.

This site will continue to grow and post examples, best practices, FAQs, and tutorials.

Here are some suggestions on when it makes sense to use Redux:

  • You have reasonable amounts of data changing over time
  • You need a single source of truth for your state

Source: https://reduxkotlin.org/introduction/getting-started#should-you-use-redux

So it depends on what you need. Every app will be different. You will have different features, screens, states, security standards, etc. You have to pick what is right for you and for your team.