Mordral

Not really, but i just do want to make sure that i am using a browser which is not running into the danger that it is suddenly no more because of the "mother project" aka Google messing around with their code.

If you think you can survive and have the knowledge to handle such a possible difficult situation, then it is a good thing.

I understand now. But i have one last question if it is allowed, as Google always removes different so called API - What would happen if they would remove a significiant one you are using for creating Vivaldi?

Could you survive such an impact? For example you also have been unable to save the old Flash plugins, if Google would remove a vital component which you are needing, that would even more complicated than the Flash stuff.

Chrome user here. I know many users of Chrome are interested in the App you have created.

But why bundling it with an own modified Chromium version and not offering it over the Chromium app store? We already have Chrome and Google creates the most error free variant.

Watched few threads of your boards, seems you have tons of bugs, so why making things that complicated? Is there a technical reason for not offering it over the Google app store?

And why not fully Open Source?

Thanks and greetings!

You misunderstood me as it seems. I am not talking about a web app. There are different kinds of apps, for example Offline Chrome apps.

As i see in the Vivaldi task manager you are using the webview process.

Would it really be limiting to split off the Vivaldi app from Chromium and offer it as Offline app in the Chrome webstore?

Not the most brightest person in technology aspects, but you are clearly rendering the UI with an app.

So, to narrow the question down: What is the difference between the App Vivaldi and a normal offline Google app? Is there really such a big difference technology wise that you can not offer it as additional stand-alone variant?