Help me choose which framework to develop extensions for google chrome?

manhtv157

Newbie
Joined
Nov 12, 2012
Messages
5
Reaction score
0
Hello seniors
I'm learning about writing extensions for chrome. Can anyone tell me which framework to choose and how to think about code layout?
Thank you!
 
Just use plain Javascript and html? I would recommend first checking an existing extension and seeing how it works. To do that, download the crx file and change the extension to zip. You should be able to see the codebase once you unzip the file.

Yes but theoratically, you could also use react or something. It depends on what the extension does.
 
Just use plain Javascript and html? I would recommend first checking an existing extension and seeing how it works. To do that, download the crx file and change the extension to zip. You should be able to see the codebase once you unzip the file.

Yes but theoratically, you could also use react or something. It depends on what the extension does.
I want to choose a standard framework to increase scalability and be able to guide my team members to code together. Tools are for personal and non-commercial use.
How to download the crx file of an existing extension?
 
I want to choose a standard framework to increase scalability and be able to guide my team members to code together. Tools are for personal and non-commercial use.
How to download the crx file of an existing extension?
As for downloading a crx, just google "download crx". There are multiple such websites.
As for scalability, it also depends. Most of the big extensions do not rely only on client side code. They rather rely on the APIs for data display and mutation. That's one way to prevent users from reverse engineering your extension as well.

In terms of scalability of code, I believe in not complicating things as long as it is not needed. You can always rewrite everything. First make it work, then make it right. Don't worry about writing the "best code" in the beginning.
 
As for downloading a crx, just google "download crx". There are multiple such websites.
As for scalability, it also depends. Most of the big extensions do not rely only on client side code. They rather rely on the APIs for data display and mutation. That's one way to prevent users from reverse engineering your extension as well.

In terms of scalability of code, I believe in not complicating things as long as it is not needed. You can always rewrite everything. First make it work, then make it right. Don't worry about writing the "best code" in the beginning.
Thanks you so much
 
Back
Top