What's happening here is probably similar to Apple's position on coverflow imitations - there have been lots of rejections for apps that imitate coverflow poorl

What's happening here is probably similar to Apple's position on coverflow imitations - there have been lots of rejections for apps that imitate coverflow poorly, even without private APIs. Speaking with somebody directly about this, and basically, their stance is: coverflow is an experience owned by Apple. If you imitate it poorly or inaccurately, users will have a bad / confusing experience (Apple's call what 'poorly or inaccurately' means, of course).