Please log in to watch this conference skillscast.
The Android framework offers a lot of flexibility when it comes to defining how to organize and architect an Android app. This freedom, whilst very valuable, can also result in apps with large classes, inconsistent naming and architectures (or lack of) that can make testing, maintaining and extending difficult. There are many different options, following different patterns and embracing different programming paradigms.
Android Architecture Blueprints is meant to demonstrate possible ways to help with these common problems. In this project we offer the same application implemented using different architectural concepts and tools.
This talk will explore the motivations, findings and numbers extracted from these various approaches which will help choosing which one works best for you and your team.
YOU MAY ALSO LIKE:
- SOLID principles for coding in Java (in London on 31st January 2017)
- Testing in Java (in London on 23rd February 2017)
- Gojko Adzic's Specification by Example: From User Stories to Acceptance Tests (in London on 9th - 10th March 2017)
- Agile Testing & BDD eXchange 2017 (in London on 9th - 10th November 2017)
Android Architecture Blueprints
Jose Alcérreca is a Developer Programs Engineer at Google where he works closely with the Android Tools and APIs teams to improve the testing experience for Android developers and help them produce awesome, solid apps.
David is an Android Software Engineer at Help Scout and a Google Developer Expert for Android. He's actively involved in the Android community, helping at the London Android User Group and has been developing with the Android platform since 2009.