Mapquest would beg to differ. To me, the interface was the killer feature for Maps. The data and trip planning functionality existed already on the web (as my print outs of driving routes in the late 90s can attest to). But being able to just scroll around a new city was amazing. Every other site required clicking through every North or West button with a round trip to the server.
It wasn’t until later that the satellite data and street view data became the next killer feature.
Well, let's hit up Yahoo! Maps to find the dopest route
I prefer MapQuest; (that's a good one, too)
Google Maps is the best; (true that;) double true!
So yeah, there was a third competitor-
https://www.searchenginewatch.com/2005/12/27/saturday-night-...
It popularized instant search, tagging and threading to such a degree you have clearly forgotten how elegant it was!
Product design is what something does, how it is structured and how it behaves to user interaction, _and_ how it appears, not just one of them. GMail was almost to email what the iPhone was to smartphones.
This is product design.
SUPERCUT Every "And loving it" in Get Smart (1965-1970)
If I remember my thoughts back when Gmail was launched I was clearly awestruck. Gmail showed what was possible to do if one had fast internet connection. All those little interactions enabled through ajax! I think it was the first time, atleast for me, a product was as good as a desktop app w.r.t interactions and usability.
For comparison, with Yahoo mail one had to hit compose button and wait for a few seconds for compose window to open up. With Gmail it was extremely nifty and nearly instantaneous because I think it was done clientside and Ajax.
[1] https://www.labnol.org/software/chrome-with-adobe-reader/201...
Chrome was dramatically faster than anything else (thanks to v8 which was a total revolution for js engines) and each tab crashed separately, with far better security than other browsers of the time. On Windows (and initially it was only on Windows) this was a big deal and so it displaced a huge proportion of the tech aware userbase very fast, permeating out from there.
The billboards were a thing but not what drove initial adoption to critical mass.
It was remarkable how quickly Chrome spread among the employees. Nothing to do with advertising -- just that it was so much faster and the whole app never crashed.
Whenever you heard someone cursing because their browser had crashed and they lost their tabs and immediate work, someone in the next cubicle would go, "why aren't you using Chrome?"
It really was that simple. It was all word of mouth.
They were then screamed at for being insufficiently "complacent" when they tried to fix those issues by changing the extension model.
Gmail was not actually a particularly elegant product design, it offered an escape from spam and manually managing your mailbox storage. Back then, if you used a free email experience, you were bombarded with banner ads, had 100MB of storage, and 99% of that was eaten by the spam sent directly to your inbox. Features are not product design.
Chrome might be a good exception, though. I still get the sense that it was primarily driven by inspired engineers. The reason for Chrome's success is probably not it's innovative design (it was it's performance), but it certainly was an incredible advance.