QuirksBlog - Samsung
Part of Mobile.
For at least a year now I’ve held to the theory that the huge uptake in Chrome we’re seeing on the mobile web is mostly due to Samsung using its own version (based on Chromium 28) in its high-end smart devices from the Galaxy S4 on.
Yesterday Krijn started tweeting about mobile stats he had, and it turned out he was willing to share. He gave me data on about 100K mobile and tablet hits in Q2 on a project of his he’s worked on for
ages five years. I took the data gratefully and created a table.
Conclusion: Of Chrome users, 25% uses Samsung Chrome — this amounts to about 5% of all mobile visits to the site. On the one hand this proves that Samsung Chrome is a Thing — on the other hand I had expected a much higher percentage. So my theory isn’t right, but Samsung Chrome is still important.
Back in October 2010 I was very glad to receive a mail from the people behind the Samsung Dolfin browser, who turned out to work from Bangalore, India, asking for my cooperation in making it better and even offering to pay me for it. Unfortunately, by now it turns out that they’re a bunch of fucking assholes who don’t do as they promise. This is to serve as a warning to others NEVER to do business with them.
It should be noted that the engineers are perfectly all-right and reasonable and can easily be talked to. It’s the fucking bureaucratic assholes in "HR" that are the enemy who’ve fucked up my life in the last year or so.
Update: This post helped. I received my money, while I was convinced I'd never get it. So that's arranged now, and my dealings with SISO are at an end.
So Samsung won’t buy webOS after all. Instead, it is said to be interested in MeeGo, which Intel may want to sell. And HP will not sell the webOS team, which has been transferred from the PC division, which will be sold, to a strategy division, which will stay. Good, HP can use some strategy. As can Samsung.
That thud you heard? I fell because my head is spinning.
Back in early June I got a Samsung Wave that runs the brand-new bada OS and did some brief tests of the native Dolfin browser. In the past few days I’ve done some more extensive testing, and the verdict is in: good browser, well on the way to becoming excellent.
(Oh, and Dolfin ought not to be confused with Dolphin, which is a skin for Android WebKit.)
It’s Samsung’s philosophy that it will not compete in a market unless it belongs to the top three of that market. In the case of the mobile browsing market Samsung has succeeded: from nothing, Dolfin has become the third-best mobile browser in the world. Only iPhone and Android are better.
If you’re keeping track of the mobile browser landscape you should add Dolfin to your A-list. It’s easily good enough, and Samsung has big plans with the bada operating system. Somewhere in 2011 the installed base of Dolfin will pass that of Safari iPhone, and bada might even become a competitor to Android. (Samsung sure hopes so.)
I have updated my mobile pages with Dolfin data. (By the way, I also tested Android 2.2 while I was at it: few changes. There’s not a single difference with 2.1 in my great WebKit
On Thursday I got a Samsung bada test phone (the Wave) that runs the latest installment of Samsung WebKit, and of course I subjected it to various tests. The verdict is clear: excellent browser. As far as I’m concerned it ousts Opera Mobile from my personal top three.
Yesterday evening I returned from my fourth foreign trip this year. This time I went to
the Mobile World Congress,
the annual Barcelona-based get-together of the mobile industry, and I can tell you, it’s
This post gives an overview of announcements by mobile players that might be of interest
to web developers. There’s an incredible lot of it, too, because every single major mobile
player except Apple feels that MWC is the ultimate forum for major announcements.
If you know of more news, or have links to additional information, please leave a comment.
I was there because Vodafone had invited me to sit on a
panel in a technical “embedded
conference” about W3C Widgets and related technologies.
The concept can use some fine-tuning; I’m hoping to do some of that in the future.
I was there mainly to stress that the mobile browser situation is not as simple as it looks. THERE
IS NO WEBKIT ON MOBILE!
While I was at it I also invented guerilla browser testing.
When I reviewed the reactions to my There is no WebKit on Mobile post, it became pretty clear that few had expected its conclusion that there is no single WebKit on Mobile. Overall, it seemed that most people were pretty surprised, and hurried to revise their ideas of the mobile browser market. That was the point of the article, so I was happy.
(I’m still tinkering with the interface, by the way, and I didn’t have the time to finish my current revision. So the coloured bars are temporarily gone, but they’ll return in the future.)
Last week I spent a lot of time on WebKit in order to produce a comprehensive comparison of all WebKits. My purpose was to prove there is no “WebKit on Mobile,” and to gain some more insight in the complicated relations between the various WebKits.
Therefore I now present the Great WebKit Comparison Table. In it I compare 19 different WebKits on 27 tests.