I skipped work and went straight to Yokohama to a Google event.

It is a good company that willingly sends you off to all-day events. We are also recruiting, so please enter here.

Well, I have to recover from this day's worth of work somewhere.

It was my first time participating in an event in a long time, but it was quite interesting. The fun of going to a place like this is to listen to the tracks of the frontrunners in the tech industry, of course, but even more so to watch the participants. It's obvious to say it, but there are a variety of people, young and old, men and women, from young female engineers to Lehman who wants to wear a suit, to an old man with a big belly, and it's kind of emotional to think that I'm in the same cluster as these various miscellaneous people.

Well, I myself am an Android app developer, so I will pick up interesting things from that perspective.

Android Studio 2.2

Android Studio is a development environment used for Android app development. Without this, you can't make an app. You can make it originally, but it is a very hurdle. It opens the door to easy app creation for Android newbies. That is Android Studio (AS).

In the past, we used an IDE called Eclipse with an Android Developer Tool plugin, but now it's an IDE based called IntelliJ, which is more modern and responsive. Personally, I don't think the usability itself will change much, but I feel that the build using Gradle is definitely more advanced than the ant-based ADT. It's not a topic of AS, though.

Adding ConstraintLayout and FlexboxLayout to Layouts

As a full-fledged developer, you can edit xml without relying on the layout editor that comes with AS! Or rather, the editor is useless, so that's the only option! There has been no progress in that area since the ADT era! I think this is the common view of Android app developers, but it seems that something that can be used properly is finally coming out. Its name is ConstraintLayout and the AS GUI editor that supports it.

ConstraintLayout

When building an Android layout, I think it is usually made by combining LinearLayout and RelativeLayout, but if you design a nested LayoutGroup like that, it will have a negative impact on the drawing speed. I didn't know, or rather, even if I did, there was nothing else I could do. With ConstraintLayout, it seems that you can design with almost only that layout, and you don't need to nest the LayoutGroup, so is it good for performance? That's what he said. This is the only way to use it.

The only thing I'm worried about is the naming and good usability, isn't this the same as the iOS Storyboard? It was so chrysotic. You won't be hit by Apple, right? this.

Well, Storyboard is almost a GUI-only layout design, so I'd rather touch the configuration file! I didn't like it very much, but I thought it would be nice if I could create a certain amount of things in the GUI and edit the generated xml by hand.

FlexboxLayout

And the other one is Flexbox-layout, which also seems to be a white thing that can be used for Android layout with CSS Flexbox. Are you okay? This rip-off.

Speaking of CSS from a long time ago, it was a float group. As someone who has seen hell there, I really like Flexbox. But if ConstraintLayout is useful enough, I don't need to remember this. However, Japanese engineer @thagikura writes it, so I hope it will be exciting.

FlexboxLayout page https://github.com/google/flexbox-layout Do your best.

Integration with Firebase

Seamlessly connect from Android Studio to Firebase (or do you say?) It seems that you can do it. This is an atmosphere that the only way to use Firebase on the server side of Android apps is to use Firebase. Personally, I was curious about Firebase Test Lab for Android.

Test Lab for Android https://firebase.google.com/docs/test-lab/ It seems that you can easily test it with an actual machine installed remotely, but depending on how easy it is, I would definitely like to use it. As a simple explanation, there are 900 Android screen sizes that must be supported x 30 languages that must be supported x 2 types of landscape and poatrait = 5400 cases of testing are required. . . It was a scene that I thought would be difficult to use a global app.

Android Emulater

I thought AS 2.1 was fast enough, but it seems to be even faster. 10 times? Is it faster than the actual machine? You may not need to connect the actual device to USB and test it anymore.

The End

That's what I said. In addition, there were a lot of Firebase-related tracks, and it was an atmosphere that Google was going all out for Firebase. The rest is GCP, which we should not forget, but that's for another time.