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

16.10 Custom Accessors

When accessing the accountBalance property in the previous section, the code is making use of property accessors that are provided automatically by Kotlin. In addition to these default accessors it is also possible to implement custom accessors that allow calculations or other logic to be performed before the property is returned or set.

Custom accessors are implemented by creating getter and optional corresponding setter methods containing the code to perform any tasks before returning the property. Consider, for example, that the BankAcccount class might need an additional property to contain the current balance less any recent banking fees. Rather than use a standard accessor, it makes more sense to use a custom accessor which calculates this value on request. The modified BankAccount class might now read as follows:

class BankAccount (val accountNumber: Int, var accountBalance: Double) {

 

    val fees: Double = 25.00

...