Not exactly. Camera+ was not approved for the app store because of the volume button as camera shutter feature, so they resubmitted but hid the feature from the reviewers by including it as an easter egg. It was removed for a while from the app store because of that intentional deception. They're lucky they were allowed to resubmit the app at all after that (and so are we all, it's a wonderful camera app).
So the app with the "volume button as camera" feature was rejected, then within a year Apple turned around and implemented the same feature themselves.
Even if they didn't directly steal the idea, it seems like a pretty slimy tactic to me.
EDIT: Re-read the original rejection of the Camera+ feature here: http://taptaptap.com/blog/cameraplus-volumesnap-rejected/
They couldn't change the public APIs until the next release of the software, which is exactly what they did, and I imagine that Camera+ will be able to benefit from that API much as any other app.
Doesn't look too slimy to me.
For me it's all about the timing. They should have relaxed the guidelines and/or policy about reusing the volume buttons for other purposes (not just for use as a camera shutter, presumably) at some point before they released an implementation of the exact same idea as a third party.
It's kind of insane that they wrote that blog post explaining what other developers are doing (and the penalties they face for doing it) and then turned around and included "Volumesnap" through a back-door anyway. So yes, they're quite lucky they were able to resubmit the app later. There's no doubt they knew exactly what they were doing.
Again, I don't know if Apple is opening this up, so I won't describe it as slimy or not.
Someone like Red Pop [1], however, might be worse off though...
Edit: Re-reading the rejection notice from your link [2], it seems clear that Apple won't be able to reject people based on that clause again. At least, using the volume button for camera now seems to be pretty standard (IANAL so YMMV).
[2] »Your application cannot be added to the App Store because it uses iPhone volume buttons in a non-standard way, potentially resulting in user confusion. Changing the behavior of iPhone external hardware buttons is a violation of the iPhone Developer Program License Agreement. Applications must adhere to the iPhone Human Interface Guidelines as outlined in the iPhone Developer Program License Agreement section 3.3.7«
Further discussion here too: http://news.ycombinator.com/item?id=2625950
This is why competition is good and investing all your eggs into a single walled garden is dangerous.
Distribution has nothing to do with it.
http://bits.blogs.nytimes.com/2011/06/06/which-apps-are-thre...
The Paul Graham quote used in this article was spot on, especially the part about "...you may find that you were merely doing market research for them."
This is the problem with building apps on top of another company's API. You will forever be subject to their rules. Whether you're building on Facebook's API, iOS, or even Amazon AWS...you will always be competing to a disadvantage.