Android Memo 5 — Maybe it’s only me so careless. But here is a warning about `asLiveData` extension. val hotData: LiveData<Int> = Model.sharedFlow.onEach { Log.d("MY_FLOW", "hot flow on each: $it") }.asLiveData() STR 1. Observe hotData from a fragment. Usually we do this from onViewCreated 2. Go to another fragment and stay there for 5 seconds (default timeout) 3. Go back to initial fragment and observe hotData again. 4. See in logs, that onEach clause runs again.

or don’t trust your API — Motivation 90% of our work is to present to user data, that we get from REST API. While it doesn’t seem rocket science, some responses could be so unpredictable, that the next app crash would make you facepalm. The very fresh example that I got: "set": [ {}, {}, {} ] …

TL;DR When creating a compound view, based on a ViewGroup (layout), don't forget about: View and ViewGroup doesn’t support enabled/disabled or checked/unchecked state by default; Such a state should be propagated to every child; Again, if that child doesn’t support that state — make it; Custom attributes are your friends; Examples are here: IndicatorButton…

You're creating one more awesome button. Nice guy designer provided you with colors for released and pressed states. A selector is your obvious choice: And you can enjoy the result:

At first, I was going to write a readme for my boilerplate repository. In the process of writing, I understood, that I’m getting not just a repo description, but some kind of essay. It summarises my experience in two Android development aspects: application architecture and testing. I decided to share…

Two years ago I created a document with checklist. What should you do before publishing your Android application. I’m going to copy it here as is. Let’s check, if it’s still useful. Read before starting: How I Develop Mobile Web Apps How to create settings. Read this tutors: Design Develop …

At least if you hide keyboard by yourself I faced this trouble. When you replace view on your activity and you have EditText with anopened keyboard, sometimes you get exception and crash: java.lang.NullPointerException: Attempt to invoke interface method 'void android.view.inputmethod.InputConnection.closeConnection()' on a null object reference at android.view.inputmethod.InputConnectionWrapper.closeConnection(InputConnectionWrapper.java:270

Motivation The Navigation Architecture Component was presented to a community not so long ago. The idea is simple: create an orientated graph, where screens are vertices and transitions are edges. In the nutshell, there is single navigation engine, router you can say. We’ve already seen this in the bunch of libraries…

Every Android developer faces this problem — how to survive a screen rotation. Specifically — how to solve this in context of MVP. There are a lot of solutions. I like one with loaders. And here is another approach with Dagger 2, that uses one powerful property of Activity. A…