Quote:
Originally Posted by Reaperducer 
Not just other devices, but on OS X, itself.
I used to use a program under Tiger called Proximisync that would detect the Bluetooth signal from my Ericsson phone when I would come home, and automatically sync wirelessly. It was a great program (when it worked). And this was way back in the days of the Palm Pilot!
For this kid to feel ripped off is stupid. Somehow it never occurred to him that his app was rejected because Apple was already working on the functionality in the OS?
Duh.

Not just other devices, but on OS X, itself.
I used to use a program under Tiger called Proximisync that would detect the Bluetooth signal from my Ericsson phone when I would come home, and automatically sync wirelessly. It was a great program (when it worked). And this was way back in the days of the Palm Pilot!
For this kid to feel ripped off is stupid. Somehow it never occurred to him that his app was rejected because Apple was already working on the functionality in the OS?
Duh.
Well, according to the article at http://www.dailytech.com/article.aspx?newsid=21871, he was rejected because of unspecified security concerns and whole rejection process was not standard one Apple serves to other rejects.
Have Apple told him (and were able to prove) they already have that functionality developed and integrated in iOS5, I think he wouldn't have much reason to complain. But the way it was presented, it seems that Apple, at best, had that idea in the pipeline for future iOS developments, but not working code... Which makes whole case a bit shady.
And I really don't see what Apple asking for CV has to do with anything. If Apple wanted his code, they should have paid him for that. If they considered to recruit him, they should have asked for CV. Completely different issues.





). I said the only way this guy has a case is if Apple foolishly used some of his code. And there's no way they would be that dumb.




