Book Image

Android Studio 3.5 Development Essentials - Kotlin Edition

By : Neil Smyth
Book Image

Android Studio 3.5 Development Essentials - Kotlin Edition

By: Neil Smyth

Overview of this book

Popularity of Kotlin as an Android-compatible language keeps growing every day. This book will help you to build your own Android applications using Kotlin. Android Studio 3.5 Development Essentials Kotlin Edition first teaches you to install Android development and test environment on different operating systems. Next, you will create an Android app and a virtual device in Android studio, and install an Android application on emulators. You will test apps on physical android devices, then study Android Studio code editor, Android architecture, and the anatomy of an Android app. The focus then shifts to Kotlin language. You’ll get an overview of Kotlin language and practice converting code from Java to Kotlin. You’ll also explore Kotlin data types, operators, expressions, loops, functions, and the basics of OOP concept in Kotlin. This book will then cover Android Jetpack and how to create an example app project using ViewModel component, as well as advanced topics such as views and widgets implementation, multi-window support integration, and biometric authentication. Finally, you will learn to upload your app to the Google Play Console and handle the build process with Gradle. By the end of this book, you will have gained enough knowledge to develop powerful Android applications using Kotlin.
Table of Contents (93 chapters)
93
Index

18.7 Configuration Changes

So far in this chapter, we have looked at two of the causes for the change in state of an Android activity, namely the movement of an activity between the foreground and background, and termination of an activity by the runtime system in order to free up memory. In fact, there is a third scenario in which the state of an activity can dramatically change and this involves a change to the device configuration.

By default, any configuration change that impacts the appearance of an activity (such as rotating the orientation of the device between portrait and landscape, or changing a system font setting) will cause the activity to be destroyed and recreated. The reasoning behind this is that such changes affect resources such as the layout of the user interface and simply destroying and recreating impacted activities is the quickest way for an activity to respond to the configuration change. It is, however, possible to configure an activity so that it is not...