Two big ones I can think of:

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

But it doesn’t act like an application. Most of the OS right click services, keyboard shortcuts, menu items are all missing. Accessibility tools don’t work.

It doesn't feel like one either. It feels like a shitty web page, and it costs 500$ to run. I can run apps in python and they don't feel the same way, never mind native.

>1. Have your application look and act like a standalone application rather than a webpage

That sounds suspiciously like "properly adheres to the native OS's conventions", the lack of which is the #1 criticism of electron.

They are talking in the context of games though, for which there aren’t such strong conventions, besides lives in your applications folder, and runs full screen.

“ because browsers change over time and electron helps you get a working offline snapshot of something you created.”

If the browsers change in a way that makes the website not work, the electron application will still work.

This makes sense from the perspective of the individual developer, but it's also a sad reflection of the sorry state of technology that the only way to be sure a website will work in 5 years is by shipping your own copy of the browser.

> which is nice because browsers change over time and electron helps you get a working offline snapshot of something you created.