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 6 years ago.
Improve this question
I did some research on Google Volley and found that it is somewhat easy and clean to use.
But I am still not sure as to what the advantages of using it are and whether I should still use the AsyncTask.
I know AsyncTask works as a background task and that it is separate but what about Volley?
Which one should I opt for?
This is mainly an opinion based question that is largely dependent on the needs of your particular application. Volley provides a lot of things for you out of the box, like network caching (assuming you're given correct cache headers from your server), and an easy to use API with all of your callbacks and different threading layers handled for you. So, it really depends on what you're looking. Personally, I think any production worthy application should use some sort of networking library that a team has spent plenty of time patching and prepping for you (rather than trying to reinvent the wheel), and since a Google team has gone through the trouble for doing this for you...why not?
One cannot compare Volley with an AsyncTask.
So your question makes no sense.
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
I have been using Firebase for 'Android' for very long time without realizing that it has REST service that I can use with the help of any backend library such as the SDK-HTTPUrlConnection or any other third party library such as Retrofit or Volley. I tried using that to see why is it different? Why would I stop using the easy things Google gives to us in the Firebase to use the REST API, I actually could not answer that question, please any know why does it exist, is it not made for Android (although it works cuz it is just a normal REST)? or Why do u think?
The REST API is for development environments that don't have a provided client library. Client libraries are only provided for Android, iOS, and web. Server libraries are only provided for Node.js, Java, Python, and Go. What if you need to access Realtime Database from C++? Or Perl? Use the REST API - it's pretty much universally available.
If the Android library is working for you, then keep using it. No need to worry about the REST API.
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 6 years ago.
Improve this question
I am already aware of the advantanges of retrofit and have used it in many scenerios. For a particular application , I need to call only 1 login API which will do authentication.
I am not sure if the advantages of retrofit are worth it for only one API. or is it a overhead and I should Http for sake of simplicity
If it is just a single request, then I'd say go with the simplest/lightest approach. But these things tend to evolve with time, therefore you are likely to find yourself in a position of adding another one, then another one...
Remember - networking mechanism is not an architectural decision. In fact, your application should not care what networking mechanism is being used - it should depend on a general interface that you define. You could start with implementing this interface using the simplest approach, and add a more complex implementation in case your networking requirements evolve. You could also implement several approaches and benchmark them...
So, whatever approach you choose, I recommend not to "pollute" your business logic with networking logic, but hide it behind interface. This way even if you make the wrong decision now, it will be a matter of few hours to fix it later.
For a single API call http is fine. As you know using library with your application is going to occupy user phone space when they install your application on their device. so for a single call, you are good to go with async task.
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 know how to design and develop android application which works offline.But now i want to move towards dynamic android app,which works totally online like facebook,quora,newshunt.Where should i start please give me a way.
Thanks
I personally am completely self-taught when it comes to android, and, well, its been a journey.
For me, a big turning point was
"http://www.androidhive.info/2012/05/how-to-connect-android-with-php-mysql/"
It really gives you a good idea of what it takes to create an app that is connected to the internet, and it isn't hard to implement yourself. Mind you, before, you were working with just android, but once you integrate network connectivity and a server backend, the levels of complexity multiply.
If you're a solo-developer, just getting started, the Google App Engine does a pretty good job of making everything very easy to use, so I might recommend that. It has a free trial of all their cloud services which is $300 for 2 months.
https://cloud.google.com/appengine
Amazon AWS also is attempting to create a similar system, but they are seemingly geared to more enterprise-level operations.
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 7 years ago.
Improve this question
My application has some complicated database operations, Almost all the sql queries i have to use.
If I want server based access to my data, what should i choose to communicate with Parse server: SDK is good, but I know there is an API as well.
I think SDK will not provide a lot of accesses, operations like email verification, complex db operation can't be handle through it. and I don't know anything of server side coding.
Please suggest , Thanks in advance
I would suggest you to first read these
All the limits of parse
Parse SDK review
The second one is for iOS, but it's basically the same for Android. (I basically copied Objective-C code to Java, especialy the requests)
If you are sure you want to make complex app on Parse, then I would probably suggest to go for SDK. It is not that restricting, but will probably be hard to understand in the beggining, but you can do whatever you want if you setup good arhitecture from the start. :)
(But. It's only my opinion)
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
There are many frameworks to make http requests in Android, like Retrofit and Volley. But also, Android has its own classes to make this type of request, like HttpURLConnection and HttpClient
So what is the advantage of using some framework like these mentioned?
My doubt is if there is some big advantage in make requests using some framework, instead of using Android native classes.
The advantage is things like retries, restarts, threading & synchronization, and state management will be handled for you. This comes at the expense of configurability, but it's not a huge expense.