Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Android Build a Weather App Hooking Up the Model to the View Plugging in the Data

Why do we need displayWeather object when we have currentWeather?

The object currentWeather has every fields set and you can do


and it works as expected. I don't see any reason why you should construct the new CurrentWeather object. After getCurrentDetails(jsonData), the fields must be set or displayWeather does not have any extra/updated information over currentWeather.

I do not think you need to use the overloaded constructor. I believe this way of doing it is correct and more efficient. The Android documents did not specify any reason for doing it using a new object either. Seems like the creators just overlooked this option.

1 Answer

Alexander Zola
Alexander Zola
9,027 Points

same thoughts if u set up async calls properly, there's no need for creating two objects (or i dont have any info that proves these practice)