next »

[isthisthingon]

http://www.pcworld.com/article/181745/lawsuit_claims_iphone_games_stole_phone_numbers.html?tk=nl_inx_h_crawl

  

Seriously not cool.  Bad Storm8 and... wait who approved this privacy pillager of an app??  It's not a slam on Apple, or at least not all of it.  Some heads should roll at Apple though 

This is the kind of thing the app approval process should catch.  Force.com is ridiculously meticulous about this and literally performs a code review after all functionality has been approved.  I've had many back and fourths answering direct questions about some of my more "questionable" cloud traversing code, some of it rather deeply nested in OO land.

[kurdt]

I always thought that quality/approval control was suppose to prevent exactly this kind of stuff from happening. Not cool Apple.

I'm sure some heads are rolling right now

[isthisthingon]

I always thought that quality/approval control was suppose to prevent exactly this kind of stuff from happening. Not cool Apple.

It's an unimaginably tough balance between staying competitive with apps and running a tight quality control ship.  The AppExchange certification process can take months.  Code testing coverage has to be above 75% and they really complain if you don't reach 100%.  With Apex it's got built in test-driven development that breaks whenever you go outside their cloud - intentionally.  Therefore you have to write automated test procedures that execute all lines of code before and after every callout.  Then test it again allowing the callout to fail that specific test procedure.

This way they can easily see each and every point where a program goes outside their cloud.  Same approach works for any OS if you choose to impose those "restrictions."  But phone numbers?    

Yep it's time for those responsible for allowing this to happen, unless Apple traded quality for quantity 

[jairez]

Yet another argument for Open Source.  IMHO

[perkiset]

Yep it's time for those responsible for allowing this to happen, unless Apple traded quality for quantity 

I'll bet not ... the reviewers are really in a tight spot. Continually assaulted for not going fast enough, then besieged for when they FU like this. I'd not take that job ... what an unforgiving and fickle position.

I'll betcha there's some sphincter factor happening in a meeting room at this very moment...