Using Electron vs. Offline HTML5 for an offline application -
when looking electron , offline html5, have found difficult make decision between 1 use project.
assuming user have go website download electron application, , have go same website offline html5 loaded, pros , cons between using 1 on other?
some think of:
- offline html5 can updated without user consciously updating application making user go online page again.
- electron eliminate need code around multiple browser/browser version dependencies , quirks
it depends on exact requirements. following list of came with:
- electron supports module system (i.e.
require
) both in main , renderer processes. - electron provides access os apis (e.g.
fs
). without such many node modules not work in js runtime of browser (e.g.ip
). - updating app electron easy sending http request. (or better described here)
- an html 5 offline app requires browser , user might give ie6.
- electron integrates native desktop environment (see dialog, power-save-blocker, shell or app examples)
- electron enhances of html5 apis such
file
api - electron lets modify default behavior of underlying chromium. example intercept urls
file
scheme , modify them on fly*.
in short if want app have native integration , act deterministic (i.e. no browser quirks) suggest choosing electron.
*
electron-jade
example takes use of protocol
api compile files ending .jade
on fly without need prior compilation. disclaimer: developer of electron-jade
.
Comments
Post a Comment