I’ve been invited as speaker at Mobiconf 2015 in Krakow. It was a really nice event and the place was a real cinema, quite an intimidating stage
I want to thank to the organizers for such a wonderful event and the excellent treatment received. If they are interested on inviting me again, I will for sure repeat next year.
Here is a list of the conferences I’ve attended and a small wrap-up. I’ll add the links to presentations once they are online.
Kevin Goldsmith – Apportioning Monoliths
Kevin is dev lead on Spotify. He was working on Microsoft for many years and he compared they way of working in the 90’s in MS with their current methods on Spotify. Basically, the first was a huge falldown process with a 3 years production phase. In Spotify they have now a 2 week release cycle and they want to move it down to 1 week
He also explained how they moved from a team-per-layer structure to a team-per-functionality structure and how this allowed this to avoid inter-layer locks. This speech really got me, as I worked in a company performing translations for Microsoft in that time and I lived part of the issues he mentioned.
Sergi Martínez – Android Data Binding
That was mine. Android introduced data binding in I/O 2015 and is still in beta, but it could be a huge difference in the way we create UIs. There are still some things missing, like the two-way binding, which can be achieved at the moment with a lot of tricks. Data binding also allows using the MVVM pattern, as we use View Models to feed the data into views. I’ll write an article about that.
Diego Gómez Olivera – Booking Now Architectural Overview: Clean code for Android
Diego is an Android engineer at Booking Now and a GDE. He explained how they implemented the Clean Architecture pattern in their application. The communication of the different components is based on a Bus architecture to send commands and receive actions. They use tiny bus, as it was the most efficient in their benchmarks over GreenBus and Otto.
Svetlana Isakova – Kotlin on Android
Svetlana is part of team that created the Kotlin language in JetBrains. This speech was an introduction to the characteristics of the language and why they think it is a good language with a lower development effort needed. The second part was a brief introduction to the language itself introducing the changes and new elements of the version 2.0. Really nice good-looking language, but still not intended for production.
Denzil Ferreira – AWARE: mobile context instrumentation framework
Denzil is an investigator at the Oulu university in Sweden. He and his team work on the AWARE framework, an open-source library for Android responsible for getting information about the user context, not only from device sensors but from other data sources. The framework is really scalable via plug-ins and the backend allows to easily retrieve information and change what data is collected on the fly. It also simplifies a lot the use of sensors and, specially, collecting and sampling data. I’ve specifically ask for car sensors and he told me that plug-ins are not available yet, but he was tinkering with it (because he has a VW car) and they are easily integrable via plugins. More: http://www.awareframework.com/
Cesar Valiente – New permissions model on a “Nice” way
Cesar works at Wunderlist (now Microsoft) as Android dev and is a GDE. He introduced us in the new permissions feature in Android Marshmallow. He told us about the “official” way of using them, and how easy it works, but also discussed about how difficult is to integrate in an efficient way into a complex application. He shown us the full workflow and a proposal to integrate it into a project based on Clean Architecture
Savvas Dalkitsis – Lightweight Android lifecycle annotations
Savvas is an android dev at Shazam. We were introduced to a library Shazam published that allows to use Aspect Oriented Programming to Android UI. They moved from calling them aspects to traits. Basically, it allows to add an remove features from view objects (View, Activity, Fragment) with just annotations. Quite amazing library, for me the best example was adding the annotion @FABButton as annotation, and hop, the activity has a FAB button configured via annotation parameters. The library allows us to easily create new annotations that add new functionalities. Worth to check.
Marcin Kasz – Your beacons have been hacked! Why security Matters
Marcin from Kontakt.io discussed about the importance of security on a beacon implementation. We reviewed the most common types of attacks and some tricks to avoid them. My favorite was piggybanking, where a competitor uses your beacons to show you geolocated prices of products that are cheaper in their store.
James Nocentini – How to develop an offline-first native Android app
James works on the CoachBase project for Android. The speech was an explanation on how their system works. The great advantage of CouchDb for Android is that synchronization between server and client is made automatically in the background and can also be done between clients in P2P mode. We were introduced to several synchronization strategies and he made a nice demo of a website accessible by everybody showing a picture of a city and a text to introduce the name and how this picture was changed in every mobile through sync. I’m not sure if it’s valid for all cases, but could be interesting for a project like the Christmas parade.
Frederik Schweiger – Hello again, Android Wear!
Frederik is from the GDG Düsseldorf and a real enthusiast in Android Wear. He made a review of Wear basics and updated to the current state of the art. He also shown us some examples of apps he made like a remote door opener for his car. The good thing about this speech was that being the last one, a lot of people already left the convention and we had more an open discussion that a round of questions. Some interesting answers to my questions: despite having wifi, new wear doesn’t allow direct connection, is just for cloud notifications. Google fit is accessible from the watch, but only gets info obtained from the watch, not from the cloud and permission must be given from the phone before, and yes, the watch can fully access sensors.