TBA

TBA

For 10 years Groovy has dramatically improved the productivity of Java developers on the desktop. With unique like closures builders AST transformations traits optional static compilation and many more Groovy turned out to be a very competitive language on the JVM. Compared to other JVM languages Groovy has the major advantage of being totally Java-friendly both in terms of syntax and interpretability. But during those years what happened on the mobile world? In particular Android developers are used to develop applications in Java so why Groovy a JVM language wouldn't be usable for Android development too? Can we ease the pain of Android developers too?

TBA

We cannot interact with our everyday life in the same way we interact with a desktop computer. Technology shouldn't require all of our attention just some of it and only when necessary. How can our devices take advantage of location proximity and haptics to help improve our lives instead of get in the way? This presentation covers the history of calm technology wearable computing and how designers can make apps “ambient” while respecting privacy and security. We'll look at ambient notifications compressing information into other senses and designing for the least amount of cognitive overhead.

TBA

Open-sourced libraries by Square -the talk shows how and why we created these things.

TBA

TBA

Using two specific case studies as well as learnings from additional projects I walk attendees through the weekly cadence that we use at Carbon Five during product development. This methodology and its activities establish a sustainable culture of integrated and invested teams that are able to communicate across disciplines in a meaningful way.The result of creating this type of culture via cadence allows our teams to put new features in front of users each week for validation and hence move the product closer to its market fit faster.

User authentication in mobile applications is a very common and integral use case. Implementing regular passwords is an easy solution for developers but comes with several pitfalls that impair user experience like (re-)entering passwords the need to create a new unique password or even just the input of personal data on a flaky keyboard while registering a new account.

In this talk the security flaws and UX implications of passwords will be discussed and highlighted which different techniques exist that are able to offer a more mobile friendly flow. Highlighting authorization and authentication techniques like OAuth OpenID Connect and even hardware features like Bluetooth Low Energy this talk will be interesting for anyone who's facing a situation where creating and storing user accounts matters.

TBA

TBA

TBA

This talk will introduce the new security features added in Android 5.0 andwill briefly describe their platform integration and internal implementation.

Features to be covered:

• Full disk encryption
• Verified boot and block-based OTAs
• SELinux policy changes
• Smart Lock (trust agents)
• Multi-user changes and managed profiles
• Device management API changes
• Cryptographic provider and SSL changes

TBA

User Experience design is an important aspect in software development. There is often times a linear process designers follow to create an overall User Experience. What guides the designer's decisions outside of user testing and software requirements is a set of intuition factors. This talk will cover Intuition Factors used when designing software with hardware components.

The Continuous Delivery book was released in 2010. Described as the most impactful post-Agile practice it has changed the way we think about developing software. It forced us to start thinking of software being "done" to mean released.  With more features getting to done sooner CD practices have enabled us to get early feedback from users and taught us a lot about testing monitoring and automating our delivery along the way. But mobile development has often been left behind. Or has it?

From the time of the first iPhone in 2008 mobile development has changed dramatically. Rapid improvements and added features in GPS Touch ID and facial recognition have caused the quality of mobile applications to improve.

In this talk we will cover how in a post Continuous Delivery world we can continuously adapt and improve in many different aspects of mobile development. Covering areas like usability security and performance. The continuous feedback loop of rapidly delivering mobile apps and putting those in the hands of customers gives us the ability to learn adapt and make more advanced applications.

Apple has introduced “a better language” for iOS developers. But what options do we have for Android? Surely Kotlin should be under consideration! Android Studio is now based on Intellij Idea the “native” environment for Kotlin.
Kotlin is a modern language for industry. It can help you reduce the amount of code you write for Android applications and at the same time make it readable and more maintainable. In this session we're going to see how certain constructs and DSL's can be used to make Android more enjoyable.

As engineers we know that having a maintainable codebase is important and that tasks like paying down technical debt are essential to minimizing the cost of future change.But that minimization function varies a lot based on the project. Planning for change in a throwaway prototype looks very different than the maintenance of long-term infrastructure. Practices that work great for a solo engineer or a team of 2-3 engineers fall apart when introduced to a larger team and vice versa. Even more worrying we frequently don't know where on this spectrum our codebase will end up.
Today's 48-hour hackathon project can easily become 5-years-from-now's legacy code and the perfect architecture carefully crafted over the course of a year could be thrown out tomorrow because of a shift in business needs.
How do we accomodate all of this while still shipping new code? This talk will explore strategies for thinking about your codebase and engineering process so that your code can stay maintainable even as the definition of "maintainable" shifts over time.

TBA

The Continuous Delivery book was released in 2010. Described as the most impactful post-Agile practice it has changed the way we think about developing software. It forced us to start thinking of software being "done" to mean released.  With more features getting to done sooner CD practices have enabled us to get early feedback from users and taught us a lot about testing monitoring and automating our delivery along the way. But mobile development has often been left behind. Or has it?

From the time of the first iPhone in 2008 mobile development has changed dramatically. Rapid improvements and added features in GPS Touch ID and facial recognition have caused the quality of mobile applications to improve.

In this talk we will cover how in a post Continuous Delivery world we can continuously adapt and improve in many different aspects of mobile development. Covering areas like usability security and performance. The continuous feedback loop of rapidly delivering mobile apps and putting those in the hands of customers gives us the ability to learn adapt and make more advanced applications.

TwoWayView is an open source library that extends the new RecyclerView framework on Android to make your life easier as an app developer. In this talk you'll learn how to use TwoWayView in your projects and how to implement your own layout managers for RecyclerView using TwoWayView's simple API.

TBA

The world is full of pretty products that aren't very functional. While customers may be initially attracted to those shiny objects in the long run if a product is an empty shell it will not last. An useless product that looks great is a failure. And the failure belongs as much to the designer as anyone else.

If you design hoping people will notice how awesome your design is you will be disappointed. Or you will build something that isn’t useful. The best design decisions are the ones people don't notice. The subtle choices that contribute to making the product easier to use better at it’s purpose. If you do your job well all but the most discerning customers won't be able to articulate why they like your product more. They just will. 

In this talk we'll take a look at examples of products that are designed well not because of how they look but how they work. The small decisions made along the way that contribute to success. We'll also talk about avoiding the common pitfalls of design for design's sake. Over-abundant animations the obsession with "clean" interfaces that lack function making our products so opinionated that only we like them—all the things we designers tend to fawn over that don't matter much to most people. Finally we'll talk about balancing the need to serve our customers' best interests vs. our own needs to survive as a company. You can't build products for people after all if you go out of business. 

Successful design solves problems. Well designed products meet needs. Focus your energy there and you will build something truly great.

Designers want to make user interfaces beautiful and distinctive developers must make them function and end-users need them to accomplish tasks efficiently.  Why are these three goals often at odds?  How can we get designers and developers to understand and support each other's missions and still give the users what they really need?

Apps are getting larger pushed by ever increasing user expectations. Social media maps advertisements... As a developer you may add a few libraries and before you know it your app is exceeding the constraints of the Android platform. In this presentation I will discuss the main problems and some solutions. ProGuard the bytecode optimizer and obfuscator in the Android SDK is an obvious first step. I will show some optimized configurations that can help you to reduce the size of common libraries. If ProGuard isn't sufficient you may have to resort to more drastic techniques such as dex splitting. I'll discuss some techniques and their implications. I'll also introduce the new dex splitting feature of our software DexGuard.

Adam will talk about how Facebook completely rearchitected the model layer of their iOS app to use immutable models and a data flow architecture.
This required a major shift in thinking about how models work and he’ll share how they dealt with the challenges of applying this architecture shift while News Feed was still under active development.

Android finally has established design guidelines and widely used UI design patterns. Android users understand functionality of components like the navigation drawer action bar sharing and many more. However the guidelines are just that guidelines not rules.
All Android apps should not look alike but neither should they all reinvent all the controls. In this presentation I will take a deep dive into details of the common design patterns and how they can be customised without compromising usability.
I want to help developers and designers alike to understand how to correctly use Android UI design patterns.

The internet of things is built around sensors without sensors we don’t know what goes on and we can’t tell our software to make rational choices based on the analytics of this data but building our own sensors are not always practical or cost efficient when there are numerous of the shelf solution that could do the same thing if we could only access their data! This talk demonstrates how to reverse engineer standard sensor wireless protocols from weather stations movement sensors and more to use for your own designs!

TBA

Imagine you change your code and see the results immediately no need to wait for your machine to recompile whole project and put in on device instead of working 8h you’d work 4h and achieve same results sounds good?
What could you achieve in those extra 4h you just got ? Either bring even more polish to your great apps or have more time for your family and life.

Let’s talk about using advanced techniques to maximise your development speed Playgrounds for Objective-C and how you can use runtime / code injection to get most out of your time.

Making a well designed Android application is not enough anymore it has to be awesome. This talk will show you how to change a good design to a awesome design to it will benefit your app.

In the era of smartphones and wearable devices anticipating the user's need from your application in his/her current context is becoming a requirement. We are moving towards context aware micro interactions à la Google Now. In this talk I will dive deep into the following topics:

• Harnessing the power of the latest iOS Android and Wearable APIs to collect and recognize significant context data across four dimensions:
• Time (calendar reminders timezones)
• Location (GPS places of interest events)
• Proximity (bluetooth/P2P/WiFi based nearby objects nearby devices nearby friends)
• Fitness tracking (movement heart rate sleep patterns)
• On significant context recognition scheduling of immediate or future actions to anticipate user requirements
• Real world case study of the LinkedIn Connected app which applies the above techniques for pre-meeting intelligent notifications for a large user base

TBA

Topics covered:

• iOS security mechanisms
• Understanding security from attacker perspective
• One more time about jailbreak and reverse engineering (tools detection and anti-detection)
• Best practices with real code examples
• Advanced security (iOS kernel syscalls)

TBA