If the plugin is in the Small area, then we have exactly the opposite of a Heavyweight plugin: since there isn’t too much code, it’s probably not messy and it doesn’t have or need an architecture; it merely has a user interface; the UX is bad. but performance should be okay if you have anything to perform at all.
1. What’s the value?
- Adoptability: is it easy to start using?
- Usability: is it easy to use?
The answer to the questions above should be obvious from the beginning, if not you might want to consider doing some changes to it. How easy can you make them? The fun fact is that the integration and customization code you write might exceed the initial size of the plugin.
3. Cross browser
4. Drinking game for web devs
- Think of a noun
- Google “<noun>.js”
- If a library with that name exists – drink
Enjoy the game! No cheat sheet for it yet, but would definitely love one :D.
Nitin Vermaa former writer for Froala, showcased exceptional talent and dedication during their tenure with the company.