Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Mostly we handle network things in AsyncTask(doInBackground method). I have googled many times to find the most easy and robust way to handle network things. I have also searched here to find the appropriate answer. But still I didn't.
Maximum developers(including me) like to handle this with AsyncTask. But I don't think this is the perfect way. I have faced many problems(like slow process, ANR(Application Not Responding) for this.
So I am excepting the best answer, which will help me and many developers to handle network things in a best way.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
Whats the threshold to move code execution to a background thread (asynctask, services, threads etcc) in Android ?
Say if we know a task will complete in 50 milliseconds, should we offload it to background ?
What is the limit ?
The official documentation Keep your app responsive says:
Generally, 100 to 200ms is the threshold beyond which users will
perceive slowness in an application.
But it also depends on what you are doing on the screen. The screen is refresh at 60Hz (16.6ms), which can be a problem if you are playing an animation.
They also gives many advices to fix this issues on the ANR Documentation
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I want to know how to detect a rooting in a Android App.
This has been answered before, but here it goes:
I had this issue some time ago, and there does not seem to be one failsafe method to do this. For most scenarios however, you could check several characteristics that might point to a device being rooted, but again, this is not guaranteed to work every time.
Check out this previous answer regarding the issue, and remember; do not just copy and paste. Build an understanding of the code, so that you may learn something in the process.
Next time, try to do some more research before asking questions, Stack Overflow is filled to the brim with great questions and answers. Good luck with your app!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
i want to create mobile apps for cross-mobile platforms.
Two Frameworks are interesting for me.
Kendo UI vs Application Craft.
Important for me are supporting charts. I know, that both Frameworks are supporting this but which one is better?
Thanks & Greetings
I have tried both personally (not in professional projects) and I have find both very similar.
However, it was easier to find solutions to Kendo problems than to find the Application Craft. It seems like Kendo is more community supported in terms of forums.
With both I achieved the results I was looking for, but still it took me slightly more time to do it with application craft
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am aware of the different methods for switching back and forth between android screens. I was wondering wich method, if any, is the best practice for doing so. Switching activites seems to be the most popular, but how processor friendly is it?
EDIT:
This question seems too objective, so I guess I will modify it by asking if anyone knows what method is most processor friendly.
Yes, apps are typically separated by multiple activities. These days, the activities contain fragments to better support multiple devices, layouts, etc. They are popular for a reason!
It's all very friendly. ;)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
In the Android online API documentation, lots of methods seem to be undocumented, e.g.,
http://developer.android.com/reference/android/app/ProgressDialog.html#setProgress(int)
I don't think it's a matter of the methods being inherited.
Clearly this can't be the case, I'm sure millions of developers would be up-in-arms otherwise, so can somebody explain why the documentation isn't here?
Michael
can somebody explain why the documentation isn't here?
Because nobody wrote it.
You are welcome to examine the source code to the class in question and contribute a patch to AOSP with suitable JavaDocs for any gaps.
Or, you are welcome to file an issue for any methods that are missing documentation, particularly those whose usage is not intuitively obvious. There is a "Developer Documentation" issue template that will help to route the issue to the appropriate people.