Home/ Questions/Q 7164827
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T14:08:24+00:00

I know you’re not supposed to include slow-acting code on your UI thread in

  • 0

I know you’re not supposed to include slow-acting code on your UI thread in Android applications, but I’m not really sure what constitutes slow and what constitutes fast.

My application includes a permanent TCP Client connection to an external server. Up to now, I haven’t made any serious efforts at configuring its related code to run on secondary threads, and it seems to be working well enough.

Does anybody have strong feelings one way or the other about how an Android application should interact simultaneously with a user and an external TCP Server??

Thanks,
R.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In Android(or other platforms) the main thread is the UI Thread. This is because the user would always expect good responsiveness while using an application. If you overload this thread with any time consuming tasks, it will appear to the user that the app has frozen. This is against all Design guidelines, and you should definitely start separating your network connections from the main thread.

    • 0