A modern programming language that makes developers happier.

kotlinlang

In <https://github.com/terrakok/Compose-Multiplatform-Wizard> why is it creating the `AndroidApp` class is implemented as a singleton!? :thinking_face:

The `AndroidApp`  is not created as a singleton, as it is not even created manually. It’s only holding an static reference to the app instance created on the app startup

Not a singleton per se yeah, wrong description

```class AndroidApp : Application() {
    companion object {
        lateinit var INSTANCE: AndroidApp
    }

    override fun onCreate() {
        super.onCreate()
        INSTANCE = this
    }
}```

The `Application` class is always a singleton, because that’s how the Android framework creates and handles it. The generator is not creating the singleton, it’s just assigning the instance to a variable to make it easy to access throughout the rest of the app. This is a very common pattern among Android apps (though it’s arguable whether or not it is a good or necessary pattern in pure compose apps)

The alternative would be something like `context.applicationContext as AndroidApp`, littering your app with unchecked casts

I was pretty much going to say the same as <@UD17D4K8W>. The `Application` instance won’t be garbage collected as it’s always used. So there’s no penalty on having it as an static reference, and it’s pretty handy for some use cases

I believe it's still not recommended to store Application context into a global variable.
1. It may break features like Instant Run/Live Edit
2. If the process is killed and a ContentProvider is called, the application may be still `null`.

There should also be a lint warning about it. At least it was in Java, as far as I remember.

I was unaware of what you’re saying here <@UHAJKUSTU>. Thanks for the info!

I think it is “dirty” example for simplest dependency container