GDD Europe 2017 Report
Redmadrobot, as a member of Google's Certification of Development Agencies, has received several tickets for Google Developers Days Europe. We share our opinions about the program, reports and atmosphere of the conference.
The conference lasted 2 days and took place in 5 tracks: 2 tracks with reports, 2 with workshops and 1 community. Reports partially overlapped with the past I / O, for some of them it became clear how much Google has advanced in each of the disciplines.
')
Blinov Alexander ( @Xanderblinov ), leading Android developer Redmadrobot
The main task that I set for myself is communication with Googlers and GDE. I was wondering how, from the point of view of Google’s engineers, to correctly solve certain tasks and compare their opinion with our vision of the approach. For example, Google engineers and I came to a consensus on the architecture of Android applications — for large applications, you need to use Clean Architecture with MVP / MVVM and routing. Unfortunately, Ben Weiss and Florina Muntenescu did not know about Moxy or Cicerone , but we fixed this unfortunate misunderstanding;)
Google pays great attention to computing in the cloud and Firebase - this technological stack has flashed through a large part of the reports and code labs. In addition to active promotion, Firebase also provides excellent support. If you have any questions about this technology stack, feel free to email them to the relevant Firebase Community on Slack channel. If you have not received a response in the channel, you can ask questions even in lichku to the GDE and Google engineers
In general, Google and GDE engineers turned out to be very sociable and friendly guys who use Clean, Rx, Dagger, Kotlin and drink smoothies!
Kulakov Artem ( @ Fi5t ), the leading Android developer Redmadrobot
I have long been interested in the topic of IoT and Android Things, so I went to the conference for reports on this topic. From the reports it became clear that Google continues to develop the Android Things platform and related infrastructure for it. Such steps have a positive effect on lowering the threshold for entering the topic of developing devices based on microcontrollers. A pleasant surprise was the box with the NXP Pico Pro Maket Kit , which was received by conference participants. This gesture inspired people who did not touch the world of iron to try themselves in this area.
We should also note the ML direction of the company. As they said on Google I / O 2017 - the company took the course AI-first and encourages others to do the same. Calls are supported by appropriate tools that are designed for developers and analysts. In addition to the already familiar Tensorflow and Cloud ML API (Vision, NLP, etc.), I learned about the existence of the Machine Learning Nanodegree course at Udacity, which uses Tensorflow . The conference showed the current level of interest in ML from the community. Most of the people I saw were right at the booth where googles answered ML questions.
Well, the cherry on the cake, for me personally, was the presentation of ARCore . Worthy answer "some other company" and its ARKit;) It's nice that it now works not on one specific device as before, but on quite ordinary Pixel & Nexus. For those inexperienced in graphical modeling, they presented a set of Blocks tools that helps to create 3D models. The tempted is the proposed rendering engine Rajawali , and for the full Jedi left raw OpenGL ES .
Dmitry Timoshilov ( @HellBurund ), leading Android developer Redmadrobot
Sundar Pichai believes that in the coming years, Mobile-first will change to AI-fst. Google Assistant, a personal assistant, is one of Google’s key products in this direction. It was introduced on Google I / O 2017, and now it is clear that Assistant is actively developing. During the demonstration, Google Assistant looked amazing. Developers go to ensure that the device can speak the same way as with a person: long or short phrases, without picking up words, to lead a full-fledged conversation. Now long conversational phrases like:
“Please let me know what the weather is about.”
In this case, the Assistant takes into account the context of the conversation. For example, if you ask:
“Tell me about Spartak football team”
Assistant will tell about the team and its players. To find out any details, it is not necessary to mention Spartak again. Just ask:
“What is the stadium”
and the assistant will tell you about the Discovery Arena, the team's stadium.
The context is also taken into account for correct speech recognition. From several words similar to the ear, the system will select the one that best suits the topic of conversation.
At the same time Assistant is embedded in the application. If you say:
“OK Google, talk to ...”
and call the application, control will be transferred to him. You can learn more about how this works in the video from the conference .
Unfortunately, Assistant does not yet support Russian. But, as managed to learn from the Googlers, support is planned. It is hoped that it will appear within a year.
Another of the loud themes of Google I / O 2017 is Instant Apps , applications launched directly from Google Play, without being installed on the device. For a long time, the technology was in a closed beta, but now Googleers are ready to tell the details.
The essence of the technology is that when the user wants to use some function of the application, it does not load and is not installed on the device as a whole. Google Play loads the module that contains the new feature, and it happens faster.
The main thing that has to change is that the monolithic apk file is replaced by a zip archive containing several apk: one basic and one for each feature. To do this, the application will have to be divided into modules by features.
There is an important limitation. The total amount of basic apk and any of apk with features should not exceed 4 MB. For example, if the size of the basic apk is 3 MB, then the rest should be no more than 1 MB each.
About Instant Apps left open questions. How to make friends with this architecture with Dagger ? How comfortable will the user go from the functionality of the already loaded module to the functionality of the not yet loaded? How to combine Instant Apps modularity with Clean Architecture modularity?
Read more about the implementation of Instant Apps here .
In general, the conference was well organized and each participant could find something interesting for themselves. Each participant received a gift IoT set.
The conference lasted 2 days and took place in 5 tracks: 2 tracks with reports, 2 with workshops and 1 community. Reports partially overlapped with the past I / O, for some of them it became clear how much Google has advanced in each of the disciplines.
')
Blinov Alexander ( @Xanderblinov ), leading Android developer Redmadrobot
The main task that I set for myself is communication with Googlers and GDE. I was wondering how, from the point of view of Google’s engineers, to correctly solve certain tasks and compare their opinion with our vision of the approach. For example, Google engineers and I came to a consensus on the architecture of Android applications — for large applications, you need to use Clean Architecture with MVP / MVVM and routing. Unfortunately, Ben Weiss and Florina Muntenescu did not know about Moxy or Cicerone , but we fixed this unfortunate misunderstanding;)
Google pays great attention to computing in the cloud and Firebase - this technological stack has flashed through a large part of the reports and code labs. In addition to active promotion, Firebase also provides excellent support. If you have any questions about this technology stack, feel free to email them to the relevant Firebase Community on Slack channel. If you have not received a response in the channel, you can ask questions even in lichku to the GDE and Google engineers
In general, Google and GDE engineers turned out to be very sociable and friendly guys who use Clean, Rx, Dagger, Kotlin and drink smoothies!
Kulakov Artem ( @ Fi5t ), the leading Android developer Redmadrobot
I have long been interested in the topic of IoT and Android Things, so I went to the conference for reports on this topic. From the reports it became clear that Google continues to develop the Android Things platform and related infrastructure for it. Such steps have a positive effect on lowering the threshold for entering the topic of developing devices based on microcontrollers. A pleasant surprise was the box with the NXP Pico Pro Maket Kit , which was received by conference participants. This gesture inspired people who did not touch the world of iron to try themselves in this area.
We should also note the ML direction of the company. As they said on Google I / O 2017 - the company took the course AI-first and encourages others to do the same. Calls are supported by appropriate tools that are designed for developers and analysts. In addition to the already familiar Tensorflow and Cloud ML API (Vision, NLP, etc.), I learned about the existence of the Machine Learning Nanodegree course at Udacity, which uses Tensorflow . The conference showed the current level of interest in ML from the community. Most of the people I saw were right at the booth where googles answered ML questions.
Well, the cherry on the cake, for me personally, was the presentation of ARCore . Worthy answer "some other company" and its ARKit;) It's nice that it now works not on one specific device as before, but on quite ordinary Pixel & Nexus. For those inexperienced in graphical modeling, they presented a set of Blocks tools that helps to create 3D models. The tempted is the proposed rendering engine Rajawali , and for the full Jedi left raw OpenGL ES .
Dmitry Timoshilov ( @HellBurund ), leading Android developer Redmadrobot
Sundar Pichai believes that in the coming years, Mobile-first will change to AI-fst. Google Assistant, a personal assistant, is one of Google’s key products in this direction. It was introduced on Google I / O 2017, and now it is clear that Assistant is actively developing. During the demonstration, Google Assistant looked amazing. Developers go to ensure that the device can speak the same way as with a person: long or short phrases, without picking up words, to lead a full-fledged conversation. Now long conversational phrases like:
“Please let me know what the weather is about.”
In this case, the Assistant takes into account the context of the conversation. For example, if you ask:
“Tell me about Spartak football team”
Assistant will tell about the team and its players. To find out any details, it is not necessary to mention Spartak again. Just ask:
“What is the stadium”
and the assistant will tell you about the Discovery Arena, the team's stadium.
The context is also taken into account for correct speech recognition. From several words similar to the ear, the system will select the one that best suits the topic of conversation.
At the same time Assistant is embedded in the application. If you say:
“OK Google, talk to ...”
and call the application, control will be transferred to him. You can learn more about how this works in the video from the conference .
Unfortunately, Assistant does not yet support Russian. But, as managed to learn from the Googlers, support is planned. It is hoped that it will appear within a year.
Another of the loud themes of Google I / O 2017 is Instant Apps , applications launched directly from Google Play, without being installed on the device. For a long time, the technology was in a closed beta, but now Googleers are ready to tell the details.
The essence of the technology is that when the user wants to use some function of the application, it does not load and is not installed on the device as a whole. Google Play loads the module that contains the new feature, and it happens faster.
The main thing that has to change is that the monolithic apk file is replaced by a zip archive containing several apk: one basic and one for each feature. To do this, the application will have to be divided into modules by features.
There is an important limitation. The total amount of basic apk and any of apk with features should not exceed 4 MB. For example, if the size of the basic apk is 3 MB, then the rest should be no more than 1 MB each.
About Instant Apps left open questions. How to make friends with this architecture with Dagger ? How comfortable will the user go from the functionality of the already loaded module to the functionality of the not yet loaded? How to combine Instant Apps modularity with Clean Architecture modularity?
Read more about the implementation of Instant Apps here .
In general, the conference was well organized and each participant could find something interesting for themselves. Each participant received a gift IoT set.
Source: https://habr.com/ru/post/337742/
All Articles