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

iOS Build a Playlist Browser with Objective-C Building a Music Library Model Adding a Playlist

Why create sub model Playlist of model MusicLibrary?

I fail to see the importance of creating a sub model Playlist for our main model MusicLibrary. Why don't we just add the methods we want into our MusicLibrary.m in order to fetch a specific index of the Library array instead of creating a new model which will have a custom initialised method for that? Isn't that extra step a bit unecessary?

A play list would only include portions of the MusicLibrary. This feature would call for a new method. Also...title, artist, album, genre, etc are different attributes which would call for more programming. Adding these extra steps make the MusicLibrary more user friendly.