Covers the why, how, and when of the various stages of development of Vivaldi browser.
We recently made significant performance improvements to Vivaldi browser that are independent of the Chromium code. Here’s how we did it.
While some browsers cut down on functionality and options, we expand those in order to give you more control and better productivity. Here’s what inspired us to redesign Vivaldi’s menu.
Sync support was considered one of the most critical features for our Android release. And keeping the synced data safe was a must. Here we explain how we implemented Sync on Android.
We thought we’d put this question to the Android team who’ve been working hard to bring you Vivaldi’s first mobile version.
Here’s how we built Vivaldi to run on the latest Chromium code while at the same time creating our own alternatives to what Google has provided in their web browser core on Android.
From “Flash is dead” to “Flash will never die” our users are split over the virtues of the Flash technology. Even though it’s being phased out, we decided to make it an option – while it’s still here.
Starting with the upcoming Stable release, we will change the way we count our users, gradually dropping the use of the unique ID for user counting.
Vivaldi developer Petter Nilsen who made possible the Razer Chroma integration, reveals how it came about.
A recent addition to the team, developer Trond Kjetil reflects on switching to Vivaldi and working on older bits of code to improve performance.
Remember when we introduced the new Application Icon way back in Vivaldi 1.11? It was high time for all the little icons in our interface to get refined.
For the first time in Vivaldi history, a button can exist in more than one location. Here’s how we’ve been able to achieve this.
Vivaldi is the first browser to introduce auto tab stacking, but did you know that it owes its life to a good karma bug?