Without using any frameworks like RxJava or managing Threads
This article is part of Today I Learned series and was originally posted at my TIL Github Repository and my website at wajahatkarim.com
Today, when I was working on a project, so I had a situation where I had to perform a very tiny operation in background in Android. I had lots of ideas such as AsyncTask or Thread or using such powerful framework like RxJava or using new APIs such as JobDispatcher or WorkManager etc. You can read about these options in this good article by Ali Muzaffar.
But my major concern was that my requirement was a very simple and little one. I wanted to get address from the location in form of latitude and longitude. And I wanted to do it in background along with showing ProgressBar and stuff. You can check the below GIF image as the result of what I did.
I had a simple method in Utilities class which performed Geocoding on LatLng object and returned an address in String or null if there’s not valid address.
I had setup GoogleMap.OnCameraIdleListener on a GoogleMap object to get the location of the center marker after dragging the map and called the above getAddressFromLocation() method there to get the address like this.
This was working but this had a small issue. If the address takes time in Geocoding, then the progress bar becomes stuck and screen hands including all the UI. This is because long operation is being on the main thread. And according to Android requirements, it should happen on the Worker or any other thread so that UI and main thread cannot be blocked.
Now, I had to put this line of calling getAddressFromLocation in another Thread or something just to make sure that main thread is not blocked. On a simple google search, I found plenty of ways like in this article. I wanted something simpler.
I liked the way of AsyncTask but I didn’t wanted to make another class extending AsyncTask . So, when I dig deeper, I found that there is a static method AysncTask.execute() which performs small operations in Worked thread without creating any extra classes.
So, after adding that my above code became like this:
As you can see, using this simple AsyncTask.execute()method made this thing very simpler. One more thing to note here is that we cannot perform UI operations like setting text on TextView or hiding ProgressBar in this Worker thread. These can only be performed in Main/UI thread. So, that’s why I have called runOnUiThread() method in the thread.
After compiling and running the app, this was the result.
Wajahat Karim is a graduate from NUST, Islamabad, an experienced mobile developer, an active open source contributor, and co-author of two books Learning Android Intents and Mastering Android Game Development with Unity. In his spare time, he likes to spend time with his family, do experiments on coding, loves to write about lots of things (mostly on blog and medium) and is passionate contributor to open source. In June 2018, one of his library became #1 on Github Trending. His libraries have about 2000 stars on Github and are being used in various apps by the developers all around the globe. Follow him on Twitter and Medium to get more updates about his work in Writing, Android and Open Source.
Wajahat Karim (@WajahatKarim) | Twitter
Also, if you have any questions you’d like him to answer, contact him through his website at wajahatkarim.com with DEAR WAJAHAT in the subject line.
Top comments (1)
That's a really neat trick, thanks for sharing! When I was looking into the AsyncTask.execute definition, the comment on the default executor says that using this method runs the runnables in "Serial Order", would this mean that it's executing the runnables similar to a Queue?
EDIT: developer.android.com/reference/ja... this kinda helps answer my question actually