Apple Lawyer Outs Internal Samsung Documents That Claim The iPhone Is “Easy To Copy”

Jordan Crook studied English Literature at New York University before entering the tech space. Prior to joining TechCrunch, Crook dabbled in mobile marketing and mobile apps as well as doing device reviews for MobileMarketer and MobileBurn. Crook is fascinated with alternative energy production and greentech. She is now a writer for CrunchGear. ? Learn More

samsung_phones_before_after_iphone

Today the first shots were fired in the high-profile U.S. patent war between Apple and Samsung, beginning with Apple’s opening statements.

And no punch was pulled — Apple’s lawyer made a few hard-hitting claims in the courtroom, providing documents that show Samsung thought the iPhone was “easy to copy.” Harold McElhinny (Apple’s lawyer) also showed documents prepared by a Samsung executive that claim that the company was in a “crisis of design” because of the iPhone.

The presentation also included images of Samsung’s design evolution between pre-iPhone time and now.

But despite the evidence, McElhinny’s most crushing blow may have come in the form of a simple and well-known tech adage: “As we all know, it is easier to copy than to innovate. Apple had already taken the risks.”

However, just saying the hardware is easily copied isn’t proof of copying it, which is why McElhinny returned to evidence introduced in pre-trial, depicting Samsung’s phones before 2007 and their phones after the iPhone’s debut.

Take a look:

According to McElhinny’s argument in court (via Reuters), the main question the court would have to answer was how Samsung went from the phones on the left to the phones on the right.

Apple argues that 22.7 million devices sold by Samsung are in violation of patent infringement, and that the company is seeking up to $2.525 billion in damages. Samsung will follow up in its opening statement later this afternoon.


Started by Steve Jobs, Steve Wozniak, and Ronald Wayne, Apple has expanded from computers to consumer electronics over the last 30 years, officially changing their name from Apple Computer, Inc. to Apple, Inc. in January 2007. Among the key offerings from Apple’s product line are: Pro line laptops (MacBook Pro) and desktops (Mac Pro), consumer line laptops (MacBook Air) and desktops (iMac), servers (Xserve), Apple TV, the Mac OS X and Mac OS X Server operating systems, the iPod, the...

Learn more jQuery(function() { jQuery("#tabs-crunchbase").tabs(); });

View the original article here


This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.
-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more