But what value is that, over the website?
1. Have your application look and act like a standalone application rather than a webpage—Chrome tried to support this with application shortcuts (or whatever they were called), but it never worked well enough
2. Give your application access to native APIs and capabilities that you can't get through the browser, like direct filesystem access
That sounds suspiciously like "properly adheres to the native OS's conventions", the lack of which is the #1 criticism of electron.
If the browsers change in a way that makes the website not work, the electron application will still work.