I will try to show you, why - in my opinion - Conductor is the best tool for the job, and has the best chance to finally rid us of Fragments in the Android world. Specifically, recently we got Scoop, Pancakes and Conductor. We would see more attempts of getting rid of Fragments. But in the end it was really great, it showed the community that we are able to try improving on the Fragments paradigm. Especially, the boilerplate was sometimes bigger than in Fragments. It was too complicated and, because of the lack of simple examples, it was way harder to incorporate in apps for many developers. It was a major change compared to Fragments - everything was based on Views, eliminating most of the problems Fragments had.įast forward to the present day, we know that Mortar&Flow didn’t take off, as many of us hoped for. They took it even further, and created Mortar&Flow, a replacement for Android Fragments. Two years ago they made a detailed critique of fragments you can read it here: Advocating Against Android Fragments. Square - a company behind many successful open source libraries - took this problem to heart. They are hard to debug and generally unfriendly to developers. There is a lot written about problems with Fragments on Android, their bugs, weird behaviors, boilerplate needed to make them work and overly complicated lifecycle.
0 kommentar(er)
