The background for this question is that I’ve been working on what I’d call a tool in which a user can build modules that they can later run. It started out as a small web page and has grown over the last year into something that more closely resembles a desktop application; but, at this point, is still just a set of html, css, and js files.
I considered using something like electron to package it as an installable desktop application, but I didn’t like that approach and thought it better to stick to something like a progressive web app because everything is done off-line.
Because I wanted to access APIs that are available only to web extensions, I’ve been reading a bit on MDN web docs about them and that has led me to wonder and become confused about the differences between a PWA and a browser extension that uses the extension pages to run its own pages/program, as opposed to altering how other web pages are viewed and used in the browser, etcetera?
If one wants their app to work off-line and behave like a desktop app, what is the downside to making it a browser extension? I came across more information on PWAs than on browser extensions, giving the impression that an extension shouldn’t be used in this manner.
It appears that the upside includes access to more APIs, it installs into the browser with its own icon, and the window of the extension pages can be altered such that it doesn’t appear to be running inside a browser.
I’m new to stackoverflow and have noticed that questions are sometimes closed because they are viewed as debatable or seeking opinions rather than facts. So, to be more specific, could you please help me to understand the pros and cons of each, and/or the decision points that should be considered in choosing an approach? Thank you.