Subscribe(users -> { showRefresh(false); mAdapter. updateUsers(users); }, blunders -> { App. L. error(error. toString()); showRefresh(false); }); } We exhibit ProgressBar, and notice the checklist of clients from the StackExchange API supervisor. the instant the record is available in, we convey it and replace the Adapter content material and the RecyclerView visibility. developing the RecyclerView adapter once we have acquired the information from the remainder API, we have to bind it to the View, populating our format with an adapter. Our RecyclerView adapter is beautiful commonplace. It extends RecyclerView. Adapter and specifies its personal ViewHolder: public static category ViewHolder extends RecyclerView. ViewHolder { @InjectView(R. identity. identify) TextView identify; @InjectView(R. identity. urban) TextView urban; @InjectView(R. identity. attractiveness) TextView acceptance; @InjectView(R. identity. user_image) ImageView user_image; public ViewHolder(View view) { super(view); ButterKnife. inject(this, view); } } the instant we obtain the knowledge from the API supervisor, we will be able to set the entire labels at the view: identify, urban, and recognition. To demonstrate the consumer picture, we'll use common snapshot Loader by way of Sergey Tarasevich (https://github. com/nostra13/Android-Universal-Image-Loader). UIL is a fine looking recognized and well-tested image-management library. shall we use Picasso by means of sq., go with the flow, or Fresco through fb besides. it really is only a topic of your individual choice. the key isn't to reinvent the wheel: libraries facilitate builders' lives and make allowance them to accomplish pursuits swifter. In our adapter, we've: @Override public void onBindViewHolder(SoAdapter. ViewHolder holder, int place) { person person = mUsers. get(position); holder. setUser(user); } In ViewHolder, we've got: public void setUser(User consumer) { identify. setText(user. getDisplayName()); urban. setText(user. getLocation()); popularity. setText(String. valueOf(user. getReputation())); ImageLoader. getInstance(). displayImage(user. getProfileImage(), user_image); } At this aspect, we will be able to run the code and procure an inventory of clients, as proven within the following screenshot: Retrieving the elements forecast Let's elevate the stakes and produce the present city's climate into our checklist. OpenWeatherMap is a convenient internet carrier with a public API that we will question to retrieve plenty of priceless forecast info. As ordinary, we'll use Retrofit to map the API and entry it through RxJava. As for the StackExchange API, we'll create interface, RestAdapter, and a convenient supervisor: public interface OpenWeatherMapService { @GET("/data/2. 5/weather") Observable getForecastByCity(@Query("q") String city); } this technique will give you the present forecast utilizing the town identify as a parameter. we will bind this interface to our RestAdapter classification like this: RestAdapter restAdapter = new RestAdapter. Builder() . setEndpoint("http://api. openweathermap. org") . setLogLevel(RestAdapter. LogLevel. easy) . build(); mOpenWeatherMapService = restAdapter. create(OpenWeatherMapService. class); As ahead of, we're purely surroundings the API endpoint and the log point: the single issues we'd like right away.