what option should i pick for developing a chrome extensions ?
i didn't build chrome extension before, and after some research i find that i can build chrome extensions with react, vue or whatever framework i can work with with some configuration instead of using vanilla javascript, here's what my app should look like: the app will be shown by default when you open a new tab it's just a map (take the full screen width / height) with many markers, the markers status will change every time the app receive data from the backend (socket.io) the downside of using vanilla js is that change may slow the "dom" that's why i think about using React to change what should be change instead of re-render the whole "dom", maybe i'm wrong i want to hear your thoughts !!
I would suggest that you go with whatever you are comfortable with. Do it with react if you believe react will do the job. Don't think too much. For your use case, I believe React or any other framework you like will be perfect since its new tab page.
I use vanilla js for tryhoverify.com because it offers more control over your app and is faster than any framework.
The chrome extension for bugshare.io was originally built using vanilla js, then after a year I ported it to using vue.js. So just pick what you know and keep moving
There is no right or wrong answer so pick what you are comfortable with. The only thing that seems like a solid concept based on what i have seen is abstracting the core extension logic from the browser. This gives you the ability to port it to multiple browsers with the only part needing to change being the code to hook into the browser.
@nblackburn what you mean by logic abstraction ? did you mean writing the core extension logic that can be shared to multiple browsers without including specific browser Apis ?
Please sign in to leave a comment.