Google’s Chrome browser has just reached a major milestone, hitting its 50th release.
For Google, it’s a moment for positive reflection. To emphasize Chrome’s might, the company points to the browser’s 771 billion page loads per month, 1 billion monthly active mobile users, 9.1 billion auto-filled forms, and 145 million malicious webpages averted. One might also point to Chrome’s ever-growing usage, accounting for 47 percent of all worldwide pageviews, including mobile, according to StatCounter.
Indeed, Chrome has become an indispensable tool for many web users, and has served as a leader in the browser world. It introduced the idea of limiting menu clutter around actual webpages, and popularized the syncing of bookmarks, tabs, and browser history across devices. After all these years, it remains PCWorld’s most highly-recommended web browser.
Yet for all the good Chrome has done, Google’s browser now stands at a crossroads. Aside from just another way to browse the Internet, it’s unclear exactly what Google wants Chrome to be.
Browser or platform?
Those advantages are less pronounced now. Nearly every other browser has embraced restraint with their own chrome, and Chrome is no longer the clear victor in benchmarks. Meanwhile, the ever-increasing demands of the modern web have given Chrome a reputation for being a resource hog and a battery killer, even if other browsers aren’t markedly better.
A few years after Chrome launched, Google started broadening its ambitions. It introduced the Chrome Web Store, and eventually the concept of native Chrome apps with offline functionality. A Chrome app launcher followed, along with push notifications from web services and Google Now. These new features were supposed to turn Chrome into a platform-within-a-platform on Windows and Mac, while making Chrome OS into a legitimate desktop operating system.
But over the last year, Google has dismantled or abandoned many of those efforts. The Chrome notification center is now dead on Windows and Mac, as Google considers embracing native notifications on those platforms. The Chrome Web Store fell into disrepair years ago, and Google has shown little interest in cleaning it up. The Chrome app launcher got nixed on Windows, Mac, and Linux because no one was using it.
As for Chrome OS, its future is far from certain. Although the platform has traction in the education world, and probably isn’t going away, a merged Chrome-Android operating system for consumers seems likely.
Amid all these retrenchments, Chrome has introduced no big noteworthy features to its desktop browser. The most interesting browser developments are instead happening on alternatives such as Microsoft Edge (with its page annotation and embedded Cortana assistant) and Vivaldi (with its web panels and tab stacking).
Google may arguably be more interested in mobile Chrome, now that smartphone usage has eclipsed the desktop. But in a world of apps, Facebook, and Instant Articles, the idea that users will spend significant amounts of time in a browser seems quaint. Perhaps that’s why Google’s 1 billion mobile user statistic is on a monthly basis, not a daily one.
So as Google celebrates Chrome’s 50th release, it should also ask itself what Chrome is now trying to accomplish. Will it recommit to its original focus on speed and simplicity, or will it try to innovate with new features? Is Chrome a platform unto itself, or just a really good way to access webpages? Are the fates of the desktop and mobile versions intertwined, or are they separate? If Google can’t answer those questions, version 100 might not be so celebratory.