But usually when you layer code on top of something else, doesn't that slow things down?
No, the way it works is that if you look at the Chromium code, one of the nice things about that code is that it has a multi-process architecture -- and that allows us to have the multi-process as one process independent from the rest.
Now we did this with Opera as well. We had a layer of code that was common across platforms and in this case we have just chosen web-technology as the layer. The benefit is that it is able to work a lot more efficiently. If you look at the code there is a lot more moving around so that the browser has become very good at running code.
It didn't do that in the past but browsers are now are very capable of running code -- and so having the browser run on top of the browser makes a lot of sense.
So this must be going down very well with the developer community?
Yes, people like that. There are a lot of technical people who love the fact that we are taking this technical approach. Now it's a new approach, it is a different approach, and the fact that we are working very efficiently -- a lot of people like that.
What's new for you?
We always have new releases coming out, but right now it is more about talking with people. We have had 1.0., 1.1, and there is a 1.2 coming out shortly.
There are a few nice things coming with 1.2. Things like the editable gestures [the ability to take a hand-drawn shape that can then be edited on-screen], or tab control and so on. It is all details but for some people, those are the things that make all the difference.
Are you funded by VC?
There is no VC funding. It is personal funding.
Are you going to keep it that way, without VCs?
We have had a lot of VCs come around. And good VCs, people who know what they are talking about. We are flattered by the fact that they like what we are doing, but we don't want to go public, we don't want an exit, we just want to build a great browser. So it's not financially motivated, it is motivated by building a great product.
This sounds like a campaign or, perhaps, a labour of love?
It is a question of design philosophy. There is a feeling these days with all the other browsers, of 'Let's make something great that works for the masses. Let's not do individual requirements, let's do standardised products that upgrade'.
But when you start to use them, they don't necessarily do what you as a user want. With us we take the view, let's build a browser for our friends and that's kind of what this is all about.
We are building a browser for our friends, which means that we listen to our friends. This means that if people want a certain feature, a certain option, then we have a slogan, 'when in doubt, make it an option'.
What it means is that we all have different opinions and we have our users asking for different things. Typically, what happens is that you will have a designer who says, 'you know what, this breaks my design'. And then we will say, 'you know what, we want to give the users what they want and if this is something they want, we will do that'. So the users get what they want and your work as a designer is to make sure that it still looks good.
So it's a democracy?
What we are saying is that there is no one way to do things. It isn't like the tabs have to be at the front. If people want it on the left or the right, it is a reasonable request. So we put in the code how they want it and the people are happy.
It sounds like the opposite approach to companies that say 'you will have it this way because it has always been this way and if you don't like it, tough'.
Basically. There has been a trend where it is 'our way or the highway' and our approach is the opposite. Every single user deserves their feature, their application, and we find a lot of people like that.
A lot of the way we work is working closely with our users and it is not one or two, it is a lot of users. And we have a lot of volunteers too. These are people we communicate with on a daily basis. They are in our chat track and they have access to our tracking system.
The second level after that is the community and that is tens of thousands of users -- and a lot of them provide feedback.
In addition to that we also take feedback on Facebook and Twitter and a lot of different channels.
How about the US market? That is often a big channel for a European company.
We actually do pretty well. The US is our number one country now. We didn't have that at Opera, so that is a difference. We have other countries doing well, like Japan and then Russia, which was always a big Opera user.
What's next for Vivaldi? What's on your personal wish list?
There are a lot of details but I suppose mail is the big one. Our client will work with Gmail and all the other [email clients]. The problem that a lot of us have is that we all have multiple mail accounts.
Now there are different ways that you can deal with that. You can have the different mails fall into one account or you can have each and every one of them handled separately, which is a chore.
Our goal is to have one client and you can go into that one client and deal with all the email. This is one of the features that we really loved in Opera. People really loved the fact that we had a mail client with an underlying database and it made it very quick to find any mail contact. And dealing with multiple accounts is easy, and you could have automatic sorting so you don't spend your time sorting your mail into folders. It takes away a lot of the chore.
How long before we see that in Vivaldi?
It's on the way. We have a number of people using it but it is not at a level where it is ready to be shown to the public.
Read more about Vivaldi and Opera