i notice there’s still a lot of distaste for fragments, what do you guys use in place of fragments?

# android

[Aaron Bond]

i notice there’s still a lot of distaste for fragments, what do you guys use in place of fragments?

[muralimohan962]

I use fragments!

[Can Orhan]

I'm using Flow & mortar in my current contract. Used conductor on personal projects. Personally, I'd use conductor whenever I can.

[BMG]

Plain Views separated based on use case and adding them dynamically to rootView.

[rkeazor]

I see nothing wrong with fragments, especially now that Google has Navigation architecture component

[rook]

I currently have Conductor in production, and I’m regretting it. I’ve been making plans to revert to Fragments, but it’s going to be a rather large undertaking.

[Aaron Bond]

thanks guys, i’ve used conductor and it’s quite good, but it does have its limitations and doesn’t seem to be actively developed.

[Can Orhan]

Hey @rook! I'd love to know what some of the regrets you have are 🙂

[rook]

@Can Orhan I’ll start with the positives, Conductor makes it super easy to move between screens in a way that is very lifecycle safe. Unfortunately, it comes at the expense of not being able to use things like SupportFragmentManager and a pretty brittle interface to all the things we normally rely on in an Activity or Fragment, like context, layout, etc. Our code is littered with null checks in order to interact with the root view component for a Controller. There’s also a bit of overhead introduced by their own lifecycle architecture. While not overly burdensome, it is something to take into consideration that you now have Android lifecycle and Conductor lifecycle to account for when trying to organize your code to run at certain moments.

[Can Orhan]

Thanks so much! Super valuable comments, there