Original Summary

If your product reads Gmail (or Drive, or anything with a "restricted" Google scope), this will hit you, and nobody warned me early enough. Until Google verifies your OAuth app, every user sees "Google hasn't verified this app" and has to click Advanced to get past it. Unverified apps are capped at 100 users in total , for the life of the project, not per month. Restricted Gmail scopes also need a third-party security assessment, which takes weeks and isn't free. What I'd do differently: submit for verification the week you pick your scopes, not the week you launch. Write the privacy policy and the scope justification first, because Google reads both line by line. And keep the scope list minimal; every extra scope is another round of questions. How it shaped my launch: I'm opening early access with 30 licences instead of an open launch, so the 100-user cap covers paying users, testers and people with several accounts. Disclosure: I'm the developer of Briskmail, a native Mac Gmail client. That's the product that ran into this.   submitted by   /u/3-Chengz [link]   [comments]

  • 情报分类：综合情报
  • 分类依据：内容未命中明确的垂直分类规则，归入综合情报
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/10/17 05:49:42