And the point of the Companion Object is just to provide a reference to the unique instance of App to different threads? If that’s the case, then I understand the example, although it’s probably not the best choice for a first example on Companion Objects, due to the weird class Application (whose quirks are not explained in your article), which adds to the confusion. So what happens if you try to instantiate App twice? The constructor of Application throws an exception? If I understand it, App is actually already a Singleton due to its super-class Application, and regardless of the Companion Object that you added to it.

If you like what you’ve seen, I encourage you to sign up for my free training, where I’ll tell you everything you need to learn about how to create your own Android Apps in Kotlin from scratch. Objects are a new concept for those of us coming from Java 6, but there are many ideas that can be associated with existing ones, so you’ll get fast with them. One might think it’s as simple as this: public class Singleton ') Conclusion Singleton in Java isn’t as easy to implement as it sounds. So if we want to find something similar in Java, that would be the Singleton pattern. In fact, an object is just a data type with a single implementation. Kotlin objects are another element of the language that we Android developers are not familiarized with, because there is nothing like that in Java.

Kotlin by lazy with parameter