wraggster
September 10th, 2009, 17:24
http://www.blogcdn.com/www.engadget.com/media/2009/09/9-10-09nanpplayer2.jpg
Palm's App Catalog isn't exactly bursting with titles yet, but that isn't stopping the company from rejecting apps -- and the dubious honor of First App Rejected goes to NaNplayer, a music player app. Apparently NaNPlayer made use of an undocumented webOS API call, so it makes sense that Palm wouldn't approve it, but there's a somewhat less-sensible flipside: it was using the same API the built-in music player uses to index files so it could make playlists. That's pretty basic functionality, so we're hoping this all gets resolved with a future webOS update -- and in the meantime, NaNplayer will be released to the burgeoning Pre homebrew community when it's complete.
http://www.engadget.com/2009/09/10/first-palm-app-catalog-rejection-nanplayer/
Palm's App Catalog isn't exactly bursting with titles yet, but that isn't stopping the company from rejecting apps -- and the dubious honor of First App Rejected goes to NaNplayer, a music player app. Apparently NaNPlayer made use of an undocumented webOS API call, so it makes sense that Palm wouldn't approve it, but there's a somewhat less-sensible flipside: it was using the same API the built-in music player uses to index files so it could make playlists. That's pretty basic functionality, so we're hoping this all gets resolved with a future webOS update -- and in the meantime, NaNplayer will be released to the burgeoning Pre homebrew community when it's complete.
http://www.engadget.com/2009/09/10/first-palm-app-catalog-rejection-nanplayer/