Google Drive hates developers now

Summary

In this video, the developer from Panic discusses their tumultuous relationship with Google Drive, detailing the challenges faced in maintaining access for their app, Transmit. After a series of lengthy security assessments and changing requirements, they ultimately decide against renewing access due to the burden it places on their team and users. The speaker highlights the broader implications for developers, illustrating the risks associated with Google’s policies, which can jeopardize livelihoods. Instead, they plan to focus on alternative features, expressing hope for future improvements in Google's security measures that could better support small software companies.

The video is abnormal, and we are working hard to fix it.
Please replace the link and try again.

Q & A

What was the primary reason Panic decided to drop Google Drive support for Transmit?

Panic faced lengthy and burdensome security reviews from Google, which required significant engineering resources without benefiting their product or users.

How did Panic initially regain access to Google Drive in 2020?

They reached out to contacts within Google after months of waiting and successfully submitted Transmit for a review, which restored their access.

What issues did Panic encounter with Google's annual re-review process?

The re-review process was time-consuming, involving a security assessment that required extensive documentation and waiting periods, ultimately taking nearly a month.

What was the frustrating aspect of the Docker image provided by Google for scanning code?

The Docker image did not work correctly, which forced Panic's engineers to spend over a week debugging it, despite the scanner finding no security issues.

What was the outcome of Panic's experience with the cloud application security assessment?

Although the review found no security issues, it still took a significant amount of time and resources without providing any improvement to Transmit.

What changes did Google implement that affected Panic's ability to conduct their own security reviews?

Google removed the option for developers to scan their own code, requiring them instead to hire a third-party partner to conduct the review manually.

How did Panic feel about the prospect of paying for manual security reviews?

Panic was concerned that they might end up paying a significant amount of money for reviews that essentially duplicated the work they were already doing.

What are the broader implications of Google's policies on independent developers, according to Panic?

Panic highlighted that Google's stringent policies can lead to significant costs and risks for smaller developers, sometimes even affecting their users' livelihoods.

What alternative storage solutions did Panic mention in their discussion?

Panic indicated they might consider alternatives like iCloud Drive and Dropbox due to their frustrations with Google Drive.

What future plans did Panic express regarding their focus after dropping Google Drive support?

Panic plans to redirect their efforts toward developing other features and products rather than continuing with the burdensome Google Drive integration.