Fragments: Past, present, and future (Android Dev Summit '19)

[@dnkilic]

thank you for helping out guys, looking forward for better fragments

[@gryzor]

I think is is a move in the right direction. To me, Fragments should have been views since day one.

[@moshewaisberg7639]

sounds more like custom views

[@johndoe2]

9:50 I love this part where he realizes he should've talked first about their solution, and then how it was before, like in the presentation :)

[@alxrm0]

hey try drinking a shot every time Ian says "kind of"

[@IanLake]

It is kind of my thing.

[@richardshin4443]

Android development has gotten so complicated over the years. Actually, it seems like we are going back and filling in the gaps that were always there in the past. Sigh. Disilliusionment. Clean architecture or Architecture Components or some mix of the two? Dagger with clean architecture, what about multi module or module by feature? I guess despite the complexity, it has been a steady march toward better and brighter things.

[@llothar68]

Clean Architecture is the reason why Android programming has become such a total mess.

[@narendranathreddy5046]

Anyone has the code link for the scenario told in this talk - Avoiding fragment recreation when switching between tabs in bottom nav?

[@ankur.singhs2111]

I have less functions to imllement, I should use fragments with a single activity or multiple activities ? Also tell if anything else I should take care of, thankyou.

[@angelserrato5340]

Fine video Thanks!😀

[@devyanshbhati3337]

really appreciated !!!

[@jonsnow9758]

I thought I was the only one who find fragment communication little weird. Now I see the problem is real.

[@Neo-wd3qy]

good but wish compose can kill the entire fragments

[@IanLake]

I talked about this over on Twitter where Fragments are a useful way of adopting Compose into an existing app, but wouldn't be something you'd use in a pure Compose app: twitter.com/ianhlake/status/1188983854410825728

[@igorg.8624]

@@IanLake So a year from now we'd use 'Pure Compose' and without any fragments?

[@IanLake]

@@igorg.8624 - that's what I said.

[@nawshadhamid]

No? Compose is just the replacement of Layout XML Editor.

[@Alfrednohike9909]

@@IanLake today's that day

[@sumitshukla6436]

Jeremy Woods is a rapper !!

[@chitho1987]

That was exactly I was thinking lol, his voice is so cool

[@gilbertsenyonjo963]

Damn right!

[@IgorKorotenko]

Fragments, loaders, navigation...they were born dead APIs, weakest things in Android were invented in this team and they are still doing this being completely disconnected. Passing data between fragment? Really, back handling? That what you did for so many years and mess of saved state error is still there..

[@thecsciworker291]

@@ferryzet Using almost all features available for navigation component...No issues what so ever.

[@dantichri5t]

I am learning to develop Android apps ( already a Java and web developer, so not exactly new to software ) and I am still trying to understand who on earth invented such a complicated way to achieve such a simple final result. Not as pointless and counterproductive as Spring and JQuery are ( my opinion ), but this is a close third. Glad to see other people dislike them so much - I thought there was something wrong with me!

[@mohammadsayed5645]

Simple Question: What you are wearing on your feet, Ian?

[@IanLake]

Vibram Five Fingers. Specifically the CVT Hemp.

[@mohammadsayed5645]

@@IanLake thanks

[@sourabhjigjinni]

Android devs should consider creating a best practices playlist, so that the average dev, could just incorporate into their projects everytime they change something. The offical docs are terrible. This doesnt seem convincing at all, they know its a mess

[@mdalikazi]

Why do they keep talking about Fragments in every Android event? I'm happy with what Fragments can do, we don't need to talk about this anymore!

[@eliasbagley]

The Fragment API is a mess and leads to hard to test God objects.. I for one am happy to see progress in this area.

[@igorg.8624]

What is the best way to test Fragments with Jetpack Navigation?

[@KangJangkrik]

Sorry for a year late, but I still found nothing

[@dhruvgarg722]

where can we get slides used in this presentation?

[@VladVoytenko]

not availble - it was only on a presentation

[@mykhailomykytyn]

How do you call a magician who lost his magic?

[@talgatb.3109]

Why dont have russian subtitles at least?

[@roxferesr]

To this day, I don't get why we need fragments in the first place. What's wrong with custom views?

[@igorg.8624]

Simply for ViewModel scope.

[@agung_laksana]

And for navigation component

[@krishnaappworlds3486]

add more then one fragment then recyclerview lagging issue

[@alexneeky7920]

Oh, it’s in rc1 cool

[@andievalderama]

vibrams in 2019, cool

[@marlonlom]

Fragments.. All u must know about screen design in Android jajaja

[@ruybarreto3556]

worst thing android made after context

[@cooliipie]

You think that's good looking UI? ......

[@marlonlom]

Do u mean the Slides?

[@asadkhandadlo6572]

Jajaja 😂🤣😂🤣

[@danitz4366]

I'm from Perú, ¿you?

[@Muhammad55597]

worst thing android made

[@asadkhandadlo6572]

Why do you think that 🤔🤔🤔

[@alexneeky7920]

no, it’s not, worst thing is Context - God object and all app depends on it

[@dominikotocan1348]

@@asadkhandadlo6572 They can become too complicated to manage because you have fragment lifecycle and the parent activity lifecycle to watch. Architecture components helped a lot with that but still, there are too many things that can go wrong

[@AnkitGusai]

@SnoopyDoo Well Dagger is not part of framework and it has its specific purpose and every app would not benefit from using dagger.