> your app uses public APIs in a manner not prescribed by Apple<p>What an enraging way to phrase this. I understand Apple's desire to shut this down, but they make their contempt for app developers obvious at every possible turn.
So why is this kosher? <a href="https://support.twitter.com/articles/20172069" rel="nofollow">https://support.twitter.com/articles/20172069</a>
<i>The obvious lesson is that you shouldn't build a service that skirts right on the edge of "Apple definitely won't like this."</i><p>Well at least you kept your sense of humor about it all. It will probably help your chances at employment (or investment of your own business) going forward. Nothing wrong with pushing the barriers a little bit.
I want to be outraged on your behalf over this but I can't really summon it forth. While I understand the ever-present engineer desire to "see if it can be done", no good can really come from this sort of service in my opinion. I guess chalk it up to an interesting technical exercise and that's it.
It's a shame you had to bring this down but it looks like you saw it coming and enjoyed the ride. I think the posts that characterize you as unethical are just not willing to cope with the disillusion that technology is a two sided coin. The information was there and you used it. I commend you on seizing on the opportunity and wish you best of luck in the future.