Radio Tuner Problems

When a program is under development and getting ready to be rolled out, it is often difficult to anticipate the problems that may be associated once it goes live.  What helps is the availability for users to have a forum where they can discuss the product, throw out questions and have other users respond based on their own experiences. 

Developers that have blog sites are an excellent source to find out about other users’ experiences with products.  They may be having trouble with the product that someone has worked through.  A prime example was a piece of exercise equipment that was seen on an infomercial.  On the site were almost 4,000 reviews, most of which dealt with how difficult it was to set the equipment up.  Several reviewers had commented on this, indicating that at first they had difficulty setting up the product, but soon discovered that there was a spring that prevented them from doing so.  No where in the instructions was this mentioned.  Subsequently, other users responded that had it not been for this valuable piece of information, which the manufacturer neglected to mention, they would have sent the product back.

Such is the case with radio tuner problems.  At the website, the developers have indicated that there have been several problems during the roll-out of the program.  For example, there seemed to be a problem with the streaming.  The moderators of the blog indicated the following: 

“We’ve seen quite a few comments about stream connection problems with the Public Radio Tuner. The development team is on the case, and working on a fix that will be released later this month. The fix will be aimed at enhancing how the Tuner handles network connection issues. When this release is pushed live, the Tuner will be more readily able to reconnect with streams when they are interrupted or buffering. Improving performance of the Public Radio Tuner is our highest development priority right now, and you won’t have to wait for the release of version 2.0, set for May.  We’d like to thank everyone who has told us about the issue and for providing the details that allowed us to trace the problem back to the source. We’ll get this fix out as soon as possible.”

It is important for the developers to have these comments and reviews of problems that users are experiencing.  It is a vital part of their project.  Many users make suggestions that aid in development of new functionality and that will be included in newer versions. Often times the moderators of the blog will respond directly to a writer who is experiencing problems.  Take for example, the afore-mentioned issue regarding streaming. The moderator replied those who were encountering problems listening to streams - “there are a number of factors and variables involved in getting the radio stream over the internet delivered to your phone and very few of them are within our control.”

Commenters will often play off of each other, answering questions directly as if the person were sitting in the same room and they were discussing the problem.  Here is an example of another interchange:  “I’m also having problems listening to streams here in Harvard Square, but when I walk home the streams magically start working again. Some things to consider; AT&T network reliability, internet stream availability and saturation.

My check to see if it’s Public Radio Tuner or the network that is having issues is to open another streaming radio app and see if they are also having problems. Most of the times if I can’t use Public Radio Tuner then Pandora or Wunder Radio also aren’t working.”

The bottom line is that developers need comments to address issues and work out kinks that they may not have thought of.  So although we hate to have problems, with an open line of communication between developer and user, those kinks can be kept to a minimum.