Roadmap

DONE

• Guest user login (with no DB storage or authentication)

• Chartroom built using the chrome api to load on the front end VS a loaded iFrame

• Displays an in line notification when another user:

  • typing
  • joins a room
  • leaves a room

• Implemented notification functionality

• Moved front end verification to servers

TODO

Google Login

We should take advantage of Google's One tap sign-up and automatic sign-in in api. Google One Tap Identity

With one tap sign-up, users are prompted to create an account with a dialog that's in line with your page's content, so they're never taken out of context by a sign-up page. With just one tap, they get a secure, token-based, passwordless account with your service.

Returning users are signed in automatically, even when they switch devices or platforms, or after their session expires. There are 3 basic steps

• On every page a user can sign in to, if the user isn't already signed in, call googleyolo.retrieve() to sign the user in automatically if possible.
• On every page where signing in might be useful, or is required to proceed, if the user can't be automatically signed in because googleyolo.retrieve() failed, call googleyolo.hint() to prompt the user to choose a Google Account to sign up with.
• On your auth back end, add the ability validate ID tokens and to use them to create new accounts.

Extension Settings

• Connect settings interface actions to 'chrome.storage' ex. When a user enables notifications the preference is automatically stored

• Add functionality for

  • notifications
  • blacklisted domains
  • pop-up box resizing

• Persist the state of the drop down so the app resumes where you left off

Notifications

As of now notifications are triggered with an '@username' message. This is a proof of concept. We need to add the logic of checking the servers user name array to see that the user exists

Channels

• We need to port over the code from Chaddon 0.1.0 which loads a new chat room based on the current users url.
  • chrome api has a built in function called 'getCurrent' which retrieves the active tab url Developer Chrome: getCurrent method

Design

Modify the different screens (ex. login, chat box) to display information more comfortably

Cross browser compatability

For the most part Chromes API is compatible with Firefox. We will address computability errors as they arise