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 presently use volley for network calls.
But, Google doesn't seem to be actively maintaining volley.
I heard that google initially developed volley to use it for its play store app but they haven't mentioned it in their list of 3rd party libraries used.
Almost everyone uses Retrofit(looking at the benchmarks, Retrofit seems better option), is it time to quit using volley?
p.s: please don't post the pros and cons of volley and retrofit
Google doesn't seem to be actively maintaining volley
That depends entirely on how you define "actively maintaining". Development is ongoing, as you can see by looking at the Volley git repo, which shows many commits over the past year (as of the time of this writing).
Google also shipped an official Volley artifact earlier this year, as version 1.0.0.
but they haven't mentioned it in their list of 3rd party libraries used
Google wrote the Play Store app. Google wrote Volley. Hence, from Google's standpoint, Volley is not a third-party library. For anyone other than Google, Volley is a third-party library.
Almost everyone uses Retrofit
Retrofit is not equivalent to Volley. The triad of Square HTTP libraries (OkHttp3, Retrofit, Picasso) would be equivalent to Volley, and that combination exceeds Volley's capabilities.
Based on questions here at Stack Overflow, I do not believe that "almost everyone uses Retrofit".
is it time to quit using volley?
Nobody can answer that other than you. You are the one with decision criteria of importance to you. You are the one who needs to evaluate which libraries meet those criteria.
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 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 3 years ago.
Improve this question
I am building a news application and I receive news in JSON format.
One of my friends recommended me to use Retrofit, but I did not understand why I should use Retrofit library instead of just handling Json with Gson myself.
Is there some advantage of Retrofit that I am not aware of?
Retrofit will save your development time, And also you can keep your code in developer friendly. Retrofit has given almost all the API's to make server call and to receive response. internally they also use GSON to do the parsing. you can go through this link you will get more info
http://vickychijwani.me/retrofit-vs-volley/
Developing your own type-safe HTTP library to interface with a REST API can be a real pain: you have to handle many aspects, such as making connections, caching, retrying failed requests, threading, response parsing, error handling, and more. Retrofit, on the other hand, is a well-planned, documented and tested library that will save you a lot of precious time and headaches.
Volley v/s Retrofit see this link
http://vickychijwani.me/retrofit-vs-volley/
compile 'com.google.code.gson:gson:2.6.2'
compile 'com.squareup.retrofit2:retrofit:2.1.0'// compulsory
compile 'com.squareup.retrofit2:converter-gson:2.1.0' //for retrofit conversion
Retrofit 2 is great networking library for modern Android apps, but each has its own strengths that is worth weighing for critical projects. Use Retrofit if your use-case is a standard REST API with JSON responses and not too many custom requirements in terms of caching, request prioritization, retries, etc.
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.
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.
The community reviewed whether to reopen this question 8 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
I am trying to implement a code which makes intial get/post request to fetch the data then using that data i m going to fetch download links with jsoup.
file are n't greater than 200 kbs
so which is better to do this task?
1)intial request
2)downloading files
How to chose between: Volley and Retrofit
If you are :
Making Requests then I would like to say though both frameworks are capable of the same outcome, Retrofit is capable of accomplishing this without customization. However, if you are implementing multiple requests within your application, and I suspect you are, customization may be necessary within Retrofit. Though that could be the case, at the simplest level Retrofit has the easier solution.
Downloading Files(Image): Being able to make file requests was a pretty large factor in the making of our decision. Volley comes packaged with a loader specifically designed to download images for you. Packaged along with the loader is a custom view called the NetworkImageView in which the developer only has to hand a URL and an ImageLoader to and Volley does the rest. This view is specifically targeted to work well with list views and allow for automatic cancellation of requests when the images parent view is destroyed. On the contrary, Retrofit does not easily support image downloads. To accomplish what we are able to with Volley, one would be required to download and include another library in your project such as Picasso. So here Volley is a better solution.
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
This question is actually not about the coding, so I don't put any codes here.
While looking into the Volley library, I found out that some part of the APIs contain classes (e.g. classes of the org.apache.http packages) that are now deprecated in Android API level 22.
As I'm concerned about getting adjusted to the newest API environment, do you think it is still worth using Volley or would you recommend using other libraries such as OkHttp or Retrofit?
Check out the detailed response:
Comparison of Android networking libraries: OkHTTP, Retrofit, and Volley
Personally, I went native to keep things simple and robust. Using it for JSON responses and occasional images with no problem and I don't think they will deprecate HttpURLConnection anytime soon.