11 Slides from DroidCon NYC 2015 - Part 2
In the previous post, I introduced the first five slides I chose from DroidCon NYC 2015. Here is the second part with the remaining ones.
6. Have you seen Cloud Spin?
Bulletproof Android wasn't the only talk that taught us Matrix techniques. In this case, Bret McGowen and Ray Tsang showed us how to use phone cameras to record movies like the Wachowski brothers in The Matrix. To be more specific, do you remember that scene where Trinity jumps to kick a bad guy and when she's in the air, the camera freezes and rotates 180-degrees? Well, if you have 19 Android devices, you can do it too. The camera part, at least...
So, the slide I've chosen from this talk is the engineer schematics of this project called Cloud Spin demo.
Since this talk also has a stand, I'll leave a bonus with this slide, which is myself playing with the spins, but remember, security has to be the number one priority, so guys and gals be sure not to try this at home alone.
7. Tools of the trade
Talking about tools, Sebastiano Poggi brought a very comprehensive and useful list of tools when writing Android code. The slide I picked from this talk is an obvious one but many times forgotten. So, besides the existence of this tag, it's very common to read "real" text on layouts even when it's for testing purposes.
Sebastiano's reminder, if you want to see how a text looks like in a layout, just use tool:text tag instead of android:text.
8. How the Main Thread works
More on tools, Michael Bailey from American Express gave a great talk about threads on Android. If you have written code on Android you know how challenging it might be to deal with main thread, background threads and communication mechanisms, so this talk really sheds light on this subject and also gives a list of resources and tools. In fact, the slide I picked from this talk is a screenshot showing Android Trace View, a tool that shows an application stack over time, which might be very helpful to detect code that's blocking the main thread.
9. What’s New in Android UI Engineering
Back to UI and Layouts, Roman Nurik, Nick Butcher and Chris Banes came with amazing new stuff on Android UI. One of them is the new PercentRelativeLayout. So, if you used to waste a lot of time trying to build responsive UI with LinearLayout, use the new PercentRelativeLayout, and not only will it be easier, but it has a better performance, as well.
10. Common slides on different talks
There were two slides that got repeated in several talks. The first one worth mentioning was Israel Ferrer's meme "Let me explain you", this became part of the folk of the conference and beyond, so here is the story. Israel was meant to give a talk during Droidcon NYC 2015 but he couldn't make it and he told the organizers in advance, so all the speakers added a slide with an Israel's photo and his favorite phrase: let me explain you.
The second most common slide during the event was perhaps a sign that this is a great moment to be an Android Developer because most of the companies for whom the speakers work are hiring. In fact, the president of the United States, Frank Underwood himself, was doing this job.
11. Be a Good Citizen: Develop Maintainable Apps
The last slide is from Annyce Davis’ talk about good practices on developing android applications. During the talk, she describes good criteria to choose what to use or not on an Android project. She also talks about testing and very briefly about an application architecture. And this is the slide I chose. “Have you seen this before?”, Annyce asks. "Here we have a snippet from an Activity which contains an animation, chromecast support, fragments and it goes on and on. This code violates the single responsibility principle".
That's it. I've written many classes that violate the single responsibility principle and that's why I felt so bad about it. Ok, I read about Uncle Bob’s clean architecture and some others’ too and I knew there's something really important to work on but I didn’t know the name until I heard Annyce and remembered the single responsibility principle.
This slide leads us to an open discussion, which, if I am lucky enough, I will tell about in next posts. It will be started off by the question: how can we build applications using classes or activities or components which follow a single responsibility principle?
Do you know the answer? I'll be very glad to know.
References
Have you seen Cloud Spin? - Blog Post.
Tools of the trade - Blog Post.
How the Main Thread works - Android Studio TraceView.
What’s New in Android UI Engineering
Be a Good Citizen: Develop Maintainable Apps
Single Responsibility Principle













