This week, I dove deeper into connecting JAICE with real email data. I focused on setting up the Google OAuth API consent process, which lets users securely give permission for the app to access their Gmail.
After getting the consent flow up and running, I tested it by having JAICE read the last 10 emails from a connected account. Seeing those show up on the home page was a big moment. It confirmed that the connection between our app and Google’s API is live and working properly.
I also added a feature for users who do not sign up directly with Google. Now, even if someone logs in using a regular email and password, they will still have the option to connect their Gmail account later to unlock the email-reading feature. That way, we are keeping things flexible for different types of users without forcing a single login method.
Overall, it is exciting to finally see JAICE starting to pull in real data from the outside world instead of just mock information. This step brings us closer to the AI email parsing features we have been planning since the beginning. Next week, we will start exploring how to analyze those emails using natural language processing so the app can identify job-related messages automatically and make tracking applications even smarter.