A History of IDEs at Google

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get kitchen staples and gadgets delivered free — and shop member deals

• Fast, free delivery on millions of items
• Access to Prime Big Deal Days deals on October 6–7
• Prime Video, Amazon Music and more included

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Google historically lacked a unified IDE approach due to diverse preferences and technical challenges. Starting around 2013, Google developed Cider, a cloud-based editor, which evolved into a VSCode-based platform by 2020. This transition aims to improve developer productivity and standardization.

Google has shifted from a fragmented IDE ecosystem to a unified, cloud-based development environment, culminating in adopting VSCode as its primary frontend for internal code editing.

For years, Google engineers used diverse IDEs, leading to fragmentation and duplicated effort in integrating tools like code search, formatters, and build support. In 2013, Google introduced Cider, a web-based editor designed to handle the company’s massive monorepo and support quick editing, especially for non-Java developers. Cider’s backend indexed the entire codebase, enabling features like code completion and cross-referencing, which significantly improved developer productivity.

By 2020, Google decided to adopt the popular VSCode frontend for Cider, leveraging its mature extension ecosystem and familiarity among developers. This transition aimed to unify the IDE experience, reduce maintenance overhead, and facilitate feature development. The new platform, called Cider V, was in beta by 2021, with thousands of engineers testing and providing feedback. The shift reflects Google’s ongoing efforts to modernize its developer tools and address the challenges posed by its large-scale codebase.

Why It Matters

This evolution matters because it directly impacts developer productivity, code quality, and operational efficiency at Google. A unified, cloud-based IDE reduces onboarding time, streamlines collaboration, and allows rapid deployment of new features. It also exemplifies how large tech companies adapt their tooling to scale, balancing custom solutions with industry standards.

Background

Google’s main codebase, google3, is one of the largest monorepos in the world, requiring specialized tooling to support its scale. Historically, engineers chose their own IDEs, leading to fragmentation. In 2011, senior engineers like Jeff Dean dismissed efforts for a common IDE, citing personal preferences. Over time, internal projects like the IntelliJ integration and the development of Cider aimed to address these issues. The rise of web-based editors like Cider in 2013 responded to the company’s web-centric culture and scale challenges. The subsequent shift to VSCode in 2020 marked a strategic move to leverage industry-standard tools for better maintainability and developer experience.

“Trying to get a group of developers to all agree on a common editor is a recipe for unhappiness. Everyone has different opinions about what is important here.”

— Jeff Dean

“Switching to VSCode as the frontend allows us to leverage a mature ecosystem and unify the developer experience across teams.”

— Google internal team (2020)

What Remains Unclear

It remains unclear how widely adopted the new VSCode-based platform will become across all Google teams or how it will evolve to meet future scaling challenges. Details about long-term support and integration with other internal tools are still emerging.

What’s Next

Google plans to continue refining Cider V, expanding its features, and increasing adoption across engineering teams. Future updates may include deeper integration with internal systems, improved performance, and broader tooling support. Monitoring user feedback and performance metrics will guide ongoing development.

Key Questions

Why did Google initially avoid standardizing on a single IDE?

Google’s culture and diverse engineering needs made it difficult to enforce a single IDE. Engineers preferred different tools, and early efforts to unify them faced resistance, so the company tolerated multiple options for years.

What prompted the shift to a cloud-based editor like Cider?

The need to handle Google’s massive monorepo efficiently and to support web-centric workflows led to the development of Cider, a cloud-based editor that could index and analyze code at scale.

How does the new VSCode frontend improve Google’s developer experience?

It provides a mature, extensible, and familiar interface, reducing the maintenance burden, enabling faster feature development, and offering better integration with existing tools and workflows.

Will all teams adopt the new IDE platform?

Adoption is ongoing, with plans to expand Cider V’s reach. The company is likely to encourage widespread use, but some teams may continue using legacy tools during transition phases.