www.webOShelp.net

Get the latest on:webOS Developers' RSS FeedwebOS Facebook page webOS Twitter Feed

Home Article Listing NaNplayer becomes first app rejected from the webOS App Catalog

NaNplayer becomes first app rejected from the webOS App Catalog

With Palm's App Catalog growing as of late and the e-commerce beta program gearing up, not all developers have their apps headed towards fame and glory. Precentral reported on the first official app rejection today, with Palm denying the NaNplayer app entry into the App Catalog. Here's a bit of what the developer, who is known as Blubble, had to say:

I have some bad news folks. Palm has told me that they will not allow my music player NaNplayer into the App Catalog at the current time...Palm stated that they don't support music file indexing and consequently won't admit the app into the App Catalog. It doesn't seem to matter that the app is works just fine on the Pre and that it is substantially better than their pathetic stock music player in terms of features and performance.

So it seems that while Blubble had a useful app forthcoming, NaNplayer makes use of an undocumented API, which queries music files on the device and their metadata. The usage likely violates the SDK EULA, resulting in an immediate rejection. However, of note is that it's the same API that the default music player uses on the Pre.

Palm developer community manager Chuq Von Rospach has since responded:

NaNPlayer is using APIs that are currently private because they will change significantly in a future release. Although we aren't able to support the functionality that JC needs right now, we are listening to the community to help prioritize which APIs and features we put into webOS.

While we can’t accept NaNPlayer into the App Catalog right now, we are not rejecting it, and we are happy for it to continue life as a homebrew application until we get to the point where we can release public, supportable APIs for the functionality that it requires.

Chuq Von Rospach
Palm Developer Community Manager

So while NaNplayer will now be scaling back to the homebrew scene right now, Palm could potentially include this API in a future official SDK release, and is listening to the community as to what other APIs and features should to be added in future releases. Has anyone else has their app denied by Palm, and if so, what reasons were given?

 

2 Comments

Feed
  1. I think it's great that Palm is addressing the rejection directly, stating reasons for the rejection (valid or not) and acknowledging the Homebrew community as a valid pipeline for future official apps and API development.
  2. Agreed, bezoris. This is good to see.

Add Comment


    • >:o
    • :-[
    • :'(
    • :-(
    • :-D
    • :-*
    • :-)
    • :P
    • :\
    • 8-)
    • ;-)