Interesting to see this video from yesterday reall...

# confetti

[John O'Reilly]

Interesting to see this video from yesterday really doubling down on message that ViewModels are still very much needed

https://www.youtube.com/watch?v=V-s4z7B_Gnc▾

[John O'Reilly]

"The ViewModel API is the only supported way to make large and arbitrary objects survive configuration changes on Android"

[John O'Reilly]

re "supported", maybe you lose your warranty or something if you use alternative approach 😃

[bod]

in a way I'm glad, it means thousands of projects and millions of lines of code don't have to be rewritten once again 😛

[John O'Reilly]

what would we do if we weren't always rewriting our apps 😃

[bod]

hahaha 😄 true story

[bod]

that feeling when opening an Android project that hasn't been maintained for 2 years... "oh boy, I guess I'll just rewrite from scratch then"

[John O'Reilly]

def does feel like that sometimes 😃

[mbonnin]

"The ViewModel API is the only supported way to make large and arbitrary objects survive configuration changes on Android"

Well.. SQLiteNormalizedCache would like a word about this

[mbonnin]

But yea, maybe the "key" thing here is "supported"

[yschimke]

"supported" is a load bearing adjective in that sentence

[romainbsl]

I quickly tried to work without ViewModels on Android, I miserably failed. Some libraries authors are trying to dissociate from Android’s ViewModels, like Voyager, as you need to create custom scopes based on a Android lifecycle stuff, that’s not that simple.

[yschimke]

I think that's the point. It's not that you want to solve this yourself. But if you want a library to solve it, that library can either extend the quirky viewmodel abstraction to non android. Or it can use some non viewmodel abstraction including on android.