When developing a library, designing an easy to use API while hiding unnecessary implementation details from clients is fundamental. Let’s look at some API design choices we’ve made for our library Krate, an Android SharedPreferences wrapper.
We all use different git configurations for various reasons, and it’s easy to get them mixed up. Here’s a look at some ways of managing them better.
There has been a website of some sorts up on this domain for a couple years now. Here’s a history of what powered it at various times.
A quick preview of the new SavedState support for Android Architecture Component ViewModels.
A perhaps overly thorough look at how extensible state saving is implemented in the AndroidX libraries, and how ViewModel state saving specifically is hooked into this system.
Not breaking client code is an essential duty of a library developer. Let’s take a look at a couple rarely discussed issues you might face in this area.
It’s the end of the year, and looking back at what you’ve done in the year that passed is, like, a thing. So I’ve decided to take a shot at it too.
Data classes are great, but don’t underestimate what a regular Kotlin class can do on its own.
Retrofit’s coroutine support has been a long time coming, and it’s finally coming to completion. Take a look at how you can use it to neatly integrate networking into an application built with coroutines.
The @JvmOverloads annotation is a convenience feature in Kotlin for interoperating with Java code, but there is one specific use case on Android where it shouldn’t be used carelessly.