2020_CSE_03: Week 08

 Week 8: (31/05/2021)

During our 1st review to the department we had specified that the "@" and "at" recognition was a bit challenging, so we modified the speech input method in such a way that if the user says the username part of the email address and upon ending his speech input the extension would append "@gmail.com" to the text.

But what about other email clients? We are looking into how to interface with the user if he wants to change the client name of the email address. We also might change this whole method so be tuned in for that.

 We also looked into gmail.js, A package which can used as an alternative to Gmail APIs for all CRUD operations, but we found few drawbacks such as

  • It mainly requires the gmail window to be open for the functioning of the extension
  • Slows down the load time of gmail window
  • If you have too many functions specified you may get your gmail account suspended ( speaking from experience, do not recommend that, the account did get restored anyway)

We got these drawbacks as of now, upon looking at the issues specified under their github repo it has not been confidence inspiring to use this. Nevertheless we will be exploring all possibilities to get the best output at the end of the day so we are not going to rule it out as of now.


Comments

  1. Ram P Rustagi31 May 2021 at 04:25

    you can learn from gmail.js package and how it has been designed. You can take required input from it and implement it in your own way keeping the overhead to minimum.

    ReplyDelete

Post a Comment

Popular posts from this blog

2020_CSE_03 Week 09

 Week 09(07/06/21): We found some challenges in regards to calling multiple Gmail APIs directly in an extension, so for now we have resorted to using a localhost server to call these APIs and run all the important functionality of our project on it till we figure out how we can resort to calling multiple APIs in the extension. We also made a mock-up UI of our prototype which has a simple layout. One of the main intention of this UI is to make the extension screen-reader friendly as well. We were able to create a compose window using Gmail API from which mails can be sent, further all of it will be revamped with the UI and will see how we can go further from there We will be testing out a few test cases in the coming weeks like: Checking how to access user created folder in gmail. To find a solution as to where the contents of the mail can be stored if the user loses internet connection before sending the mail.  
Read more

2020_CSE_03 BLOGS

Welcome to our blog series where we share our journey in building a chrome web browser extension which can read, compose and organize a user’s Gmail inbox all controlled through his voice. We will be updating our findings and progress every 2 weeks through this series.  x So what exactly are we working on? The plan is simple, over the course of next few months we are aiming to develop a chrome extension which acts as a Voice Assistant for your Gmail account. Our main goal is to make it so user friendly that even visually blind users can access their Gmail accounts without any hassle. Why? As we all are witnessing the importance of technology and it’s services during the pandemic, we realized that many of the services available today mainly rely on an email client for communication of important information, thus many visually impaired users face a challenging time in accessing these technologies in their day to day life. In an attempt to make the internet a more accessible place, w...
Read more

2020_CSE_03 WEEK 10

 Week 10(14/06/2021) We integrated the UI with the part that was running on localhost which was retrieving emails and deployed it on replit. We also added a few voice commands such that total mail count and unread mail count is given as a voice output. We did research on colors such that someone with color blindness would also be able to use our interface easily and differentiate elements   So far we have a UI which can be comforting to color blind users, retrieval of 10 emails from the user's inbox and a voice output of unread emails count of the user.  Challenges: When a voice command is given the output is repeated twice and we are finding it a bit challenging while getting voice outputs of retrieved emails.
Read more