Librerie su Android: come non reinventare la ruota @ whymca 2012

•Télécharger en tant que KEY, PDF•

1 j'aime•1,609 vues

Nei progetti J2EE siamo abituati a usare decine di librerie esterne, sia per classi di utilità sia per framework per strutturare meglio il codice. Come è messo Android da questo punto di vista? Nell'ultimo anno sono nati molti progetti interessanti (quasi tutti open source) che stanno portando un gran numero di librerie che permettono di non reinventare tutte le volte la ruota. In questo talk vedremo le principali librerie utilizzabili in un progetto Android evidenziando pregi e difetti di ognuna. Tramite una applicazione di esempio di librerie che permettono di evitare problemi di frammentazione (Android Compatibility Library e ActionBarSherlock), di quelle che mettono a disposizione nuovi componenti (GreedDroid, ViewPagerIndicator) e di quelle che cambiano radicalmente il modo di sviluppare una app (aQuery, Spring Mobile, AndroidAnnotations).

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Librerie su Android: come non reinventare la ruota @ whymca 2012

Contenu connexe

En vedette

What’s the best testing framework on Android? Espresso or Robotium? Robolectric or a plain JUnit test? The reason why many developers don’t write tests is not due to the testing libraries but because of the low testability of the Android code. In this talk we’ll see, thanks to a practical example, how to use Dependency Injection (using Dagger) and the Model View Presenter pattern to write a testable Android application.

Testable Android Apps DroidCon Italy 2015

Testable Android Apps DroidCon Italy 2015

Testable Android Apps DroidCon Italy 2015

Testable Android Apps using data binding and MVVM

Testable Android Apps using data binding and MVVM

Testable Android Apps using data binding and MVVM

Android App Development, Creare la nostra prima app

Android App Development, Creare la nostra prima app

Android App Development, Creare la nostra prima app

Introduction to Retrofit and RxJava

Introduction to Retrofit and RxJava

Introduction to Retrofit and RxJava

The Data Binding framework was one of Google’s announcements at I/O 2015, it’s a big change in the code organization of an Android app. Some developers are sceptical about this framework but, if used in the “right way”, it’s very powerful and it allows to remove a lot of redundant boilerplate code from activities and fragments. In this talk we’ll start from the Data Binding basic concepts and then we’ll see how to use it to improve the architecture of a typical Android application applying the Model View ViewModel pattern. Using this pattern you need to write less code to create an app that can be easily tested using JVM and instrumentation tests.

Android Data Binding in action using MVVM pattern - droidconUK

Android Data Binding in action using MVVM pattern - droidconUK

Android Data Binding in action using MVVM pattern - droidconUK

The Data Binding framework was one of Google’s announcements at I/O 2015, it’s a big change in the code organization of an Android app. Some developers are sceptical about this framework but, if used in the “right way”, it’s very powerful and it allows to remove a lot of redundant boilerplate code from activities and fragments. In this talk we’ll start from the Data Binding basic concepts and then we’ll see how to use it to improve the architecture of a typical Android application applying the Model View ViewModel pattern. Using this pattern you need to write less code to create an app that can be easily tested using JVM and instrumentation tests.

Data Binding in Action using MVVM pattern

Data Binding in Action using MVVM pattern

Data Binding in Action using MVVM pattern

MVVM with DataBinding on android

MVVM with DataBinding on android

MVVM with DataBinding on android

Rodrigo Bressan

En vedette (7)

Testable Android Apps DroidCon Italy 2015

Testable Android Apps DroidCon Italy 2015

Testable Android Apps DroidCon Italy 2015

Testable Android Apps using data binding and MVVM

Testable Android Apps using data binding and MVVM

Testable Android Apps using data binding and MVVM

Android App Development, Creare la nostra prima app

Android App Development, Creare la nostra prima app

Android App Development, Creare la nostra prima app

Introduction to Retrofit and RxJava

Introduction to Retrofit and RxJava

Introduction to Retrofit and RxJava

Android Data Binding in action using MVVM pattern - droidconUK

Android Data Binding in action using MVVM pattern - droidconUK

Android Data Binding in action using MVVM pattern - droidconUK

Data Binding in Action using MVVM pattern

Data Binding in Action using MVVM pattern

Data Binding in Action using MVVM pattern

MVVM with DataBinding on android

MVVM with DataBinding on android

MVVM with DataBinding on android

Plus de Fabio Collini

Compose is stable, it's time to integrate it into our apps! But it can be harder than expected and there are some questions to answer. Can the same architecture of a View-based app be reused or should we change it? Should the Compose code be aware of the architecture at all? And should the non UI code be changed to start using Compose? What can be replaced with a Composable, only the layouts or also something else? Probably the best answer to all these questions is “it depends”, in this talk we’ll see some reasons and how to leverage Compose and the other tools to create a good architecture. Compose is more than just a UI framework and it can seem appealing to use it in a big portion of an app, a good architecture can be useful to limit this portion and use it only when necessary.

Architectures in the compose world

Architectures in the compose world

Architectures in the compose world

Modularizing a project is never easy, a lot of files to move and the dependencies between them is not always what we expect. Then the Dagger configuration used in a single module project often doesn't scale well to a multi module project. Hilt is opinionated about the configuration to use (we don't need to argue anymore about using component dependencies or subcomponents!) and this configuration works perfectly even in a multi module project. In this talk we'll see first an introduction to Hilt and a comparison with Dagger to understand why it's easier to configure. Then we'll see how to leverage it in a multi module project (both in a standard layered architecture and in a Clean Architecture that uses the Dependency Inversion) to improve build speed and code testability. Spoiler alert: using sample apps that include a single feature in the app helps a lot!

Using hilt in a modularized project

Using hilt in a modularized project

Using hilt in a modularized project

Using Kotlin coroutines it’s really easy to execute a task in a background thread and update the UI based on the result. Just enter the coroutine world using the launch method and then change thread using withContext. It’s even simpler if the task is an http call (thanks to coroutines support in retrofit) or a database query (thanks to Room). The final code is the same we’d use to execute synchronous code. But coroutines are more than just a tool to switch thread, we can use them to execute tasks in parallel. The code is still really easy to read but sometimes it can be difficult to write: we need to pay attention to many aspects (like nested scopes, exceptions and dispatchers). In this talk we’ll see how to leverage the coroutines library to manage parallelism, from the basic concepts to some advanced example.

Managing parallelism using coroutines

Managing parallelism using coroutines

Managing parallelism using coroutines

The lazy delegate is probably the most famous Kotlin delegate, it’s easy to use and can be really useful. However delegation is a concept that can be used in many other ways in Kotlin. A delegate can be declared at two levels: * a delegated property allows changing the way the property is managed * an interface can be implemented delegating the methods to another object In this talk we’ll see many practical examples to show how to leverage standard delegates and how to create new ones to improve the quality of our code and to avoid duplication.

Kotlin Delegates in practice - Kotlin community conf

Kotlin Delegates in practice - Kotlin community conf

Kotlin Delegates in practice - Kotlin community conf

The lazy delegate is probably the most famous Kotlin delegate, it’s easy to use and can be really useful. However delegation is a concept that can be used in many other ways in Kotlin. A delegate can be declared at two levels: * a delegated property allows changing the way the property is managed * an interface can be implemented delegating the methods to another object In this talk we’ll see many practical examples to show how to leverage standard delegates and how to create new ones to improve the quality of our code and to avoid duplication.

Kotlin delegates in practice - Kotlin Everywhere Stockholm

Kotlin delegates in practice - Kotlin Everywhere Stockholm

Kotlin delegates in practice - Kotlin Everywhere Stockholm

Clean Architecture and app modularization are often used together to achieve a better code structure and a faster build time. But how can we use Dagger in an app structured in that way? Can we use subcomponents (with or without Dagger Android) or are component dependencies enough? In this talk we’ll see how to leverage Dagger to organize the dependencies in a multi-module project with particular attention to testing and decoupling. The examples will be both in a standard layered architecture and in a Clean Architecture where the Dependency Inversion increases the overall structure but can complicate the Dagger code.

Using Dagger in a Clean Architecture project

Using Dagger in a Clean Architecture project

Using Dagger in a Clean Architecture project

The Clean Architecture has been formalized by Robert C. Martin in 2012, it's quite new even if it's based on the SOLID principles (presented for the first time in early 2000). The biggest benefit that we get using this architecture is the code testability, indeed it separates the application code from the code connected to external factor (that usually is more difficult to test). In this talk we'll see a practical example of how to apply the SOLID principle, in particular, the dependency inversion.

Solid principles in practice the clean architecture - Droidcon Italy

Solid principles in practice the clean architecture - Droidcon Italy

Solid principles in practice the clean architecture - Droidcon Italy

The Clean Architecture has been formalized by Robert C. Martin in 2012, it's quite new even if it's based on the SOLID principles (presented for the first time in early 2000). The biggest benefit that we get using this architecture is the code testability, indeed it separates the application code from the code connected to external factor (that usually is more difficult to test). In this talk we'll see a practical example of how to apply the SOLID principle, in particular, the dependency inversion.

SOLID principles in practice: the Clean Architecture - Devfest Emila Romagna

SOLID principles in practice: the Clean Architecture - Devfest Emila Romagna

SOLID principles in practice: the Clean Architecture - Devfest Emila Romagna

The Clean Architecture has been formalized by Robert C. Martin in 2012, it's quite new even if it's based on the SOLID principles (presented for the first time in early 2000). The biggest benefit that we get using this architecture is the code testability, indeed it separates the application code from the code connected to external factor (that usually is more difficult to test). In this talk we'll see a practical example of how to apply the SOLID principle, in particular, the dependency inversion.

SOLID principles in practice: the Clean Architecture

SOLID principles in practice: the Clean Architecture

SOLID principles in practice: the Clean Architecture

Kotlin is a first-class language for Android development since Google I/O 2017. And it’s here to stay! Thanks to Android Studio it’s really easy to introduce Kotlin in an existing project, the configuration is trivial and then we can convert Java classes to Kotlin using a Alt+Shift+Cmd+K. But the new syntax is the just beginning, using Kotlin we can improve our code making it more readable and simpler to write. In this talk we’ll see how to use some Kotlin features (for example data classes, collections, coroutines and delegates) to simplify Android development comparing the code with the equivalent “modern” Java code. It’s not fair to compare Kotlin code with plain Java 6 code so the Java examples will use lambdas and some external libraries like RxJava and AutoValue.

From Java to Kotlin beyond alt+shift+cmd+k - Kotlin Community Conf Milan

From Java to Kotlin beyond alt+shift+cmd+k - Kotlin Community Conf Milan

From Java to Kotlin beyond alt+shift+cmd+k - Kotlin Community Conf Milan

It’s never easy to write async code but luckily there are many libraries to manage asynchronicity without adding too much complexity. In the last years RxJava and the other ReactiveX libraries have been very popular but lately there is a new way to manage async code in Kotlin: the coroutines. In this talk we’ll pros and cons of there two approaches and how to leverage them to simplify asynchronous code on Android. Do they solve the same problem? Can we use them together? Which one can be used to write functional code? How can we use them effectively in Android development? Spoiler alert: They are both great! In this talk we’ll see how to solve common problems using RxJava or Coroutines, starting from basic concepts (for example the Retrofit support and how to cancel a task) to some more advanced (like threading, error management and how to combine multiple tasks). All example of the talk are available on this repository: https://github.com/fabioCollini/RxJavaVsCoroutines

Async code on kotlin: rx java or/and coroutines - Kotlin Night Turin

Async code on kotlin: rx java or/and coroutines - Kotlin Night Turin

Async code on kotlin: rx java or/and coroutines - Kotlin Night Turin

Recap Google I/O 2018

Recap Google I/O 2018

Recap Google I/O 2018

Kotlin is a first-class language for Android development since Google I/O 2017. And it’s here to stay! Thanks to Android Studio it’s really easy to introduce Kotlin in an existing project, the configuration is trivial and then we can convert Java classes to Kotlin using a Alt+Shift+Cmd+K. But the new syntax is the just beginning, using Kotlin we can improve our code making it more readable and simpler to write. In this talk we’ll see how to use some Kotlin features (for example data classes, collections, coroutines and delegates) to simplify Android development comparing the code with the equivalent “modern” Java code. It’s not fair to compare Kotlin code with plain Java 6 code so the Java examples will use lambdas and some external libraries like RxJava and AutoValue.

From java to kotlin beyond alt+shift+cmd+k - Droidcon italy

From java to kotlin beyond alt+shift+cmd+k - Droidcon italy

From java to kotlin beyond alt+shift+cmd+k - Droidcon italy

Kotlin is a first-class language for Android development since Google I/O 2017. And it’s here to stay! Thanks to Android Studio it’s really easy to introduce Kotlin in an existing project, the configuration is trivial and then we can convert Java classes to Kotlin using a Alt+Shift+Cmd+K. But the new syntax is the just beginning, using Kotlin we can improve our code making it more readable and simpler to write. In this talk we’ll see how to use some Kotlin features (for example data classes, collections, coroutines and delegates) to simplify Android development comparing the code with the equivalent “modern” Java code. It’s not fair to compare Kotlin code with plain Java 6 code so the Java examples will use lambdas and some external libraries like RxJava and AutoValue.

From java to kotlin beyond alt+shift+cmd+k

From java to kotlin beyond alt+shift+cmd+k

From java to kotlin beyond alt+shift+cmd+k

Writing reliable tests is not easy for many reasons, especially when asynchronous code is involved. Some libraries can be used to create a testable architecture (for example Dagger and RxJava) and to simplify testing (Mockito, AssertJ and DaggerMock). In this talk you'll learn how to write JVM and Espresso tests with particular attention on how to replace real objects with mocks and how to test asynchronous RxJava code. In this talk, you will also explore: how to take advantage of Mockito and other libraries to write good JVM and Espresso tests in both Java and Kotlin how to use DaggerMock (an open source library available on github to avoid boilerplate code in tests how to test asynchronous RxJava code using a JVM test

Testing Android apps based on Dagger and RxJava Droidcon UK

Testing Android apps based on Dagger and RxJava Droidcon UK

Testing Android apps based on Dagger and RxJava Droidcon UK

Intro to Retrofit 2 and RxJava2

Intro to Retrofit 2 and RxJava2

Intro to Retrofit 2 and RxJava2

In this talk, you will learn: how to take advantage of Mockito and other libraries to write good JVM and Espresso tests how to use DaggerMock (an open source library available on github https://github.com/fabioCollini/DaggerMock) to avoid boilerplate code in tests how to test asynchronous RxJava code using a JVM test Writing reliable tests is not easy for many reasons, especially when asynchronous code is involved. Some libraries can be used to create a testable architecture (for example Dagger and RxJava) and to simplify testing (Mockito, AssertJ and DaggerMock). In this talk we’ll see how to write JVM and Espresso tests with particular attention on how to replace real objects with mocks and how to test asynchronous RxJava code.

Testing Android apps based on Dagger and RxJava

Testing Android apps based on Dagger and RxJava

Testing Android apps based on Dagger and RxJava

Plus de Fabio Collini (17)

Architectures in the compose world

Architectures in the compose world

Architectures in the compose world

Using hilt in a modularized project

Using hilt in a modularized project

Using hilt in a modularized project

Managing parallelism using coroutines

Managing parallelism using coroutines

Managing parallelism using coroutines

Kotlin Delegates in practice - Kotlin community conf

Kotlin Delegates in practice - Kotlin community conf

Kotlin Delegates in practice - Kotlin community conf

Kotlin delegates in practice - Kotlin Everywhere Stockholm

Kotlin delegates in practice - Kotlin Everywhere Stockholm

Kotlin delegates in practice - Kotlin Everywhere Stockholm

Using Dagger in a Clean Architecture project

Using Dagger in a Clean Architecture project

Using Dagger in a Clean Architecture project

Solid principles in practice the clean architecture - Droidcon Italy

Solid principles in practice the clean architecture - Droidcon Italy

Solid principles in practice the clean architecture - Droidcon Italy

SOLID principles in practice: the Clean Architecture - Devfest Emila Romagna

SOLID principles in practice: the Clean Architecture - Devfest Emila Romagna

SOLID principles in practice: the Clean Architecture - Devfest Emila Romagna

SOLID principles in practice: the Clean Architecture

SOLID principles in practice: the Clean Architecture

SOLID principles in practice: the Clean Architecture

From Java to Kotlin beyond alt+shift+cmd+k - Kotlin Community Conf Milan

From Java to Kotlin beyond alt+shift+cmd+k - Kotlin Community Conf Milan

From Java to Kotlin beyond alt+shift+cmd+k - Kotlin Community Conf Milan

Async code on kotlin: rx java or/and coroutines - Kotlin Night Turin

Async code on kotlin: rx java or/and coroutines - Kotlin Night Turin

Async code on kotlin: rx java or/and coroutines - Kotlin Night Turin

Recap Google I/O 2018

Recap Google I/O 2018

Recap Google I/O 2018

From java to kotlin beyond alt+shift+cmd+k - Droidcon italy

From java to kotlin beyond alt+shift+cmd+k - Droidcon italy

From java to kotlin beyond alt+shift+cmd+k - Droidcon italy

From java to kotlin beyond alt+shift+cmd+k

From java to kotlin beyond alt+shift+cmd+k

From java to kotlin beyond alt+shift+cmd+k

Testing Android apps based on Dagger and RxJava Droidcon UK

Testing Android apps based on Dagger and RxJava Droidcon UK

Testing Android apps based on Dagger and RxJava Droidcon UK

Intro to Retrofit 2 and RxJava2

Intro to Retrofit 2 and RxJava2

Intro to Retrofit 2 and RxJava2

Testing Android apps based on Dagger and RxJava

Testing Android apps based on Dagger and RxJava

Testing Android apps based on Dagger and RxJava

Notes de l'éditeur