java - Is there a best use API client pattern for Android? -

java - Is there a best use API client pattern for Android? -

this question may seem subjective because i'm not sure how inquire leads objective answer. there best utilize design pattern creating rest api client in android?

typically i:

put api methods in static apiclient class write manual serialization code each model i'm getting api (mostly because adding serialization library seems more complication). let activities handle success , error responses.

however i've seen lot of code has distinct classes each type of api call, extending classes abstractaction , abstractresponse. seems lot of people have own, different, ways of doing it, unusual because writing api client 1 of first things have when writing app. there right way it, or @ to the lowest degree improve way it?

the best pattern combination of various patterns. it's subjected type of activity supposed do.

for recommended design patterns see: google i/o 2010 - android rest client applications: http://youtu.be/xhxn3kg2iq

for accessing rest api, there's several libraries designed specific purpose (e.g., retrofit, volley, beingness of them) abstract network access serialization, doing these yourself, seems overkill unless there's specific reason so.

for example, in retrofit it's easy this:

the api interface

public interface githubservice { @get("/users/{user}/repos") list<repo> listrepos(@path("user") string user); }

using adapter

restadapter restadapter = new restadapter.builder() .setendpoint("https://api.github.com") .build(); githubservice service = restadapter.create(githubservice.class); list<repo> repos = service.listrepos("octocat");

this serialization, , serialization required.

there official example/tutorial on volley here

java android rest design-patterns serialization