MavenCentral is the place to be for Android libraries, but publishing there is no easy task. With JCenter going away soon, this problem is more timely than ever. Here’s the step-by-step guide on how to do it.
Kotlin 1.5 will bring exciting new features, among them improvements to sealed classes and an introduction of sealed interfaces. Let’s take a look at what that will look like!
In MVVM-like view architectures, view state isn’t enough to communicate from the ViewModel to the View. They have to be supplemented by some kind of events, which come with several challenges you should be aware of.
Fragments have… Complicated lifecycles, to say the least. Let’s take a look at these, and how they all fit into the world of Jetpack today, with LifecycleOwners, LiveData, and coroutines.
RainbowCake is an Android architecture framework, providing tools and guidance for building modern Android applications.
Accessing SharedPreferences using its API directly can be somewhat inconvenient. Krate is a library built on Kotlin delegates to simplify the use of SharedPreferences.
One of the most significant items of the Effective Java book is Item 18: Favor composition over inheritance. Let’s see how Kotlin promotes this with class delegation.
When designing a library, minimizing your API surface – the types, methods, properties, and functions you expose to the outside world – is a great idea. This doesn’t apply to just libraries: it’s a consideration you should make for every module in a multi-module project.
Let’s send this one off so that we can get started on a better one. The “usual” recap of what I’ve done this year.
I think any respectable service these days should offer a web API to paying customers, so that power users of the service can integrate it with other services, and have reliable, trustworthy programmatic access to their data. Here are some anecdotes about services and APIs.