Judge denies Apple’s motion to ban infringing Samsung products and denies Samsung’s juror misconduct motion

Apple vs Samsung

Yesterday the first two decisions after the December 6 Apple v. Samsung hearing were handed down, and I’m sure the decisions have left each party unhappy for different reasons.

Denial of Apple’s motion seeking sales ban:

Judge Koh’s decision hinged on the lack of a “causal nexus” between the infringement and the harm suffered by Apple.  In the case of smartphones, which utilize literally thousands of patented technologies, Apple must demonstrate that it lost sales directly due to the 6 infringed patents in order to obtain an injunction:

First and most importantly, Apple has not been able to link the harms it has suffered to Samsung’s infringement of any of Apple’s six utility and design patents that the jury found infringed by Samsung products in this case. The fact that Apple may have lost customers and downstream sales to Samsung is not enough to justify an injunction. Apple must have lost these sales because Samsung infringed Apple’s patents. Apple has simply not been able to make this showing. Though this is a case where the “plaintiff practices its invention and is a direct market competitor,” [citation omitted] it is not a case where the
patented inventions are central to the infringing product. Without the required causal nexus, the parties’ status as direct competitors simply does not justify an injunction.

The large number of patented technologies that make up a smartphone compared with the small number of infringed patents owned by Apple was significant to Judge Koh:

The phones at issue in this case contain a broad range of features, only a small fraction of which are covered by Apple’s patents. Though Apple does have some interest in retaining certain features as exclusive to Apple, it does not follow that entire products must be forever banned from the market because they incorporate, among their myriad features, a few narrow protected functions. Especially given the lack of causal nexus, the fact that none of the patented features is core to the functionality of the accused products makes an injunction particularly inappropriate here.

Judge Koh also noted that Apple’s previous agreements to license its patented technologies (including with HTC as well as negotiations with Samsung) demonstrates that Apple’s patented technologies are not priceless, which weighs against an injunction.

There is no doubt that this decision does not sit well with Apple. While many of the Samsung devices that are the subject of this lawsuit are no longer on the market and are certainly not driving Samsung’s current sales, I’m sure Apple does not want to allow this kind of reasoning to stand because it will make it more difficult for Apple to obtain injunctions against Samsung or other competitors in the future. For this reason, I’d say an appeal is a near certainty.

I see both sides of the coin here. On the one hand, user experience is an important factor in smartphone sales, and there are many elements that users don’t even realize exist that combine to make a better user experience. Features like the way pages scroll and the visual effect you see when an app opens and closes go unnoticed by many, but does that mean that these features can be stolen from their inventors with the consequence of only monetary damages from a company rolling in money simply because it is impossible to pinpoint those features as driving sales?  This will, Apple will argue, give a license to steal any feature that doesn’t make up the core functionality of a smartphone.

On the other hand, there can be half a million patented technologies in a single smartphone, and if sales were allowed to be halted due to just a few infringed patents there would be even more patent litigation and it would slow down technological innovation – the very thing patent law is in place to foster – because smartphone manufacturers would fear that the inclusion of a technology that comes too close to a patented technology could have a disastrous effect on their business (as sales bans in the fast-moving smartphone world basically render the banned device worthless).

At the end of the day, Samsung turned itself into a smartphone powerhouse and the billion dollar jury verdict (if upheld) was really worth it to get its foot in the door. It seems unjust when said like that, but Apple isn’t exactly a sympathetic party either.

Worth noting is that Judge Koh’s decision denying the injunction did not speak to the jury findings, though reading between the lines it is almost a sure thing she will not completely throw away the jury verdict after issuing this decision.

* * *

Denial of Samsung’s juror misconduct motion:

After the verdict was reached, Samsung moved to throw away the verdict based on an alleged bias of the jury foreman and on that same foreman bringing extraneous evidence into jury deliberations. In short, Samsung alleged that the foreman, Velvin Hogan, intentionally omitted a lawsuit involving him and Seagate Technology, his former employer, when asked about prior lawsuits. Seagate was his former employer and had given Mr. Hogan a loan which Mr. Hogan did not repay after being terminated, and when Seagate sued Mr. Hogan, Mr. Hogan filed for bankruptcy  The significance of this is that Samsung now is the largest shareholder of Seagate with a 10% share. Samsung also claimed that Mr. Hogan’s post-verdict interviews demonstrated a desire to be on the jury (which Samsung claimed coupled with his Seagate omission proved bias) and also demonstrated that he gave the jury improper instructions based on his own understanding of patent law as opposed to what they were told by the court.

Judge Koh found that Samsung failed to exercise reasonable diligence in researching Mr. Hogan and thus lost its right to challenge his impartiality. Judge Koh opined that Samsung knew of the bankruptcy proceeding and knew of Mr. Hogan’s past employment with Seagate, and if it had timely requested the bankruptcy file, as it did after the verdict, or questioned Mr. Hogan on his relationship with Seagate, it would have discovered the prior lawsuit. Since Samsung did not properly research Mr. Hogan prior to the trial, it cannot claim impartiality after the trial.

Judge Koh also held that Mr. Hogan’s statements in post-verdict press interviews are inadmissible under Rule 606(b), which prohibits a juror from being able to impeach is or her verdict. The judge found that while jurors may not bring their personal knowledge of the parties or the specific issues presented into deliberations, they can bring in their general knowledge and life experience, which is what Mr. Hogan did. In denying Samsung’s request even for an evidentiary hearing to further address these issues, Judge Koh found that Samsung did not properly show that the verdict would have been different had the alleged misconduct not occurred.

Worth noting is how much deference Judge Koh gave to Mr. Hogan’s statements that he is unbiased and fair.

I am not surprised that Judge Koh did not toss the verdict based on Mr. Hogan’s interviews, as courts are very reluctant to second-guess a jury’s thought process. I am slightly surprised that Judge Koh did not seem more bothered that Mr. Hogan failed to disclose his Seagate litigation. She is 100% correct in saying that Samsung should have done more research into Mr. Hogan’s past, but that doesn’t completely negate the fact that Mr. Hogan omitted elements of his past in voir dire. Any party can (and should) do independent research into prospective jurors to find out potential biases, but requiring Samsung to do so makes the voir dire process designed to elicit those biases seem hollow.  I also find it to be a circular argument to respond to Samsung’s claims that Mr. Hogan is essentially a liar with Mr. Hogan’s statements that he will be honest. But I do understand how gutsy it would have been of Judge Koh to toss the verdict and order a retrial, which would cost hundreds of thousands of dollars to the parties, not to mention possibly billions of dollars if a different verdict is reached, and her reluctance to do so. I also understand not wanting a party to get away with turning a blind eye to a potential bias and then raising it when the verdict doesn’t go the way they want, so I really can’t say I disagree with Judge Koh’s reasoning.  I do think Judge Koh should be more mad at Mr. Hogan, but I guess, unlike me, a judge has to pick a side and I don’t blame her for picking the side she did.

The real thing I take away from her decision is that civilians like Mr. Hogan and the other jurors, whose reasoning in the jury room will clearly not be questioned, should not be responsible for applying extremely complex patent law principles. Patents are highly technical documents, and attorneys drafting them are required to have technical backgrounds. Patent examiners who determine whether to grant a patent are also required to have technical backgrounds. Engineers who invent the software that is the subject of this lawsuit all have technical backgrounds.  Ditto for other kinds of inventors. So why, after all that work performed by experts, do we leave evaluating whether a patent is valid and infringed upon to civilians, many of whom have little to no technical expertise whatsoever, and then require such a high standard in reversing their decisions? It seems like a weak link in the process that has great consequences and could be avoided. I’m all for a jury in determining whether a murder suspect’s alibi is convincing or whether parties intended to form a contract, but with patent law it seems like these important decisions would be left up to trained individuals.

Apple Unveils the iPhone 5

Apple unveiled its highly-anticipated next-generation iPhone, the iPhone 5, today. Here are some of the most notable changes that the iPhone 5 brings:

  • Larger display:  The 3.5″ 960×640 4:3 display (dubbed a “retina display” based on pixel density by Apple) found on previous iPhone models was increased to a 4″ 1136×640 16:9 widescreen display.  The increased size is due to the display being elongated vertically; in other words, it remains the same width, but adds an additional 176 rows of pixels to the length of the display.  While on a homescreen, this change adds another row of icons.  Developers will be able to modify their apps to make use of the additional space, or current apps will be centered on the display with black bars on the top and bottom, akin to how widescreen movies looked on older4:3 television sets.  The display also has 44% better color saturation than previous models.
  • LTE capability:  The iPhone 5 can now connect to faster 4G LTE networks.  There will be GSM and CDMA versions, unlike the iPhone 4S which ran on both CDMA and GSM networks.
  • Lighting connector:  Apple has done away with the 30-pin connector that it introduced with the iPod and replaced it with a smaller connector that works whichever way one plugs it in.  Apple said this was necessary to make the iPhone 5 thinner.  It appears the Lightning connector will become the standard across all portable Apple devices, and Apple said audio manufacturers are already implementing the new connector in their clock radios, docks, etc.  Apple will also sell converters for older devices.
  • Improved camera:  In what has become a standard Apple improvement, Apple has made the iPhone cameras better.  The rear “iSight” camera remains 8 megapixels but adds faster photo capture, better low light performance, and panorama mode.  The rear-facing camera will still record video at 1080p, but adds face detection and the ability to take photos while recording.  Of note is that the iSight camera is protected by sapphire crystal, which is very scratch resistant and is the material used on luxury watches.  The front-facing FaceTime camera has been upgraded from VGA (0.3 megapixels) to 1.2 megapixels, and it records 720p video.
  • A6 Chip:  Apple claims that the A6 chip used in the iPhone 5 will give it 8 hours of browsing time using LTE.
  • iOS 6 and Apple Maps:  The iPhone 5 will come with iOS 6, which has switched from Google Maps to an Apple mapping software which adds turn-by-turn navigation and flyover mode.
  • Thinner and lighter:  In what has become another Apple standard improvement, the iPhone 5 is 18% thinner (at 7.6 mm) and 20% lighter (at 112 grams).
  • EarPod headphones:  Apple redesigned the headphones that will come with the iPhone – they said it took 3 years! – and claim that they fit and sound better.
  • A third mic:  Apple added a third microphone to the iPhone – now there is one on the front, one on the back, and one on the bottom – that are supposed to work to cancel out background noise while on the phone.

All in all, I would say the iPhone 5 is a good, solid phone, but it is more of a catch-up with other smartphones than it is a standard-setting, industry-leading device.  It does look beautiful, and the increased screen size and LTE capability were both necessary improvements at this stage.  However, so many of the features can already be found on other devices: LTE has been on smartphones for a year and a half, 4.5″ and larger displays are really the standard, the pixel density found in the “retina display” is no longer that remarkable, there are already phones that are thinner and lighter, an 8 MP rear- and 1.2 MP front-facing camera is pretty commonplace, panorama mode was included in Android Ice Cream Sandwich almost a year ago, the ability to use FaceTime over a cellular network only catches it up to other video-conferencing programs, and I would say the booming headphone business makes the EarPods less of a draw.

And of course, the change in mapping software is also a catch-up in a way.  iOS devices have traditionally had a stripped-down Google Maps that doesn’t include turn-by-turn navigation and has more limited search results (for example, if I search “restaurant” on my iPad Maps it will return only the ten nearest results, and if I want to see restaurants in a new area I have to re-center the map and search again, while on my Galaxy Nexus Google Maps will return all restaurants, and keep showing more results as I scroll to other areas.)  I am not sure who is to blame for the stripped-down Google Maps, but better mapping software with navigation was much-needed, so in a way the new Apple Maps is an improvement.  That being said, I think Google Maps is the best and most widely-used mapping software out there, and I think the iPhone 5 would have been better off with an improved Google Maps app.

Another area where the iPhone 5 really disappointed me is the lack of NFC (Near Field Communication).  NFC allows for a variety of applications, most notably using a phone to pay for items at checkout by tapping the phone on the credit card reader in a store.  Google Wallet is a popular platform for this, but NFC allows for a variety of software.  While NFC hasn’t quite hit the mainstream yet and stores that make use of the technology are in the minority, it is a technology that is being implemented more and more and has the potential to be revolutionary.  I think Apple really dropped the ball by not including it.  Maybe most customers won’t miss it, but for a company that prides itself on innovation, Apple should have included it.

* * *

I understand that Apple can’t release a product that changes the industry with each new iteration of the iPhone, and perhaps the lukewarm reception the iPhone 4S and the iPhone 5 has seen is a result of Apple setting the bar very high for itself.  But the bottom line is that the mobile industry is moving at a lightning-fast pace and releasing a thinner and lighter phone with beefed up specs each year won’t cut it in the long-run, and where a few years ago competitors would be racing to put out products that can compete with the iPhone after an iPhone announcement, now I can’t really see anything that Google or Android device manufacturers need to implement in order to compete with the iPhone 5.  And from what I hear Windows Phone 8 is going to be very impressive when it is released in a few months.

The iPhone 5 will no doubt be a commercial success, and there is a huge market of people who are invested in the Apple/iTunes ecosystem and/or who think the iPhone is the simplest solution for them and/or are scared of change, but just like how RIM had so many invested users who fled when a better product came out, a f light from which RIM still has not recovered, the same could happen to Apple.  I can see it now: people looking back at the iPhone the way I look back at my tiny BlackBerry Pearl, and laughing about how small the screen is and how dull the static grid of icons looks.  Now, I’m being a little facetious, and Apple, unlike RIM, does have sort of an all-encompassing ecosystem that includes music, movies, TV, computers, and printers, and that ecosystem encourages people to stay with Apple, but I think my point is still valid.  I would like to see Apple come out with something that sets a new standard in the tech world in this post-Steve Jobs era, because any company releasing better technology benefits the entire industry.

For more on the iPhone 5, check out Apple, CNETThe VergeEngadget, Gizmodo, BGR, and The New York Times.

Worth noting is that Apple also unveiled a new iPod Touch, iPod Nano, and iTunes software today.

Opinion: The Apple v. Samsung Patent War Is Out Of Control

Apple v. Samsung, worldwide:
Apple and Samsung are currently suing eachother in over 50 cases in 10 countries, and the verdict reached by a jury in California last week that largely favored Apple seemed to do little to push either party towards reconciliation; I figure it emboldened Apple and made Samsung want to clear its name and also avoid cutting Apple a check for a billion dollars. The final decision in that case is still pending a December 6 hearing, and subsequent appeals. I would be surprised if all of the jury’s findings on both patent validity and patent infringement are upheld when all is said and done, but the jury’s verdict does give Samsung an additional hurdle to overcome. Even after a final determination is made in this case, Apple still has additional patent claims pending in California.  I had a glimmer of hope for a resolution when I read news earlier today about Apple and Google continuing to engage in talks to end their patent wars, but that hope didn’t last long.

Samsung will sue Apple if when it releases a 4g LTE iPhone:
Today I read a troubling story in The Korea Times, which stated:

Samsung confirmed that it will immediately sue Apple if the latter releases products using advanced long-term evolution (LTE) mobile technology.

It is almost a sure thing that the next iPhone will use 4G LTE technology. Apple may have a few defenses, like that Samsung’s 1129 LTE-related patents are industry standard functionality that must be licensed under fair, reasonable, and non-discriminatory (FRAND) terms and that a vendor that supplied Apple with the chips that incorporate the patented technologies already paid Samsung licensing fees (known as “patent exhaustion,” as was found to be the case with Intel and 3G technology in the most recent litigation), but this litigious stance by Samsung will amount to even more patent lawsuits worldwide between these parties, and provides even more evidence that our patent system may need fixing.

Smartphones and Patent Law:
Patent law began as a way to encourage innovation by granting an inventor the exclusive right to use (or not use) his or her invention. I’m all for this, and can see the usefulness back when people were inventing new methods to manufacture automobiles or harvest grain, and can still see the usefulness in areas like pharmaceuticals and medicine. But now, at least with technology, products are more complex – a single smartphone can utilize over 250,000 patented elements – and they are being developed at an incredible rate. Add in that the mobile market is extremely lucrative (Apple and Samsung combined for approximately $40 billion in revenue from smartphones in the first quarter of 2012) and that Apple and Samsung both have more than enough money to afford their worldwide litigation, and that is how we find ourselves reading about such a vicious patent war, which, by the way, is also costing tax-payers money by tying up our courts and federal employees. I can’t fully blame Apple or Samsung, as they are both working within the framework of our (and other countries’) patent systems. Sure, it’d be nice if they reached a peaceful resolution, but they are entitled to litigate should they be unable to resolve their disputes.

I don’t claim to have a solution, as it is always much easier to identify a problem than it is to solve it. One possibility is to be much more strict about what patents are granted. Right now an invention won’t be patented if it is “obvious at the time the invention was made to a person having ordinary skill in the art to which” the invention pertains. Perhaps the “non-obvious” standard is applied too liberally by Patent Examiners, and the Patent and Trademark Office doesn’t look to prior art, or earlier inventions that are similar, enough in determining whether an invention is obvious. Allowing minor differences from prior art to be the grounds for a patent grant, for example, in finding distinctions between various kinds of gridded icon layouts or methods for attaching photos to emails, is fueling all this litigation by increasing the number of patents and thereby increasing the likelihood of infringement claims.

Another area in which patent law as it relates to smartphones is completely out of touch is the duration of patents.  Right now a utility patent lasts for twenty years.  Twenty years is a long time in the technology world.  Twenty years ago, I think my family had an old black-and-white computer that we used for word processing, and I remember thinking I was on the cutting edge of technology with my Aiwa CD Boombox.  Fifteen years ago, I was still using  AOL with a dial-up 28.8k modem, and thought when my friend got a 56k modem that it was lightning fast.  Ten years ago I had a cell phone with an antenna, rubber buttons and a black-and-green display. Just five years ago, I was using the BlackBerry Pearl, and most of my friends were impressed that I could get email on my phone. My point is that twenty years is a long time for technology, and giving an inventor the right to a software patent for such a long time – probably longer than that patent will have value – does far more than is necessary to encourage inventors to invent new software. If doing away with software patents altogether doesn’t sit well, perhaps with a shorter duration – maybe even as short as a year or two in some cases – the inventor will be rewarded with a period of exclusivity on his or her invention and get a head start on the competition and hopefully reduce the number of lawsuits because it will make the waiting period more practical.

The changes that the patent system should see are all aimed at encouraging competition, which ultimately benefits the consumer. The problem is that some companies invest millions of dollars in developing new technology, and without the exclusive right to use their invention others will benefit off their hard work. While I understand this concern, I still think that a significant market benefit goes to a creator. Look at Apple and the iPhone: regardless of what prior art preceded the iPhone, it was the first device of its kind to see success in the market, and the value of being the original stands for a lot, and in my opinion, still drives sales to this day, over five years later. So whether or not Apple had patent protection, it saw a huge reward for being the original. The same goes for the iPod and iPad. And for instances where companies are making outright copies of the iPhone, then companies like Apple can protect their exact designs through copyright and trademark law.

I don’t mean to advocate for the abolition of all intellectual property rights; my issue is with a narrow area of software patents relating to the mobile industry that is giving large technology companies weapons to fight what looks to be a never-ending patent war, and how the law behind these kinds of patents should at least be looked at. A re-evaluation and possible change would at least keep the war out of the US, freeing up our courts and encouraging companies to bring their newest and greatest products here.

Jury finds in Apple’s favor on most claims and awards $1.05 billion in damages

The jury in the most-anticipated patent trial I can remember, and certainly in the mobile phone and tablet industry, has reached a verdict surprisingly soon – after less than three full days of deliberation. And while Apple didn’t win on all claims, it comes out the victor in this trial…pending appeal, of course.

It’s hard to summarize such a complex trial involving so many patents, devices (including the Galaxy S, S II, Epic 4G, Captivate, Vibrant, Infuse 4G, Droid Charge, and the Galaxy Tab 10.1), and three different Samsung corporate entities, but I’ll give it my best shot, with some help from The Verge (and more help from The Verge here):

Apple’s design patents and the jury’s finding:

The ’677 Patent and the ’087 Patent both describe an iPhone with an uncluttered front display made of glass, rounded corners, an edge border, a home button, and a speaker slot. The jury found that almost all of Samsung’s smartphones in question infringed both patents.

The ’305 Patent describes the iOS user interface: a grid of icons with a dock for icons at the bottom of the display. The jury found that most of Samsung’s devices infringed the ’305 Patent.

The ’889 Patent relates to the iPad and describes a rectangular electronic device with a thin bezel, outer edge border, rounded corners, and rounded edges where the back casing meets the front display. This was a positive for Samsung, as the jury found that the Galaxy Tab 10.1 line of tablets did not infringe the ’889 Patent.

Apple’s utility patent claims and the jury’s findings:

The ’381 Patent, commonly referred to as the “scrollback” or “rubberbanding” patent, describes how a background image (a textured grey image in iOS) is displayed when a user scrolls beyond the edge of a page, and how the page bounces back afterwards so that the edge of the page aligns with the edge of the display. The jury found that all of Samsung’s devices infringed the ’381 Patent.

The ’915 Patent, commonly referred to as the pinch-to-zoom patent, describes how a user can use to fingers, either moving closer together or further apart, to zoom in on a display. The jury found that most of Samsung’s devices infringe the ’915 patent.

The ’163 Patent, known as the tap-to-zoom patent, describes how a user tapping a point on the display will result in the display zooming in and centering around the tapped point. The jury found that many Samsung devices infringe the ’163 Patent.

Apple’s trade dress claims and the jury’s findings:

Trade dress falls under the trademark umbrella and refers to visual elements of a product or its packaging that denote its source of manufacture to consumers. The classic example of trade dress is the shape of a coke bottle, but other examples can include the circular Corvette tail lights and the Tiffany blue box. When a third-party “blurs” the consumer association of the mark with the producer, then that third-party is said to have diluted the trademark. The owner of a trademark need not register the mark to have legal protection (though there are benefits to registering), and in this case the documentation regarding Apple’s trade dress claims is limited to one registration, and that one registration applies to the iPhone 3G/3GS. The jury found that Samsung diluted the trade dress relating only to the iPhone 3G/3GS, and only with regard to certain devices.

Samsung’s patent claims and the jury’s findings:

Samsung alleged that Apple infringed two of its standard-essential patents – ’941 and ’516 – that relate to the transmission of data over a 3G network. The jury found that Apple did not infringe either patent.

Samsung also alleged that Apple infringed three of its utility patents: the ’460 Patent relating to the transmission of emails with or without embedded images from a camera phone, the ’893 Patent relating to the method used when switching between the camera and gallery display, and the ’711 Patent relating to displaying music playing in the background while multi-tasking on a device. The jury found that Apple did not infringe any of Samsung’s utility patents.

Damages award:

Apple was awarded just under $1.05 billion in damages. Samsung was awarded no damages.

Apple’s statement:

We are grateful to the jury for their service and for investing the time to listen to our story and we were thrilled to be able to finally tell it. The mountain of evidence presented during the trail showed that Samsung’s copying went far deeper than even we knew. The lawsuits between Apple and Samsung were about much more than patents or money. They were about values. At Apple, we value originality and innovation and pour our lives into making the best products on earth. We make these products to delight our customers, not for our competitors to flagrantly copy. We applaud the court for finding Samsung’s behavior willful and for sending a loud and clear message that stealing isn’t right.

Samsung’s statement:

Today’s verdict should not be viewed as a win for Apple, but as a loss for the American consumer. It will lead to fewer choices, less innovation, and potentially higher prices. It is unfortunate that patent law can be manipulated to give one company a monopoly over rectangles with rounded corners, or technology that is being improved every day by Samsung and other companies. Consumers have the right to choices, and they know what they are buying when they purchase Samsung products. This is not the final word in this case or in battles being waged in courts and tribunals around the world, some of which have already rejected many of Apple’s claims. Samsung will continue to innovate and offer choices for the consumer.

My thoughts on the verdict:

As I was following the jury verdict on Twitter and various liveblogs, I started to get a sinking feeling in my stomach as it became increasingly clear that the verdict was going to really be in Apple’s favor. I don’t really have a dog in the fight here – I like Apple’s products a lot, and I also like Android devices, though for full disclosure at the moment I am more into the latter – but more than anything, I love reading about new technology, and especially in the smartphone and tablet arena where technology is developing lightning-fast. While Apple has paved the way in some respects, all technology products – including those made by Apple – have benefited by the fierce competition we see in this growing area. Perhaps if Android-powered tablets didn’t finally begin to become viable options about a year ago, we wouldn’t see an iPad with an incredible 2048×1536 display resolution. Maybe if Android-powered devices didn’t adopt 4G-LTE early on, even at the expense of decent battery life, then the new iPhone and the current iPad would still be sitting back on 3G. Ditto for the next iPhone’s larger display size, as the larger HD displays found on some Android phones have really made the 3.5″ iPhone screen look outdated. The same can be said for iMessage, which came as a result of BlackBerry Messenger and is clearly better than SMS messaging, as well as for pull-down notifications. I’m not saying this to claim Android and BlackBerry is to thank for all innovation. Apple certainly deserves credit for taking us away from physical keyboards and moving towards touchscreens, incorporating media into our smartphones, and basically forcing so many mainstream companies to adopt the concept of an “app,” among other developments.

My point is that all this competition is good for innovation because it pushes the competition to improve their devices in order to stay competitive. Maybe Samsung came too close to iPhone elements in some of its earlier devices – the case for willful copying was pretty strong and those Samsung documents describing how Samsung phones should be more like iPhones didn’t gain it any sympathy – but to uphold the validity of patents describing a device with rounded corners and a flat, all-glass front display (the ’677 and ’087 Patents), a grid layout of apps and a dock at the bottom of the display (the ’305 Patent), or pinch- and tap-to-zoom functionality (the ’915 and ’163 Patents), both of which are integral to using touchscreen displays, seems to be asking for the innovation we currently see to slow down because of the lengths that competitors will now have to go to in order to avoid claims of infringement. In short, my criticism here is not with Samsung being punished for what seems like intentional copying; my issue is that the validation of patents that are so basic and are the result of the natural progression of an industry rather than true invention will really hurt future invention and innovation in the industry.

Looking forward:

I think it is a safe bet that Samsung will appeal this verdict. Before an appeal, there will be motions by Apple for triple damages based on Samsung’s willful infringement, injunctions banning sales of infringing devices, and for a judgement notwithstanding the jury verdict to set aside the finding that the Galaxy Tab 10.1 does not infringe an iPad design patent. There will also be motions by Samsung to toss out all jury verdicts that went against Samsung and to issue an order finding invalidity and/or non-infringement or a new trial. The next hearing in the case is scheduled for September 20 December 6.

I also think that this is not sounding the death knell for Android – newer versions of Android stray further from the look and feel of iOS, and newer devices look less like the iPhone. While arguments could be made against other Android devices, it seems to me that Samsung and its TouchWiz user interface was most blatant in trying to look and function like the iPhone. For that reason, I think there is still a bright future for Android. That being said, the validation of the tap-to-zoom and pinch-to-zoom patents does concern me since those are crucial elements to using a touchscreen device. [UPDATE: Apparently the pinch-to-zoom patent is very narrow and there are many work-arounds.]

For further reading, check out:
The New York Times
The Washington Post
CNET
Engadget
The Verge
FOSS Patents
AllThingsD

PSA: DO NOT buy expensive HDMI cables

This is not exactly news, but it’s a story worth telling…

Yesterday I went with a friend to Best Buy to help him pick out a TV for his new apartment. I was tagging along as an expert of sorts, if you think knowing that plasma sets have a wider viewing angle and darker blacks and LED sets are thinner and use less power makes me an expert. Anyway, after picking out a TV and Blu-ray Player, I told my friend not to spend a lot of money on HDMI cables because all HDMI cables with the same rating produce the same quality picture and sound. And by “same quality” I mean same exact quality, not “the difference is imperceptible to most people” or “the difference is not worth the price.” As HDMI carries a digital signal, it will either work or not work; and different cables, provided they all work, will not produce crisper audio or video. So we picked out a very inexpensive Dynex HDMI cable rated “High Speed with Ethernet” that was $10 for 4 feet. The salesman, who had been nice and knowledgeable up until this point, tried to upsell us to a “better” HDMI cable because “for a TV this size (50″) you will notice the difference in quality.” We went with the cheaper cable.

I was pretty sure of myself on this issue, but when I got home I double-checked my research.  I discovered that I was, in fact, correct: there is absolutely no difference in the picture or sound quality produced by cheap HDMI cables versus expensive HDMI cables, provided they both have the same rating (“High Speed” is best for 1080p video content). So a High Speed generic cable from Amazon or Monoprice produces the same result as a High Speed Monster cable. I researched several reputable websites, below, and every single one came to the same conclusion based both on science and on real-life performance. I was unable to find any websites that said otherwise. The only times where more expensive cables may be worth considering are long distance/in-wall installations and when the cables will be connected and disconnected often, both of which may require sturdier cables. But for a standard 4′, 6′, or 12′ cable, the consensus is pretty unanimous: cheap cables produce the exact same quality result as expensive cables. Here are some blurbs:

CNET: Why all HDMI cables are the same:

[The picture is] either exactly what it’s supposed to be, or it fails and looks like one of the images above [with white pixels known as "sparkles"]. In order for one HDMI cable to have “better picture quality” than another, it would imply that the final result between the source and display could somehow be different. It’s not possible. It’s either everything that was sent, or full of very visible errors (sparkles). The image cannot have more noise, or less resolution, worse color, or any other picture quality difference. The pixels can’t change. They can either be there (perfect, yay!) or not (nothing, errors, boo!).

All the claims about differences in picture quality are remnants of the analog days, which were barely valid then and not at all valid now. There is no way for different cables to create a different color temperature, change the contrast ratio, or anything else picture quality-wise.

Consumer Reports: HDMI cables: Once again, don’t spend more than you need to:

We’ve long been advocates of not paying for pricey cables, which often do little more than pad the pockets of the manufacturers that make them and the retailers that sell them…

So to be clear, unless you plan to regularly disconnect and reconnect components, where it might make sense to buy pricier, sturdier cables with more rugged connectors—or you require very long HDMI cable runs, more than 30 feet—any high-speed-rated cable should suffice. And don’t let a package or retail associate tell you otherwise.

Popular Mechanics: Brand-Name HDMI Cables: Are They Worth It?:

The fact is, HDMI is digital, meaning you either get the feed or you don’t. High prices and gimmicks like gold-plating don’t affect 1s and 0s. Our advice: Purchase your wiring online for cheap, and use the saved money to upgrade to a larger flat screen.”

Crutchfield: The Ins and Outs of HDMI:

You won’t see dramatic differences in picture quality among HDMI cables. Unlike analog video transmission, which can display varying degrees of picture quality, digital video transmission typically delivers a clean, clear picture or no picture at all.

In short, all High Speed HDMI cables should produce identical pictures and sound, so don’t let creative marketing or the hope to avoid “cheap” components talk you into spending more than $10 on an HDMI cable.

 

And on a lighter note, if you want a good laugh check out this $1,095 3.3′ HDMI cable at Best Buy.  The Customer Reviews are worth a read.

Follow-up: makers of Android devices still botching software updates

Last week I wrote an entry in the wake of Apple’s unveiling of the new iPad about how Google – the producer of the Android operating system – can learn from Apple’s product launches and software updates by essentially being faster and more definitive with the timeline of such events. More specifically, Android devices are often released without specifics regarding pricing and availability, and this really can cut into all the good – and free – press that the products may receive at launch. Google also receives press when it announces a new version of its Android operating system, but then it can take months for device manufacturers to even announce a release date, let alone actually release the update. I was pretty hard on Google, and rightly so in this case. I love what Google does (and if anyone from Google is reading this please feel free to contact me at your earliest convenience to schedule an interview), but I think that its product launches and software updates really do have a negative impact on its sales, especially with regard to customers who may not be technologically inclined and who are unwilling to stay updated on Android news.

Today is the one week anniversary of my entry, and in that one week we have seen statements from two major Android manufacturers – Samsung and HTC – regarding Ice Cream Sandwich updates, both of which support my criticism. And unless I hear otherwise, I am taking sole credit for forcing those statements through my editorial abilities (kidding).

Anyway, keep in mind that Google unveiled Android Ice Cream Sandwich on October 18, 2011.

Samsung:

After some confusion, Samsung released an official statement on March 13, 2012 regarding its Android update schedule for its flagship Galaxy SII line of devices as well as other Galaxy devices. The statement read, in part:

The upgrade will begin in European countries including Poland, Hungary, Sweden, as well as Korea today and gradually roll out to other markets. Android 4.0 ICS software upgrade for GALAXY Note, GALAXY SII LTE, GALAXY Tab 8.9 and 10.1 will follow soon.

Of importance is that Samsung did not commit to Ice Cream Sandwich release dates for any of its devices here in the United States. As if Samsung’s non-committal announcement wasn’t clear enough, it added this disclaimer at the bottom: “The availability and scheduling of the software update and specific models upgradable to Android 4.0 will vary by market and wireless carriers’ requirements.”

HTC:

HTC released an official statement on March 14, 2012 regarding Android updates. HTC did a great job identifying which devices (16 in total so far) would receive the update, but like Samsung, it fell short on the timeframe portion of the statement, which read as follows:

As for timing, we’re in the early stages of rolling out Android 4.0 for the HTC Sensation and HTC Sensation XE and upgrades will be more widely available in the next few weeks. The update for the HTC Sensation 4G and HTC Sensation XL will follow. Please note, once we start pushing out updates it will take time for all carriers in each country to get the update. We are working closely with our carrier partners to nail down update schedules for our other smartphones and will have more to share very soon.

In short, HTC did not commit to Ice Cream Sandwich release dates for any of its devices.

Motorola:

This week Motorola made minor revisions to its update timetable from a month ago, but as far as devices here in the United States go, the only information we have is what devices are scheduled for “Q2 2012,” “Q3 2012,” and what devices will have “further details to follow.” Most US devices – including the Droid RAZR, Droid RAZR Maxx, Droid Bionic, and the Droid zyboard tablet – fall into the latter category.

Like Samsung and HTC, Motorola has not committed to an Ice Cream Sandwich release schedule.

Nexus devices:

Also worth noting is that the Nexus S by Samsung, a device running “pure Google” (and not incorporating a customized user interface by Samsung) still has not received an Ice Cream Sandwich update or any information about an Ice Cream Sandwich update. According to Android Community, an update was release a month after Ice Cream Sandwich was announced, only to be pulled by Google almost immediately for stability issues, with no further information or timeline from Google in the five months since then. This is especially vexing because the update is handled directly by Google.

Nearly six months after Google unveiled Ice Cream Sandwich, we have no firm release dates for any products here in the US, with the exception of the wifi-only version of the Motorola Xoom tablet.

Effect on Android’s success:

The lack of updates and information about updates has several negative impacts on the Android platform, and it is more widespread than simply being a poor reflection on a single device manufacturer:

(1) It costs the entire Android platform valuable press that follows the unveiling of a new operating system, because Google is essentially promoting features that are not available no matter how much consumers love the features. So Google gets press, but then doesn’t find a way to convert that press into sales.

(2) Similarly, after receiving good press, if a potential customer goes to a store not only will they be unable to find devices with the new operating system, but devices running the previous version of Android will all of a sudden look very stale. It will be harder to convince a customer to buy that stale device with no update in sight.

(3) The lack of updates reduces the incentive of app makers to update their apps or create new apps to utilize the new features. This hurts the overall user experience when the new operating system becomes available.

(4) The lack of updates force customers to use an outdated operating system for much of that device’s life cycle. If Android is updated annually (which is longer than history would indicate), and it takes six months to update a device to the new operating system, that means that for every year a user has a specific device, six months of that year is spent waiting for the manufacturer to release an update.

(5) The lack of updates or even specific dates just makes Android look unprofessional and is very frustrating to customers.

Google’s options:

As I said last week, the real culprit here are the manufacturers, who really bear the responsibility of releasing updates. And the reason it takes so long is because each one of them has to take the time to add a proprietary custom user interface on top of the operating system in an effort to provide a better user experience, plus have the updates approved by various carriers. While that is understandable, it is not excusable and the manufacturers are really making Android and Google look bad. Android sales are fine, but I think that there is still some apprehension regarding Android by non-techies, and that apprehension plays right into Apple’s business model of producing devices that are simple and easy-to-use by everyone.

Google is a huge player in the technology world, and has the power to implement some changes to the status quo. First, while Android is open-source, Google can place restrictions on its use. For example, [I think] Google can place the requirement that manufacturers push updates to devices within a set period of time (two months sounds fair to me). Considering manufacturers have few other options when it comes to mobile operating systems, I think they would agree to that. They would do so possibly at the expense of more advanced user interface customization or by releasing fewer devices (both of which contribute to such a lengthy update process), but I don’t think that would hurt Android or the user experience. Another option is delaying the announcement of Android OS updates to allow time for manufacturers to prepare an update that would be released closer to the announcement. This method does have problems, mainly that by its open-source nature Android is available to everyone and by making the code available to everyone, even without a formal unveiling or announcement, the cat would be out the bag and we’d be back to square one. I still think there is room for a compromise somehow. A third option is making a version of stock Android available and downloadable right away, and then allowing Samsung, HTC, etc., to push customized updates at a later date. This would definitely light a fire under the manufacturers to release updates faster, although I am really unsure if doing this is even possible from a technical perspective. Finally, Google should at least get things right with the Nexus line of devices to show that any delays are caused by manufacturers and not Google.

In sum, the Android update process is a real headache and a sore spot for a company that really does great things and is dominant in the market, and while it is the fault of the manufacturers more than Google, Android is a Google product and Google can and should step in, even if it means ruffling a few manufacturers’ feathers, to try to make things run more smoothly.

Google Can Learn From Apple’s Product Launches and Software Updates


[Image courtesy of aoisora9x.]

There’s a war raging out there of Sean Avery vs. Martin Brodeur proportions: Android users vs. Apple users. I follow all sorts of technology blogs, including blogs that cover a broad range of topics and blogs that only cover Android or only cover Apple, and after yesterday’s iPad unveiling, comments sections everywhere seemed to be flooded with Android vs. Apple arguments.

Similarities and differences between Android and Apple:
Android and Apple (and really Apple’s iOS) are similar in some respects: They are both operating systems used on smartphones and tablets, they both have their own ecosystem of apps and content, and they are both very popular. They are also both involved in worldwide patent litigation, but that’s another story.

There are also some fundamental differences between the two. Android is an open-source operating system and it is used in devices made by a variety of manufacturers, and Google, the company behind Android, has relatively little control over how their operating system is used and when it is updated. There are benefits to the glut of companies using Android, as it has led to a market full of different devices, each with their own strengths. If you want a large screen or a small screen or a higher resolution screen, a stylus, a physical keyboard, 4G LTE, a better camera, an upgraded audio system, a larger battery, etc., you can find a device that best fits in with what you want. Each manufacturer also makes its own modifications to Android, so there is more variety in that respect too. For the technology-savvy, there are even more options with regard to tweaking Android’s software (through gaining root access). The downside is that there’s no sense of a governing body overseeing quality control so there’s a bit more of a “buyer beware” atmosphere with Android devices. Google also has very little oversight when it comes to when and how new devices are launched and when manufacturers update the software on existing devices. There are similar upsides and downsides to Android’s Market (which was recently re-branded as Google Play Store), which has limited review over what apps are made available. Another downside is that the number of Android devices and the frequency with which new devices are released can make choosing a device seem very complicated, and that complexity even got the attention of writers at SNL.

Apple’s strengths are largely a mirror image of Android’s weaknesses. Apple manufacturers devices and creates an operating system for those devices. As such, Apple has complete control over the end user experience. That is both a positive and a negative. It is a positive because when you buy an iPad or an iPhone, you know what to expect and it’s pretty hard to go drastically wrong. If you’re invested in Apple’s iTunes ecosystem, which many people are, buying a new device is pretty much a no-brainer; it just comes down to how much storage you want and what color, and whether to wait for the next generation device. The downside is that there are no real options so customers lose some of the freedom provided by Android.

What Google can learn from Apple:
Whether Android’s options or Apple’s simplicity is “better” is not my concern right now. My concern is with two areas in which Apple excels and Google needs serious improvement, and those two areas become apparent with every product launch.

Product Launches:
Apple has great product launches. Take yesterday’s iPad launch and October’s iPhone 4s launch: Apple announced the device and gave pricing and availability, with pre-orders starting either immediately or days later, and availability within two weeks of the launch. Apple also had its website immediately updated so that people interested in the new devices could check out the new features, and either pre-order the device immediately or make a mental note of the pre-order or release date. This allowed Apple to capitalize on the publicity – both in the press and by word of mouth – it received and turn it into sales.

Google is at a disadvantage when it comes to new product launches because, as I said above, the devices are made by independent manufacturers with little control by Google. But that is still no excuse. Take Google’s latest Nexus device, Galaxy Nexus by Samsung. Unlike other Android devices, a Nexus device is made through a collaboration of Google and the device manufacturer, Samsung in this case. If there is a device that Google has control over and can dictate the details of its launch, it is a Nexus device. Google and Samsung announced the Galaxy Nexus on October 19, 2011 alongside Android’s new Ice Cream Sandwich operating system. Carrier availability, pricing, and release dates were not revealed in the announcement. Verizon confirmed that it would carry the Galaxy Nexus two days later. Verizon, Samsung, and Google then fell silent for two months on availability – with other devices being announced and released in the interim – before finally announcing on the afternoon of December 14 that it would be available the following day.

In my opinion, the Galaxy Nexus had the best hardware of any smartphone at the time, and it came on the heels of an iPhone announcement that was considered underwhelming by many, and could have made some noise in the market. But unfortunately, Google announced the device, got some good press out of it, and then sat still for two months with regard to a US release date, hoping that consumers would remember the Nexus during that time and stay loyal despite all the other options – iPhone 4S included – that are there in stores and waiting to be purchased. That is no way to launch a product, and this kind of launch is not unusual for Android devices.

One of Apple’s strengths is that its devices are simple and approachable by people of all technical abilities, and that begins with the launch. Figuring out how to buy an Android phone or tablet after reading about the launch is a complicated process that often requires follow-ups for pricing and availability. There are some people who simply do not care enough to check back at a later date, and those people are customers Google risks passing on. Google can pass the buck in some cases, but there’s really no excuse, especially in the case of a Nexus device. Google has the power to dictate the terms of use for device manufacturers, and while Google clearly values openness, to conquer all sectors of the market it should really consider exercising more control over Android devices so that the launches are more polished and professional.

Software updates:
When Apple launches an iPhone or an iPad, they generally announce a software update and make it available that day and they announce what devices the update is compatible with. Google announced Ice Cream Sandwich back on October 14 alongside the Galaxy Nexus, and most Android devices still, nearly 5 months later, have not seen the update or even an announcement of when to expect the update. In some cases, it is still unclear whether a particular device will even be getting an update. Even the Samsung Nexus S, the predecessor to the Galaxy Nexus and is designed in part by Google’s engineers, took two months to get the Ice Cream Sandwich update. Like the issues with launches, the delay and uncertainty creates the need for Android owners to do legwork to figure out whether and when their device will see the update. To some people, like me, checking technology news is part of our daily routines. But to others, it is not. Those people want to be able to – and should be able to – easily determine when they can get the update they just read about. Imagine Apple announcing an operating system that includes iMessage and then giving no information on availability. It wouldn’t happen, but that is exactly what happens with Android updates. Android users are forced to go digging around on tech blogs and Twitter to get a “we are working to update our devices in the coming months…details to follow” kind of statement from their manufacturer, usually issued days or weeks after the update is announced, and then wait possibly months to hear more details. Some people are willing to do this as a trade-off for Android’s openness. But there is a sizeable segment of the smartphone and tablet markets who don’t care enough to follow tech blogs, and Google needs to do more to simplify things for those people.

Again, Google can pass the buck onto manufacturers, who choose to first modify software updates with custom user interfaces, or skins. Really, those manufacturers are the cause of the delay. But still, these are “Android devices” bearing the name of a Google product, and Google can and should place requirements on manufacturers about timeframe and announcements of updates for the sake of growing their product and appealing to more people. I am not a software engineer, but I have to think that these manufacturers can be faster and more forthright with updates if they were forced to be. Or, if it is really a six month process to customize the user interface, Google should at least put its foot down with Nexus devices and make sure those launches and updates go smoothly. I am in no way advocating eliminating the freedom found on Android devices that is lacking with Apple devices, but a little more control from Google wouldn’t hurt.

The FCC’s stance on cell phone jammers and government shutdown of cell phone service

I came across two tangentially related stories yesterday, both of which involve cell phone service and the FCC…

Cell phone jammers:
Forbes ran an article asking whether cell phone jammers are “the next big thing?” Cell phone jammers are devices that emit a frequency that disrupts cell phone service, and according to the article, people are using them on buses and trains in order to silence their fellow passengers. The article reports that this is going on in Philadelphia and New York City, and that users of the device see themselves as doing some sort of public service by restoring peace and quiet. According to the FCC, it is illegal to use or sell cell phone jammers in the United States.

I often take public transportation, and I’ve heard my share of people having obnoxiously loud and/or long and/or annoying conversations. And I wouldn’t be opposed to some kind of no talking on cell phone rule, although I doubt that’d really be enforceable (and have seen firsthand that it is not enforceable on New York City Express Buses). But to have random people taking the power to shut down cell phone service – and interfere with a service contract between an individual and their cell phone provider – without any notice and maybe without justification is really overstepping the bounds of decency and is responding to rudeness with even more rudeness. I hardly ever talk on my phone in public, and when I do it is usually just to make plans and then I hang up (I actually get self-conscious having a personal conversation when strangers can hear me). But someday I may have to receive an emergency phone call and I do not want some random stranger deciding whether I should receive it or not. Yes, there was a time before cell phones when I couldn’t receive such a call, but now cell phones are staples in our society. Also, I keep busy on the train reading news and social media while listening to music on headphones (in other words, I keep to myself), and unless there is a law or official rule prohibiting that, there is no reason why I should be disrupted and prevented from using my phone’s internet capabilities. Finally, taking public transportation – or doing anything in public for that matter – inherently involves interaction with other people, some of whom will be annoying. That’s just a fact of life, and something people have to learn to deal with, especially if they choose to take public transportation in large cities.

Hopefully Forbes is just being sensational and we do not start seeing cell phone jammers on buses and trains.

Public entities turning off power to cell towers to curtail protests:
Back in August, I talked about the San Francisco subway system shutting off power to cell towers for 3 hours to hinder an illegal protest. I said that I think there may be legal issues with doing this. Last December, the San Francisco subway system (known as BART – Bay Area Rapid Transit) adopted a policy that provided that they will only interrupt cell phone service when there is “strong evidence of imminent unlawful activity that threatens the safety of district passengers, employees and other members of the public.”

BART’s policy may not fly with the FCC, which is reviewing whether such a policy should be allowed and whether it has authority to regulate this issue. Here’s the FCC’s statement:

Our democracy, our society, and our safety all require communications networks that are available and open. Any interruption of wireless services raises serious legal and policy issues, and must meet a very high bar. The FCC, as the agency with oversight of our communications networks, is committed to preserving their availability and openness, and to harnessing communications technologies to protect the public.

Also of note for this issue and with regard to cell phone jammers is that the FCC says that 70% of 911 calls originate from cell phones, so cell phones are used for positive reasons, not just to organize illegal protests or have small talk.

I think in the end there will be a rule strictly limiting circumstances under which cell phone service can be interrupted. Cell phone use is too important to everyone from all walks of life to leave it up to government agencies to determine when and under what circumstances they can block cell phone service, and I think some guidance from the FCC would be really beneficial.

Chrome for Android Beta: Has potential but needs work.

Two days ago Google announced Chrome for Android, which is available in beta on Ice Cream Sandwich phones and tablets (depending on country) and which is expected to become the standard browser on all Android devices in the future. I must say, I like the stock browser on the Galaxy Nexus, and many tech blogs called it the best mobile browser ever just a few months ago. So for that reason, I was surprised to see Google release a Chrome browser that is aimed at replacing the stock Android browser, even though this was rumored for some time. But Google’s business plan is based on people using their services so that Google can sell ads, so it makes sense that they would want to create another reason for people with Android phones to use Google Chrome as their browser on their computers and vice versa, because the final result will be more Google searches, more gmail messages sent, more +1′s, and so forth.

As I said, I like the stock browser. It looks nice, works well, has a nice “request desktop site” feature, has tabs, provides a two-way sync of bookmarks between my phone and any Chrome browser that I am signed into, and does a great job of redirecting pages to their appropriate app (so a link to a YouTube video will open in the YouTube app, and a link to a map will open in the Google Maps app). But I am always happy to try new programs and applications, and this one received rave reviews, so I gave it a shot. Here’s what I think:

Good:

Speed: I haven’t timed page rendering, but Chrome seems just as fast if not faster than the stock browser. Google attributes this to preloading the top search results before the full search term is even entered. The stock browser has a similar function, but Chrome does a good job with it too.

Syncing: Syncing between different Chrome-using devices is probably Chrome for Android’s biggest selling point. Bookmarks between all devices are synchronized, and windows and tabs open on one device can be accessed by all devices. There is a feature that lets a user send a page from their desktop browser to their phone, and Chrome can preload that page immediately. Search results are also synced, so that if I typically search “New York Rangers” on my desktop browser, “New York Rangers” will appear as soon as I start typing the first few letters. There are plans to synchronize all stored passwords too, but that is not available yet. While synchronization of bookmarks already existed in the stock browser, Chrome for Android does it better and with more options.

Tabs: Chrome for Android has a really attractive tab layout that lets the user look through open tabs sort of like a deck of cards, and to switch tabs with a flick of the finger. Also, while the 16 tab limit on the stock browser has never been an issue for me, Chrome for Android has unlimited tabs.

Bad:

No Flash support: Adobe discontinued mobile Flash a few months ago and will not support it on Chrome for Android. However, the stock browser as well as many third-party browsers still support it, and some, although a dwindling number, of websites still use Flash. So that means that there will be some content on some websites that Chrome will not be able to display. In the quest to bring the desktop browsing experience to mobile devices, the absence of Flash in Chrome for Android is disappointing. Not necessarily a dealbreaker, but a big minus.

Appearance: Ice Cream Sandwich – at least the stock version on the Galaxy Nexus – has sort of a dark appearance. The stock browser fits in nicely, with a black search/address, bookmarks, and settings bar. Chrome for Android has a fixed grey bar at the top housing the omnibox, bookmarks, and settings menu, and that grey bar just does not look natural next to the pitch black status bar at the top of the phone. It’s minor, but details matter.

No “Request Desktop Site” feature: Not a big deal but is a nice feature that has come in handy for me in the past.

Ugly:

Interaction with other apps: I reset all my defaults to go to Chrome for Android, but this issue was a dealbreaker for me and made me go back to the stock browser. I tried and tried to figure out a way to fix this, but it did not work. Say you find a website that has embedded YouTube videos, like this blog entry. In the stock browser, videos can be played in the browser or using the YouTube app. When it’s in the YouTube app the navigation controls disappear and the video takes up the entire 4.65″ display, in HD, and looks beautiful. In Chrome for Android, the video sometimes can not play at all on the webpage, sometimes expands to varied degrees but never full-screen like in the app, and sometimes opens in the mobile YouTube site. It never opens a video using the YouTube app.

This also happens when searching for YouTube videos on Google. To test this, I searched for Samsung’s Galaxy Note Super Bowl commercial by searching Google for “Samsung Super Bowl youtube”. I then followed the links to the official Samsung video in each browser. The stock browser opened the video in HD in the YouTube app and Chrome for Android opened it on the mobile YouTube site. I then took screenshots in roughly the same place in the video, and the difference really is amazing:

The video using the YouTube app (top photo), which I have set to automatically open from the stock browser, takes up the entire screen, including the navigation menu, and is a much higher resolution than the video that opened using Chrome for Android. And when you’re done watching the video in the YouTube app, you can hit the back button and it’ll take you right back to the browser. Simple. I’ve had similar results with other apps – the stock browser can open maps and Google+ pages using the respective apps, while Chrome for Android only takes you to the mobile version of the respective sites. And these are all apps made by Google that I am testing!

I don’t mean to be hard on Google, as I appreciate their trying new things and releasing beta versions, and I am mindful that this is, in fact, a beta version. But the problem I am describing really hurts the browsing experience to the point that it outweighs the benefits of Chrome for Android. While I may be alone in finding this to be a problem (I have searched all over for similar complaints with no success), I really hope that Google addresses this with the next update.

All in all, Chrome for Android has potential. Once Google fixes a few things, I think that it definitely has what it takes to be the new Android browser. But until then, I’m sticking with the stock browser that came with my phone.

For other perspectives, check out The Verge, Engadget, Droid-Life, and TechCrunch.

Facebook Timeline is on its way, whether you like it or not.

Facebook is rolling out Timeline and there’s nothing you can do to stop it, short of closing your account.

Facebook Timeline is a new way of formatting Facebook profile pages. It has been optionally available for a while now, but Facebook is now making it mandatory. Facebook will gradually post announcements on the top of profile pages that the profile is being converted to the new Timeline format and a user will have up to 7 days to make whatever changes her or she wants before their newly-formatted Timeline is made visible to the public (or to whomever they currently allow to view their profile page).

I switched to Timeline a month or so ago, and I think it gives a much more cohesive picture of “me” than the previous design. To me, the three biggest changes are the way activity is formatted by date, the way events (like places I went, who I became friends with or what pages I liked) are grouped together, and the addition of a cover photo.

Currently, Facebook wall posts are pretty much just reverse chronological order (ie newest at the top). When it comes to finding out what friends are currently up to, the current format is sufficient. But if you want to see what a friend was doing two years ago when they graduated from a school/got married/had a child, you have to wade through pages and pages of wall posts to get to that date, or search for their photos, hoping that the photos you’re looking for are in a properly labeled album. Now, you can locate the year and month on a timeline on the right hand side of the page, and it will take you to that time period on their Timeline and show all of your friend’s activity. And speaking of milestone events, Timeline adds a prominent box (content on the Timeline is formatted in boxes rather than a list) for things like getting married or graduating from a school, and you can insert a picture to represent that event.

Depending on how accurate one wishes their timeline to be, especially the photos on their timeline, there is the ability to “change date” on their content so that it matches up with the time that the content was created rather than the time that it was posted. For example, when I first joined Facebook I posted pictures of friends and I from several years before joining, but on my Timeline they all appeared to be from the date that I posted them. So I changed the dates in order to have them in the corresponding sections of my Timeline.

Timeline also groups activity like added friends and liked pages by month, and this makes it easier to see a person’s friend activity if that’s what you’re looking for, or to skip over it if you’re looking for something else. Finally, Timeline has the space for a large “cover photo” that lets a user show his or her personality more – it can be a favorite landmark, a sunset, group of friends, etc.

In short, the current Facebook format is good for keeping current with friends. But Timeline provides a much more complete and easy to access view of both who we are now and who we were in the past, and I really don’t see a downside to the change.

It seems that whenever Facebook implements any kind of change, users do not welcome it and want the “old Facebook” back. It’s funny, actually, that Facebook really revolutionized the way we communicate by introducing a service that we didn’t even know we wanted, and that many Facebook users apparently welcome technological innovations (otherwise they’d still be using AOL profiles), yet they are so resistant to change and so distrusting of Facebook’s ability to create the best user experience possible.

A complaint I’ve heard is that Timeline makes it easier to find older, embarrassing pictures and posts that are currently buried. This is true, but that content is still there now and can be found, there are privacy settings available, and most importantly, everyone knows not to post embarrassing pictures to the internet. Another complaint I’ve heard is that the change is mandatory rather than optional. If Facebook never made changes mandatory, very few people would adopt them – of my 356 friends, only 58 of them have switched to Timeline despite it being optional for four months. So clearly if Facebook doesn’t make Timeline mandatory, it won’t catch on and we’ll have to deal with the lack of uniformity between profile pages that contributed to myspace’s demise. I think this is a case of Facebook knowing what we want more than we do.

Anyway, PC World has an interesting article chronicling changes to Facebook and the subsequent backlashes, and The Washington Post cites two surveys that show that nearly half of Facebook users do not want Timeline.