A talk on which I try to explain some of the problems and concerns android developers (and mobile in general) have. That developing for android is not just drawing an UI to visualize data. As well as some libraries and suggestions by the community.
Mobile Constraints • Weak internet connection; - Internet is not always available nor always speedy; - Can fail in a middle of a request => inconsistent state
Mobile Constraints • Weak internet connection; - Internet is not always available nor always speedy; - Can fail in a middle of a request => inconsistent state • Limited mobile data and battery;
Mobile Constraints • Weak internet connection; - Internet is not always available nor always speedy; - Can fail in a middle of a request => inconsistent state • Limited mobile data and battery; • Divided Attention (must be objective);
Mobile Constraints • Weak internet connection; - Internet is not always available nor always speedy; - Can fail in a middle of a request => inconsistent state • Limited mobile data and battery; • Divided Attention (must be objective); • Handedness;
Mobile Constraints • Weak internet connection; - Internet is not always available nor always speedy; - Can fail in a middle of a request => inconsistent state • Limited mobile data and battery; • Divided Attention (must be objective); • Handedness; • Small screens.
Context awareness Who is your user? (Sign In API) • Email • name What is the user doing? (Activity API) • Walking • Running • Sleeping Where is your user? (Location API) • Location (latitude, longitude)
Context awareness Who is your user? (Sign In API) • Email • name What is the user doing? (Activity API) • Walking • Running • Sleeping Where is your user? (Location API) • Location (latitude, longitude) Who or what are they near? (Places API) • Places • People
Android in a nutshell • Activity - UI Screen in the application. • Broadcast Receiver - Subscribes OS events (ex: internet connection). • Service - Long running operations without a UI.
Android in a nutshell • Activity - UI Screen in the application. • Broadcast Receiver - Subscribes OS events (ex: internet connection). • Service - Long running operations without a UI. • Content Provider - Manages access to structured data.
App Architecture • Over the years, Google barely mentioned anything about android app architecture. • Aside from 2010’s Google IO talk by Virgil Dobjanschi on “Android REST client applications” which was very focused on android components like Content Providers (that are rarely needed), Services, Loaders (not suitable for network requests). • Last year on Android DevSummit, Google did a talk on android apps architecture; • This is a 5 years gap. • In between, the community came forward with different solutions.
App Architecture • Doesn’t matter for the user; • Architecture for the User Experience; • Offline or online use must be transparent to the user. • Pending web requests should be persisted until performed.
App Architecture • Doesn’t matter for the user; • Architecture for the User Experience; • Offline or online use must be transparent to the user. • Pending web requests should be persisted until performed. • The best apps are not only the most clean and simple to use but those that sync online with offline like magic. • Google Keep, Gmail, Pocket Casts, etc.
RxJava • “A library for composing asynchronous and event-based programs using observable sequences for the Java VM.” • Helps a lot with its threading API.
RxJava • “A library for composing asynchronous and event-based programs using observable sequences for the Java VM.” • Helps a lot with its threading API. • Contains operators to transform, filter and convert multiple sets of data;
RxJava • “A library for composing asynchronous and event-based programs using observable sequences for the Java VM.” • Helps a lot with its threading API. • Contains operators to transform, filter and convert multiple sets of data; • Handles errors in a clean and organised way;
RxJava • “A library for composing asynchronous and event-based programs using observable sequences for the Java VM.” • Helps a lot with its threading API. • Contains operators to transform, filter and convert multiple sets of data; • Handles errors in a clean and organised way; • RxAndroid adds a specific scheduler for the UI thread;
RxJava • “A library for composing asynchronous and event-based programs using observable sequences for the Java VM.” • Helps a lot with its threading API. • Contains operators to transform, filter and convert multiple sets of data; • Handles errors in a clean and organised way; • RxAndroid adds a specific scheduler for the UI thread; • RxBindings adds RxJava binding APIs for Android UI widgets from the platform and support libraries.
RxJava + RxAndroid • In android, view related operations (inflation, drawing) must be done on the UI thread. Everything else should be done on a worker thread. • RxAndroid adds specific Android Scheduler for UI Thread. mService.getPostById(postId) .subscribeOn(Schedulers.io()) .map(new Func1() { @Override public PostView call(Post post) { return mPostMapper.transform(post); } }) .observeOn(AndroidSchedulers.mainThread()) .subscribe(new Subscriber() { ... @Override public void onNext(PostView postView) { mView.onPostLoaded(postView); } });
RxJava + RxAndroid • In android, view related operations (inflation, drawing) must be done on the UI thread. Everything else should be done on a worker thread. • RxAndroid adds specific Android Scheduler for UI Thread. mService.getPostById(postId) .subscribeOn(Schedulers.io()) .map(new Func1() { @Override public PostView call(Post post) { return mPostMapper.transform(post); } }) .observeOn(AndroidSchedulers.mainThread()) .subscribe(new Subscriber() { ... @Override public void onNext(PostView postView) { mView.onPostLoaded(postView); } });
RxJava + RxAndroid • In android, view related operations (inflation, drawing) must be done on the UI thread. Everything else should be done on a worker thread. • RxAndroid adds specific Android Scheduler for UI Thread. mService.getPostById(postId) .subscribeOn(Schedulers.io()) .map(new Func1() { @Override public PostView call(Post post) { return mPostMapper.transform(post); } }) .observeOn(AndroidSchedulers.mainThread()) .subscribe(new Subscriber() { ... @Override public void onNext(PostView postView) { mView.onPostLoaded(postView); } });
App Architecture • Monolithic solutions are good for demo purposes but many companies still do it. “Testing in android is not so simple and clear as in other platforms, so we don’t do it” - Someone.
Testing • For the data (repositories) layer: • Roboletric 3 • And for the presentation layer: • Espresso • Android Instrumentation Testing • MonkeyRunner • Mockito and JUnit can also be used in the data layer as well as the domain layer.
Third party libraries There are many libraries for different purposes but lets focus only on these topics: • Communication with Web Api’s • Requests persistence • Image Loading • Structured Data
Retrofit Type-safe HTTP client for Android and Java. 1 - Turn your http api into a java interface: public interface GithubApi { @GET("group/{id}/users") Call> groupList(@Path("id") int groupId, @Query("sort") String sort); } 2 - Create a retrofit instance: Retrofit retrofit = new Retrofit.Builder() .baseUrl("https://api.github.com") .addConverterFactory(GsonConverterFactory.create()) .build(); 3 - Instantiate it and perform the request:
GithubService service = retrofit.create(GithubService.class); Call> response = service.groupList(10,"asc");
Requests persistence Just like mentioned before, requests should be persisted until completed. We should prevent the loss of data, in cases like when we run out of battery, the system crashes or the app closes. • Tape - by Square • Android Priority Job Queue - Yigit Boyar
Glide Loading images over the network is harder than it seems, since we should: • Cache images (since downloads are costly) • Load them as fast as possible • With little memory footprint • UI Lifecycle aware Fortunately Glide does all of this (and more), through a simple api: Glide .with(myActivity) .load("www.images.com/image.png") .centerCrop() .placeholder(R.drawable.loading_spinner) .crossFade() .into(myImageView);
Structured Data • SqlBrite - Wrapper for Sqlite with reactive stream semantics (RxJava). Apps still need to implement SQL logic. • ORM - (ActiveAndroid, OrmLite, SqlBriteDAO, etc) add an abstraction over SQL. • RealmDb - Closed source c++ database with java bindings. Simple to use and generally fast.
Screen sizes Android iOS Source: Open Signal 2015 - “…from almost 10 million OpenSignal users. In this graphic we are showing physical screen size, not size in pixel…”
Svg support Replaces multiple png files for one single xml SVG (single vector graphics). • Available only for Android 5.0 (api 21) • Since February 24th available on Android 2.1 (api 7) !!
Design Library • With Android 5.0 a new design language was introduced to the Android experience. • Days after the announcement, Google provided a spec sheet on how to design android applications.
Design Library • With Android 5.0 a new design language was introduced to the Android experience. • Days after the announcement, Google provided a spec sheet on how to design android applications. • However, implementing some of those behaviours and components was usually very hard.
Design Library • With Android 5.0 a new design language was introduced to the Android experience. • Days after the announcement, Google provided a spec sheet on how to design android applications. • However, implementing some of those behaviours and components was usually very hard. • Almost a year later, Google announced the Design Library to help developers achieve a consistent visual experience in a easier way.
Avoid • Overdraw • Allocations in critical parts • Deep view Hierarchies • RelativeLayout does two measure passes. It’s usually negligible but with nested complex RelativeLayouts, could be a problem. • Avoid nesting weights on Linear layouts
Falcon Pro case • On Falcon’s case, the problem was caused by setting the alpha property on the small little circles under the title. • This means there are more reasons for performance problems than the previously mentioned. GOOD BAD
Falcon Pro case • On Falcon’s case, the problem was caused by setting the alpha property on the small little circles under the title. • This means there are more reasons for performance problems than the previously mentioned. • Android doesn’t like the blur effect either. :( GOOD BAD
fmendes6
77web
kazutan
hitoshi_a0
fabpot
akatsuki174
mski_iksm
dicoding
iwaken71
manfredsteyer
codehex
fendo181
mojombo
davidbonilla
cherdarchuk
garrettdimon
samanthasiow
reverentgeek
dougneiner
jrom
smashingmag
productmarketing
keithpitt
brianwarren