simple-stack VS guide-to-kotlin

As someone who had been using single-activity since 2015 (a'la Flow) and eventually just rewrote the whole thing to fix all the bugs we had with it in 2017, I find it sad that the single-activity approach was questioned not because it was harder, but because people made their own lives harder. And then Google made their lives harder.

I've been using single-activity but with Simple-Stack since 2016 and never deprecated it because Navigation just has these quirks that impede you a lot. I know how to use it but wouldn't really pick it.

This is why we've been using https://github.com/Zhuinden/simple-stack and it was never deprecated. We've been using it for 6 years, I'd say there was a critical bug but it was fixed in 2.3.1...

I mean, we use Simple-Stack because it makes things easier, if it didn't we'd have ditched it long ago https://github.com/Zhuinden/simple-stack

Agreed. I also added support for it 2 weeks ago.

I don't, because we use this and it's better than activities+intents 😅

We've been making single activity apps with https://github.com/Zhuinden/simple-stack and it has been easier than multi-activity.

I still use https://github.com/Zhuinden/simple-stack to this day, although I still use it with fragments.

I have been using Fragments instead of compound viewgroups lately with simple-stack as the navigator for the single-activity, although I need to figure out how to switch to use onBackPressed+onBackInvokedCallback and not just onBackPressed.

You can think of Simple-Stack as a direct successor of Mortar+Flow.

Read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you'll know Kotlin. That, and you can also check the collection APIs which are pretty much the best thing in Kotlin compared to Java.

I would recommend learning Kotlin for Android though, it does help. I wrote this guide https://github.com/Zhuinden/guide-to-kotlin/wiki but you can also look at this video https://www.youtube.com/watch?v=wuiT4T_LJQo

I wrote this guide for Java => Kotlin a few years ago, other than me not adding coroutines it still holds: https://github.com/Zhuinden/guide-to-kotlin/wiki

Check this guide by me to learn Kotlin: https://github.com/Zhuinden/guide-to-kotlin/wiki

but you can read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you will know what you need to know for Kotlin basics (except coroutines, then you watch https://www.youtube.com/watch?v=6P20npkvcb8 )

I wrote https://github.com/Zhuinden/guide-to-kotlin/wiki a few years ago for people who know Java and don't know Kotlin, I've heard many positive feedback for how simple it is to transition from Java to Kotlin once reading through it.

you should probably look into Kotlin (see https://github.com/Zhuinden/guide-to-kotlin/wiki and/or https://www.youtube.com/watch?v=wuiT4T_LJQo ),

You actually can just read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you'll know how to use kotlin lo

I wrote this guide a while ago specifically to cover this kind of migration https://github.com/Zhuinden/guide-to-kotlin/wiki it should be fairly no-nonsense and I've heard people like it (they said it helped them).

I didn't need to because by the time it came out I already knew Kotlin, personally I wrote this https://github.com/Zhuinden/guide-to-kotlin/wiki