Releasing an app to an app store like the Google Play Store is a common task that Android developers have to go through.
Because you need to verify that you are the owner of the respective app, you need to digitally sign your APK (Android application package) or AAB (Android App Bundle) before being able to upload it.
To be able to sign your application, you need to generate a .jks (Java KeyStore) file that contains your certificate.
If you are working alone on your app, you can easily use the Android Studio’s built-in Generate Signed Bundle/APK function.
The look and feel of an app is one of the main factors when it comes to the point of how the overall app experience appears to the user.
In general, we see rather static buttons in mobile apps. Therefore, if you want your UI to really stand out, why don’t you try to use animated buttons?
In this article, I will show you how you can use a Lottie Animation to use the animations to represent different button states and also to have really nice click animations.
The inspiration for this article came when I implemented a button in…
Android 12 is coming. With Beta 4, it has just reached platform stability. Taking a look at the timeline below, the final build is expected to be released in November 2021.
Paging 3 is the recent evolution state of Android’s Paging Library. The component allows you for example to easily integrate paging REST Endpoints or let you load database entries from Android Room in a paging manner.
If you use the library as it is intended, you will not have any problems. Regardless of whether you load the data directly from an API or database, the data is determined by that data source.
But what if we need to edit the items that are already queried and set to our adapter?
How to solve this issue is what we are going…
It is mostly used for updating the UI with a new state of the respective ViewModel. By using this component we can switch from a pull to a push behavior when we need to inform our UI about state changes.
Sometimes you don’t only want to get informed about one single item but multiple ones.
Especially when it comes to multiple asynchronous LiveData streams that are required at the same time to…
In most cases, Android apps consist of multiple screens that are interconnected with each other. One screen can be accessed via interaction with another.
In earlier stages of Android development, one would rely on manually pushing and popping fragments via
With the introduction of the Navigation component library, which got released within the context of Android Jetpack, manual handling of these transitions is now a thing of the past.
The first Navigation component library stable release is available since 2019. It drastically facilitates consistent behavior for navigation within your Android app. …
viewModels delegate lets us initialize our
ViewModel in our Android app’s activities or fragments with no effort.
However, the drawback of this function is that we are limited to the initialization of our respective
ViewModel without the ability to use any initial parameters via a constructor.
Because in many cases we have parameters that get passed by a previous screen via Navigation Component’s safe args or on the standard way via the arguments or intent bundle, we often need these parameters in our
If we show a list on our screen that depends on the respective parameters…
The Event Bus design pattern is a well-known practice that has been widely used in many Android apps in the past to achieve an event-driven architecture.
With the slow replacement of Java by Kotlin over the recent years, this approach was almost forgotten. Kotlin itself and also other popular frameworks nowadays offer various options for implementing a publisher/subscriber architecture, such as Kotlin Flow, RxJava, or LiveData.
This article will be the second post in my new series about refactoring tips for Android Studio and IntelliJ IDEA.
In my last article, I talked about the “Find and Replace” feature which lets you easily change specific keywords across your whole project or scoped to explicit sections of your codebase.
This succeeding post will be covering another feature that astonishingly facilitates the refactoring of your code.
We will be talking about the “Change Signature”. As the name already implies, this feature allows you to easily refactor function signatures.
The “Change Signature” refactoring function can be found in the refactoring…
Kotlin Inline Classes are a subset of the Kotlin Value classes. An inline class can be used as a wrapper around some other type, described on a very high level.
Within this article, we take a detailed look at the new syntax for inline classes, introduced with Kotlin 1.5, and how to use the feature in practice.
If you come from Java, a very good example for understanding the basic principle is to look at the wrapper classes for primitive types. Let’s take a look at the class
Boolean, that wraps the primitive type