-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meeting Google's Branding Compliance Requirement #3153
Comments
I'll check with our designer and come back to this. |
any luck? |
Created a PR |
Adding to this that despite the changes we are still facing issues related to Google Drive brand guidelines. I think the issue is that the white drive icon is not official and in breach of their brand guidelines. Is there a way to provide alternate icons that do meet Google Drives brand guidelines? |
Is there any potential timescale on making this change? We're completely blocked by this at the moment. |
There is a branch but not yet a PR. We'll try to wrap it up today. Preview: |
I see this is now merged which is great, when will it show up in a release we can use? |
Released :) |
Hi Uppy team,
First of all, thank you for the Uppy library, it has helped us implement our uploader with ease.
We currently let users upload from local disk, box, dropbox, and google drive, The first three works just fine, but Google has given us some issues. We requested to have our app verified by Google, and they responded with the following email.
`Hi,
Unfortunately, since the button initiates the OAuth Sign-in process, it is required to comply with the Google sign-in branding guidelines. Please update any links and/or buttons on your application that initiate the OAuth Sign-in process to comply with our policies.
Once you have made the appropriate updates to your site and/or your OAuth Consent Screen, please reply directly to this email so that we may continue with the verification process.
Please see attached screenshot for reference.
Note: Failure to satisfy/provide the preceding information might result in a rejection of your request. To avoid this outcome, update the applicable information in your request to meet our requirements.
If you have any other questions, you can read the OAuth Application Verification FAQ or reply directly to this email.
Thanks,
The Google Cloud Trust & Safety Team`
Here's the attachments they sent:
And the link they gave:
https://google.com/url?&q=http%3A%2F%2Fdevelopers.google.com%2Fidentity%2Fbranding-guidelines%23top_of_page
And I suspect this section as well even though it was not in the screenshot they sent:
After reading their guidelines, my understanding is that these need to use their "G" icon in order to meet the requirement, and I don't think Uppy currently supports customization to these icons. Although I can probably do something hacky on my end to change these icons, I think it's best for the sake of other developers if you guys can modify the icons to meet Google's (overly strict?) guidelines.
P.S.(rant) I also don't see how the Google Drive triangle icon ISN'T part of their brand.
The text was updated successfully, but these errors were encountered: