This is more compact, and better (IMHO) for larger displays at higher resolutions. There icons are selected and positioned based partially on IE parity, as well as a few are placed to introduce Firefox Advantages (new tab). Secondly they are spaced and catagorized appropriately (core navigation features, url bar, quick search, browser accessory features).
This is even more of a feature parity, and keeps the same concept. The big ‘advantage’ here is that the URL is more visible on smaller displays. Not sure if that long is needed. Most end users will only enter domains, not long url’s, so having that much space is mostly irrelevant.
The one button that would be cool to have with either is a second bookmark button to add the current page as a bookmark. That way even such a feature as bookmarking is visually represented easily in the interface.
Ideally I see three goals:
- Parity, reduce the learning curve for potential new users.
- Optimize screen real-estate. As much page space as possible. Minimize clutter.
- Make common features, and our ‘best parts’ visible. Such as the go button, quick search, as well as tabs (it’s a big feature).
End users aren’t learning key commands. That’s why they like GUI’s. So things like tabs become much more accessible as a button than as a menu option in the file menu. That’s obscure, and users don’t see it. But as a button it’s easily accessible.