Looking through Google

How did Google I/O contribute to Android developers?

This year’s Google I/O brought novelties straight outta Sci-Fi movie. You’ve already most probably seen most of the news roaming around the Internet, or at least heard about things like Google Assistant or the newest version of Android’s OS.

For what we have seen, the upcoming months are going to be all about artificial intelligence — which wasn’t difficult to predict. AI is obviously the hottest topic right now — but what is really significant, Google I/O did not only give us more AI but also finally started talking about allowing developers to create their own intelligent solutions using their technology. AI with Google tag is always great news, but the chance to develop your own ideas utilizing their tools and experience is obviously even more exciting.
Let’s take a closer look at what this year’s edition of this big developer festival brought us, and most importantly — what it changes in the context of application development.

To organize: Android Jetpack

Let’s begin with something overlooked by many tech websites, yet so significant for Android developers: Android Jetpack. Behind this quite quirky name hides the great idea of finally organizing and formulating Android’s sources and components.

For those familiar with Android development it’s a well-known fact that if you were to use tools provided on the platform, you need to have the ability to manage chaos. Lots of components you are forced to write from scratch every single time, even though you should be able to utilize what was already created. Being a little cynical: you almost need support to use Support Library.

In addition to that, you have to manage all versions of the platform. Every single one of them differs in code, so if you want to keep compatibility, you have to use libraries provided by Google. The new features are available for the newest version of the system, and they are also added as libraries. Developers always use the newest versions of support libraries, because they contain solutions from older versions of the system.

You can find the full story on our blog

human-centric software design & development. check out our website: www.iteo.com