This is the 100th episode of Fragmented. We do things a little differently for our 100th episode and field a bunch of listener questions that came in. We’re going a little meta and talking about our experience starting Fragmented, our process, how we pick guests and topics, our setups, our favorite Android libraries and classes (?!).
Thank you so much for being a listener. We cannot express how grateful we are to have you.
.. and many many more
Favorite class and libs
In this episode, Florina returns to talk to us about Google’s recently announced paging library!
The paging library is a powerful take on implementing paging functionality in general, not necessarily linked to a particular technology or library. Florina breaks down the different components and explains what specific function each of them play.
We start off with DataSources, talk about when one would want to use “Tiled” or “Keyed” data sources, and then talk about making them work with RecyclerViews (which is really what 99% of us eventually want). Florina also explains the role of PagedLists, PagedListAdapters and so much more.
If you ever wanted to get an overarching view of Google’s first take on implementing the paging library, this is a great starting point. Listen on so you can understand, try it out and then give feedback to Google, to participate in the making of this new library.
In this episode, Romain Guy from Google gives us the lowdown on a bunch of Hardware related stuff.
He starts off by explaining how the refresh rates on screens matter, what it would mean to have something like a 120Hz display for Android screens, how things like V-Sync and double buffering work, using different screen technologies, how much work is done by the CPU and GPU and so much more.
This was one of those episodes where we tried so hard to hold back for fear of recording for another 2 more hours. Romain is clearly one of the most knowledgable and interesting engineers to talk to today in the hardware land of Android. What a blast!
Screens, refreshing/rednering Color
In this episode, we talk to Florina from Google about the recently released Database library Room. Room was introduced as part of the Android Architecture components and has been picking up a lot of steam in the community.
Room focuses on being a beautiful api layer to Sqlite. Florina explains to us how we can use Room to create a database, creating entities and how they map to tables using DAOs to access data and even “observe” them. Listen on for more of the details!
Micellaneous questions about Room (that we chopped off for lack of time)
Q: Does Room use reflection?
A: There’s only 1 reflection call (at the time of finding the database implementation, when you call Room.builder). Most of the other stuff is generated code (with compile time verification!).
Q: Does Room provide compile-time SQL checks
A: Yes, Room was designed to provide compile-time checks.
Q: Does Room handle SQL injection attacks (security)
Yes … for all practical purposes. See this post for times when it doesn’t.
Q: Do we have tools to access the sqlite database file directly?
Nope, at the moment, adb is your friend. Use that to download the file manually from your device.
In this episode of Fragmented, our friend and RxJava paragon of the Android – Dan Lew, returns for a record 3 and 1/2 time.
We’ve been using RxJava over the years now and have even talked to Dan about it in previous episodes.
How has our understanding of Rx use in Android changed over the years? We know some of the super standard usecases for RxJava in AndroidDev. But the important question to be asking is: when are the times we “shouldn’t” be using RxJava? Are we over-complicating our code by shoe-horning it in different places. Concepts like functional programming and reactive state management have picked up steam again, how has this influenced our RxJava use?
Kobiton – Fragmented