accompanist VS simple-stack

The truly disheartening part is that whenever you choose something that works, for example ViewPager1, you need to defend that yes, this thing actually works as intended, yes, there's nothing in it that would "break over time" just because Googlers added the @Deprecated on it, and yes, you still don't want to use Compost for this because you still cannot scroll vertically in a horizontal Pager if your view is a WebView.

Compose on the other hand came out half-baked, significant performance issues, missing features, bugs and bugs and bugs and bugs and bugs and bugs and bugs and bugs and bugs.

Just to add to the list, Accompanist is a collection of compose libraries that helps a lot with some features. I can recommend Navigation-Animationand Permissions. https://github.com/google/accompanist

To give a bit of context, libraries not released as Jetpack libraries as experiment projects. Once they're released as Jetpack libraries, we have stricter release schedule in place and more resources to provide better stability for developers. That's why some Accompanist libraries end up as part of Compose foundation set, while others are still being shipped as part of the Accompanist project.

So you're going to get support for Parcelables in argument passing, animation support without having to fear crashes, and if you drink the ScopedServices koolaid you even get to get DI with lifecycle management and scope inheritance.

Here's a fun bug though https://github.com/google/accompanist/issues/1233

There is a bug the preview is not working when System UI controller is used. See issue tracker here.

👋 I have been using Mobius personally and for work for over two years now. It's a lot of fun to use and I would definitely recommend the community to consider using it. I frequently visit their GitHub repo because they still have their documentation in the GitHub wiki, unlike new repos such as Accompanist. So, I thought what better way to give back than do the grunt work of porting their wiki to GitHub Pages + MkDocs ❤️🔥

Accompanist for unofficial stuff that's still useful

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.