blaenk / difm Goto Github PK

If the guys at di.fm don't come up with a way to fetch the stream URLs (JSON for example), then figure out a way to store the URLs.

To avoid a single point of failure, fetch all of the possible stream URLs and store them in a property list. Dictionary root with array keys which store the genre followed by all of the URLs. Change the streamer source so that if one fails, another one is attempted.

Perhaps provide a way to download the pls file and scrape the URLs as a form of updating the URLs in case they become old or outdated, though this probably wouldn't be very efficient.

Redesign the User Interface to mimic the look and feel of the iPod app. Every page should have a button on the top right to go to the player controller.

The player view should have a YouTube logo or icon that when clicked, takes the user to the YouTube app's results page for that song. Include an alert view to alert the user that they will be taken away from the app.

The favorites list should also include links to YouTube results.

This would allow users to easily favorite the songs on their YouTube accounts for later viewing or even for hearing the song again.

Also provide links to DJ Cotts, Ravine, and other DJs from di.fm in the app. They could appear in the channels list in their separate section or somewhere else.

Note: Verify legality of including YouTube logo.

Using the info from page 115 of the book, maybe it'd be a neat idea to make the favorite channels and all of the channels be back to back.

If not, then have two sections, one for favorites at the top and the other for the rest of the channels.

Clicking each channel will switch the view to the player view if it is a different channel than the one currently playing.

Use this as a guide. Create sub-folders for the resources to make things neater, and to avoid having everything in the top level directory.

Using the Reachability source files, determine if the situation is decent enough to stream the radio. If need be, fall back to lower bitrate streams, though they are different formats (I believe AAC 32kbit).

Reachability Sample Code

Currently, when a stream is chosen and the connection fails somehow, it displays an alert view.

Implement a fallback mechanism. If one stream fails, try to load a different URL. If all of the available URLs fail, cycle through all of the URLs one more time. If this fails, finally display the alert view.

Read Issue #7

The player view sould have an empty star or heart, clicking on it should fill it or color it. What this will do is add the song name (Artist and Title) to a favorites database categorized by genre/channel. Whenever the same song plays again, the heart or star will be filled, and perhaps the DI.FM logo will glow.

Perhaps add an option to vibrate the phone at the beginning of the song.

A database should be created for this. It will store the genre and song artist and title. Each time metadata is updated, the database will be queried to find out if the song is already there. If it is, then the heart will already be filled with red and song will not be allowed to be re-added to the database.

Should the genre be stored? If it isn't, it would avoid the problem that might happen if the same song appears in different channels. If it is stored, then when the user views the favorites, he or she will be able to look at their favorites on a per-channel basis.

Create an sqlite database (Core Data?) to store the total playtime for every channel.

Use FMDB or Core Data

Instruments says that there is a memory leak every time a stream is created. This is most likely somewhere around the header setting and CF calling. It says that there's a leak on an HTTPMessage, Dictionary, and an Array.

Tools:

• http://clang-analyzer.llvm.org/installation.html
• http://clang-analyzer.llvm.org/scan-build.html
• http://valgrind.org/
• http://landonf.bikemonkey.org/code/iphone/iPhone_Simulator_Valgrind.20081224.html
• http://www.mobileorchard.com/find-iphone-memory-leaks-a-leaks-tool-tutorial/
• http://www.cimgf.com/2008/04/02/cocoa-tutorial-fixing-memory-leaks-with-instruments/

Sometimes the meta data is stupid and messy like "Artist-Song (The Remix)". If the first parse attempt fails, try for this format.

Send the custom User-Agent string so that di.fm operators can see iPhone user statistics.

The formatted time string should not be created manually each time. Instead, create a method within DIFMStreamer that returns the formatted string.

When the ad comes up "Hey, you like the tunes here right?" the app crashes. This is most likely due to an out of bounds error when the metadata is parsed and split. A fix has been applied, but it has not been tested yet.

Redesign the Audio Streamer's architecture so that it is not necessary to access the app delegate each time (Makes things messy). Instead create a singleton that provides all of the necessary information. This should also make it easier to re-start the stream using the persistent data.