I am very passionate about chrome extensions. I see what my co workers are doing, and create extensions to make their job easier. After making several extensions that talk with mingle, splunk and internal apis I'm curious to make another for the gmail api.
Each day I ride the vanpool an hour to work, then an hour back home. This is the time I will devote to the extension development. I will also spend a few hours in research and setup at home when online, where I will also gather sample responses to work with.
Suggested timeline:
- 2 days = published extension on chrome web store ( via link only, not searchable ) that has hard coded test data to demo the features. Hard coded test data is what the api previously responded with. This will serve to get feedback on the most fundamental features, and explore the most common scenarios. This will also serve to support development and testing offline ( in the vanpool )
- 4 days = working proof of concept : published extension that is using live data. It will have the desired functionality, but be quite ugly, and clunky, with extra steps to get stuff to work, such as copy and paste things here and there, or scroll around to find things. a you tube video will explain how to find each feature.
- 6 days = stuff works, and now looks pretty
- 7 days = final documentation.
I love making chrome extensions, and look forward to working with you.