nanplayer
Latest
Palm responds to NaNplayer rejection: "We are happy for it to continue life as homebrew" until APIs are complete
Well, how about that -- Palm Developer Community Manager Chuq Von Rospach has taken the time to respond to earlier reports of NaNplayer's rejection from the App Catalog, and he's surprisingly cool about it. As we'd heard, the underlying issue is that NaNplayer uses private APIs that will change in a future version of webOS, so Palm doesn't want apps built on them. That's understandable, but here's where Palm's doing it right: Chuq says that Palm is happy for NaNplayer "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." That's the sort of hacker-friendly compromise we can get behind -- anyone in Cupertino taking notes?[Thanks, Joe]
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.
