Vincenzo Visciano febbrile

I hereby claim:

• I am febbrile on github.
• I am febbrile (https://keybase.io/febbrile) on keybase.
• I have a public key ASAZe4KLbyLiLZIbwpAH3P_t_j6JH0UVmn4kia_Wb3Lk2Ao

To claim this, I am signing this object:

#Introduction

Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.

Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.

1. Understand the Chrome Architecture
2. Understand the Tabs-Extension Relationship
3. Picking the right interface for the job