CONCLUSION

The Async task by default runs the tasks in serial fashion, one after the other. Once the
task is not complete, the other tasks are waiting in the Queue to be picked up. The Async task
performs long-running tasks to keep our Main UI responsive, android provides a class known
as AsyncTask. As discussed above that AsyncTask separates intensive or time taking processing
from the Main UI. AsycTask has the ability to display the results back in the main UI Thread
while running or finished that's why we use AsyncTask rather than simple Thread class
and runnable().

Feature Enhancement

 In future we will provide a better GUI for the user interface with asyncTask
 Update the functionalities of asynchronous task
 Introduce the function that user doesn’t need to open the application again and again
 Improve the background running services
 Reduce the battery consumption of device
 Keeping device fast

12
 REFERENCES

[1]. Google. 2018. Processes and Threads. Retrieved 2018-7 f since Android UI toolkit is not
thread-safe, the single-GUI-thread model requires that async threads should not directly
manipulate GUI objects.

[2]. Cong Zheng, Shixiong Zhu, Shuaifu Dai, Guofei Gu, Xiaorui Gong, Xinhui Han, and Wei
Zou. 2012. SmartDroid.

[3]. Linjie Pan, Baoquan Cui, Jiwei Yan, Xutong Ma, Jun Yan, and Jian Zhang. 2019. Androlic:
an extensible flow, context, object, field, and path-sensitive static analysis framework for
Android.

[4]. Domenico Amalfitano, Anna Rita Fasolino, Porfirio Tramontana, Bryan Dzung Ta, and
Atif M. Memon. 2015. MobiGUITAR: Automated Model-Based Testing of Mobile Apps.
IEEE Software 32, 5 (2015), 53–59.

[5]. Domenico Amalfitano, Vincenzo Riccio, Ana C. R. Paiva, and Anna Rita Fasolino. 2018.
Why does the orientation change mess up my Android application? From GUI failures to
code faults. Softw. Test., Verif. Reliab. 28, 1 (2018).

[6]. Saswat Anand, Mayur Naik, Mary Jean Harrold, and Hongseok Yang. 2012. Automated
concolic testing of smartphone apps. In 20th ACM SIGSOFT Symposium on the
Foundations of Software Engineering (FSE-20), SIGSOFT/FSE’12, Cary, NC, USA -
November 11 - 16, 2012. 59.

13