Print 41 comment(s) - last by Hintzmann.. on Jul 29 at 4:55 AM

Pending EU legislation may force Apple to open up its platform to rivals like Adobe.
Change in antitrust laws could have serious implications for many other companies as well

The European Union's European Commission, under the guidance of commissioner Neelie Kroes, has had no qualms with slamming U.S firms with massive antitrust fines.  Now it's preparing a massive new initiative which just may have a major effect on some U.S. firms.

The new measure, called the Digital Agenda, raises many points, but one of the most significant is to redefine what companies can be subject to scrutiny over abuse of their market position.  The Agenda looks to change the necessary language from "dominant" to "significant".  Its text, found here, includes the passage:

Since not all pervasive technologies are based on standards the benefits of interoperability risk being lost in such areas. The Commission will examine the feasibility of measures that could lead significant market players to license interoperability information while at the same time promoting innovation and competition.

This proclamation may affect a number of key players in the tech industry by forcing them to open their gates or face massive fines.  

Perhaps the biggest example is Apple, Inc.  Apple is being probed by U.S. government antitrust investigators over its decision to ban Flash from its iPad and iPhone.  The problem is that Apple can easily argue that it does not have a "dominant" position to abuse when it comes to the iPhone.  And even the iPad, the new clear leader in the tablet industry could stake make similar claims -- after all the term "dominance" is loosely defined.

However, there's little doubt that it plays a "significant" role in the tablet and smartphone industries.

Under the new measure, if the language is approved, the EU may gain the power to force Apple to allow Flash onboard.  It may also be able to finally force Apple to allow third-party devices -- like Android smartphones, the Palm Pre, or rival MP3 players – to sync with iTunes.  The EU has long complained about Apple's efforts to block such syncing.

If the measure forces the hands of companies like Apple, they may feel compelled to eventually embrace similar measures in the U.S.  The U.S. is slowly trending towards a policy of stricter antitrust enforcement, following in the EU's line.

Ultimately the issue boils down to whether the market's largest players have a responsibility to "leave the door open" when it comes to interoperability.  This may come at a small expense to firms to publish documentation, which they could likely cover with licensing fees.  However, what they ultimately truly stand to lose is a tool against their competitors.  

By tightly controlling their platforms and various products' ties, companies like Apple can build their brand in the eyes of the consume -- a key part of the so-called "halo effect" which has driven purchasers of one Apple product to pick up more Apple gadgets.  It's remarkably similar to the inside track that Microsoft Word and Microsoft Internet Explorer were given with Windows -- which landed Microsoft in hot water with U.S. antitrust investigators around the turn of the millennia.  Ultimately, such maneuvers don't even need a monopoly -- as Apple's extensive use of them has proven.  They merely require a significant market share to start; hence the EU's claim.

So is interoperability something that should be mandatory?  Or should companies be allowed to close their platforms tightly?  Advocates of a more laissez faire government would certainly argue the latter, but the EU and Kroes seem convinced of the former, a platform that may have a big impact on some of the tech industry's top firms in the U.S. and abroad.

Comments     Threshold

This article is over a month old, voting and posting comments is disabled

RE: You understand this wrong
By Penti on 7/3/2010 12:39:50 PM , Rating: 1
Apple are free to join the Open Screen Project if they wanted to develop flash for Adobe rather then the other way around and get access to source.

But Adobe wouldn't really develop the product and they (Apple) don't want to bundle it. But at the time they fought about it, Adobe had nothing to show except for none full flash versions like Flash lite.

I understand where Apple comes from, but to be fair they didn't as Palm join in to actually develop Flash Player for mobiles, they also didn't want to open up the system to just some developers. However as said Adobe hadn't demonstrated that they could pull it off as it hadn't engineered Flash 10.1 for mobiles yet, which is of a different architecture then the desktop version which still does CPU compositing. They could have created support for it in several ways. However just opening up the platform wouldn't really have cut it by itself and would have invited others to do webkit-plugins utilizing the hardware. If they hadn't fought about it maybe it could have been supported in iPhone 5 arriving next year, but not this year. They hadn't even released an open beta by the time the iPad released, yet Apple was unfairly criticized for not supporting it. Nobody else where supporting it either in a commercial product. It wasn't available. It wouldn't really have been finish by the time of the iPhone 4 release if they had tried. Android 2.2 with 10.1 built in is just arriving now. But that's also a platform better suited to have that kind of integration. (Droid 2 is released in August for example, Nexus One got 2.2 now though.) Other phones still stuck with 2.1 (or earlier) has no flash support. They can't postpone stuff in the wait for Adobe to get up to speed. It simply couldn't be included as a feature for the product even if they wanted to.

Mind you that the Flash 10.1 in Android 2.2 (FroYo) is still in beta. And that the Flash 10.1 player for Palm isn't released yet. No revolution either way yet. If Apple decides to release it in six months they will still be further along then most in adopting it. However Adobe has much to prove. It serves all companies to rather use the native ways integrated in the device to play videos. Then to go through an still unstable flash beta. At least if you like full frame rate video. It's nice to be able to use ordinary sites. But then it needs to be usable also, it isn't really yet. So why would Apple care about something Adobe doesn't really want to develop any way. They gave quickndirty access to hardware acceleration in OS X but as the Flash Player architecture is so awkward it isn't really a good fit and didn't made it into 10.1. Flash for cellphones isn't here yet so iPhone isn't missing out yet, neither is iPad. It needs to be x86 based to have hardware support, acceleration and that isn't really a MID-tablet. But rather a tablet PC. And you can't compare them two. It's better if the preferred way isn't dependent on Adobe release schedules. Why would you want to engineer something you ultimately has no control of. Integrating it to the device and it's usable as soon as it's included in an update (which is already done and supported by all smartphones). Most flash sites already encodes files that would play back fine directly by the phones own multimediaframework. Dropping being dependent on flash only techniques would be a good idea. Like RTMP and all that broken DRM stuff. It gives the manufacturers control. I don't really think it's about apps. As long as it's browser based only HTML5/CSS/JS apps competes fine with that. Flash in the browser wouldn't replace all the retarded apps people install.

RE: You understand this wrong
By MatthewFabb on 7/5/2010 11:37:05 PM , Rating: 2
Flash Player 10.1 for Android is no longer in beta, the final version was released June 22. When Nexus One's started received OTA Android 2.2 updates that include the final version of Flash Player 10.1.

Adobe also announced that they have given their Open Screen partners the final code base for 10.1. So with Palm, the ball is in their court, but everything seems to be on hold as the HP buyout goes through.

Also while Apple did open up the API for video hardware acceleration on Macs, Adobe wanted a full beta cycle like the Windows version got, rather than rushing it in and finding bugs later. When it was originally announced Adobe has said it would be released after the initial 10.1.

Anyways, if Apple had worked with Adobe, iPhone 4 could have shipped with Flash Player 10.1. In the meantime, someone has ported Flash Player 10.1 for Android to a jailbroken iPad (search YouTube for videos). Support for the iPhone 4 and 3GS is apparently coming as well, but they still need to be jailbroken.

RE: You understand this wrong
By Penti on 7/11/2010 6:19:48 PM , Rating: 2
They didn't open up an API, they created a specialized API just for the task which don't fit well in Flash Players awkward work flow.

But sure (new) Android phones come any day now with the final version. Palm on the other hand has had flash running for years without releasing anything. Point I made with Open screen was they could have treated OS X as a platform to release _and_ develop (and therefore also for iPhone) for themselves. But Apple have been busy doing other stuff, and Palm has been busy not getting out their phones, which I still can't buy here. Adobe should have a more off interest themselves, they don't really have an Apple team, they didn't at first collaborate with Apple or Nvidia and ATI, they did freaking do that on Windows, Microsoft didn't help them a bit. It's all in the drivers there. APIs weren't implemented so they could be used by Adobe. Of course I understand that they want to test it before releasing, but it's just retarded that it's so much harder for them then anyone else. You had CUDA, Elementals etc on Mac (which is used in a freaking Adobe product to begin with.). It wasn't Apple or anyone but themselves stopping 10.1 none-gala getting hwacceleration. Maybe iPhone 4 could have got flash but it would probably still have delayed the phone because of the developing resources not going to the core functions. iPad on the other hand couldn't when it was released. There's still no tablets with flash support really. Nvidia and ATI aren't forbidden to release drivers any how for the mac, and they don't even need to be signed and they are free to include any function they want, IO kit doesn't bring any limitations. It's not Apples fault just as it isn't Microsoft's service that got them enabling hwacceleration on Windows. But of course Apple made the choice not to work on the Adobe flash codebase. But neither did Microsoft. It's not Apple causing the injustice on the desktops, only when it concerns the handhelds. Which they I still say couldn't have counted to be included as a feature to any product. Of course it still can be released for both iPad and iPhone 4, theres no other reason then not have joined open screen project stopping that. But launching it as a feature would have taken a lot of work by Apple and not so much Adobe. It's simply a business structure or strategy not all will jump on. Including Microsoft.

And while it might be final it's still not universally useful. Still not a core feature of any product.

"Google fired a shot heard 'round the world, and now a second American company has answered the call to defend the rights of the Chinese people." -- Rep. Christopher H. Smith (R-N.J.)

Latest Headlines

Most Popular Articles5 Cases for iPhone 7 and 7 iPhone Plus
September 18, 2016, 10:08 AM
Automaker Porsche may expand range of Panamera Coupe design.
September 18, 2016, 11:00 AM
Walmart may get "Robot Shopping Carts?"
September 17, 2016, 6:01 AM
No More Turtlenecks - Try Snakables
September 19, 2016, 7:44 AM
ADHD Diagnosis and Treatment in Children: Problem or Paranoia?
September 19, 2016, 5:30 AM

Copyright 2016 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki