How is this different from doing Chrome > More Tools > Create Shortcut > Open as Window ?

[dzg]

How is this different from doing Chrome > More Tools > Create Shortcut > Open as Window ?
Thanks

[dzg]

Heh, I asked ai ... 

Nativefier and creating a desktop shortcut for a web app in Chrome are two different ways to create standalone apps from web apps. Here are the main differences:

• Nativefier packages the web app into an executable app using Electron, so it doesn't require having Chrome open to run the app. The desktop shortcut approach still requires having Chrome open.
• Nativefier apps can have custom icons, names, etc. The Chrome shortcut approach doesn't allow customizing the app name/icon.
• Nativefier lets you configure settings like disabling web security, enabling node integration, etc. The Chrome shortcut method doesn't allow configuring those kinds of settings.
• Nativefier apps will have access to Node.js APIs since they use Electron under the hood. The Chrome shortcut apps are just a shortcut to a web page and don't have access to Node.js.
• Nativefier generates a standalone executable for the current platform. The Chrome shortcut only works on the machine it was created on.

So in summary, Nativefier creates a more integrated, customizable app that doesn't depend on Chrome being open. The Chrome shortcut approach is faster and simpler but provides less flexibility and integration.

Does this about sum it up?

[TheCleric]

That seems like a fair summary to me.

[kobaltz]

Another use case that I use nativefier on is with my kids. We have browsers blocked on their profile, but will use nativefier for any websites that we want to let them have access to. It's not a perfect solution, but it works really well for us.