How optimal is to pass a parcelable list of 1000 r...

# android

[Laura de la rosa]

How optimal is to pass a parcelable list of 1000 rows or more from one fragment to another through a bundle?
knowing that I can't persist that list and using navigation jetpack

[Marko Mitic]

bundles have a size limit, so it might randomly crash

[Laura de la rosa]

what is the size limit?

[Marko Mitic]

500KB but it's shared among all active transactions so it's hard to say in practice

[jw]

You don't need to persist the list. Just store it somewhere in memory that's common to both fragments.

[Laura de la rosa]

@jw like a singleton class?

[jw]

Well presumably both fragments are being displayed in the same activity, so you could use an object which is scoped to the activity instance

[jw]

I shudder to even suggest this, but something like a view model in the activity will do just fine

[Laura de la rosa]

@jw thnak you so much

[Marko Mitic]

@jw not a fan of view models?

[jw]

no

[Laura de la rosa]

why?

[Marko Mitic]

View models in general or AndroidX implementation?

[jw]

they're not view models in the defined sense, they have forced subclassing, they have unnecessary lifecycle, they're trying to steal the non-config instance support from activity. it's just a class-keyed service locator and factory with too many responsibilities that leads to bad architecture (no IoC) and state soup.

[Marko Mitic]

that answers it 🙂

[Marko Mitic]

We'll have to make our own KMP-friendly viewmodels, with blackjack and h*****s

[Kelvin Pere]

@jw sent a DM

[Cody Engel]

Android JakePack brought to you by Square

[dave08]

Could you please link an example of what you use instead @jw? Or it's just a simple class with a CoroutineScope? Does yours live through the lifetime of the app, or is it limited by some way (there could be lots of them if they do manage state... but then, they shouldn't?).

[Pablichjenkov]

Use SOLID instead of Android ViewModels and liveData