Apple has been granted permission to step in against Lodsys, a holding company with alleged ties to Intellectual Ventuers, which is intent on suing iOS developers for patent infringement. Apple had originally applied to intervene nearly a year ago after Lodsys claimed the right to in-app purchasing, and consequently went after big-name devs like Square Enix, 2K, Atari, Rovio, and EA for royalties. Apple's stance has been that they've licensed the rights to the in-app purchasing mechanism to these parties, and that Lodsys should take up the fight with Apple directly.
This is a textbook case of patent trolling, and I imagine that while Lodsys might have had a shot squeezing money out of the smaller developers, and a slim chance of getting royalties from the bigger ones, they won't stand a chance against Apple. Lodsys went after Android developers too, and Google intends to intervene on that front in much the same way as Apple.
It's only unfortunate the courts took this long to decide, however, because those smaller developers have no doubt been hurt in the mean time.
Get the best of iMore in in your inbox, every day!
Editor-at-very-large at Mobile Nations, gamer, giant.
I'm tired of reading about a new Apple suit every week....
.... but not tired enough to still read and comment on them, obviously
Well, it's the right thing to do, if the audience is also democratic... Try to make things better via discussion and persuasion...
agreed, although this is important news which directly relates to apple, developers and users. you can't dumb down a site for the lowest common denominator when the other solution is : don't click on the link.
This also isn't a new suit, its been ongoing.They are just reporting that Apple can finally step in and aid the developers.
It's the free (for all) market, guys. Things like corruption, exploitation and patent hoarding/trolling are natural.
Taste of their own medicine looks like.
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.