Sending email as your users: why I ditched Gmail OAuth for App Passwords

I'm building RecruiterReach, a tool that helps job seekers email the recruiter behind a job posting — sent from the user's own Gmail, so replies come back to them. That "send as the user" requirement turned into the most annoying technical decision of the whole project. Here's what I learned, in case it saves you the same detour. The obvious path: Gmail API + OAuth The "correct" way to send email on a user's behalf is the Gmail API with the gmail.send OAuth scope. I built it, it worke...