The Android platform
Since the start, I loved changing to the new stage and learning new things about exercises, offbeat programming, pop-up messages, and simultaneousness. At that point, Honeycomb showed up with sections; and afterward, Ice Cream Sandwich with Holo. Individuals were having a great deal of fun composing code for little applications.
As applications developed, devs began to consider cleaner code, better architectures, better apparatuses, and testing. They understood that those immense action classes would reverse discharge one day and they reused great programming designs and concocted new ones. Everyone began discussing MVP, MVVM, hexagonal engineering, and open-source libraries where flourishing. I was amped up for perusing each one of those posts by individual developers and viewing those incredible talks.
The Android stage was intended to be exceptionally adaptable. In reality, I believe that is its most prominent quality and that is the reason it takes a shot at such huge numbers of telephones, tablets, TVs, watches, vehicles, and things. It was believed to be versatile, continually monitoring equipment imperatives like CPU speed, memory, and battery. Android’s layered design permits isolating worries for various advancements and groups chipping away at them. On account of this, for instance, Google had the option to consistently change to OpenJDK in Android Nougat:
android structure
Source: https://source.android.com/security/
Something feels wrong
I think Android is an incredible stage, yet I likewise imagine that some APIs accessible to engineers in the structure layer (the green one in the past picture) should be upgraded.
Exercises are ostensibly the most significant part in Android, and alongside pieces, they are difficult to get a handle on and to be utilized correctly — and Google knows it. Their lifecycle is perplexing, and this solitary adds unpredictability and disarray to the engineer:
