Google Antigravity Initial Impressions

Introduction

Following the sunset notice of Firebase Studio, I was forced to migrate my four active projects to Google Antigravity.

• Despite my initial reluctance, the migration was completed successfully in every attempt.

Initial Impressions

Since I am maintaining existing projects rather than starting from scratch, this review may not be exhaustive.

However, a few key distinctions stood out immediately:

• Transparency and Control: Google Antigravity provides a detailed plan of proposed changes and only proceeds with explicit permission. This is a significant improvement over the over-aggressive nature of Firebase Studio, which often implemented changes regardless of instructions.
• Seamless Integration: While I previously found Google service integration in Firebase Studio to be fragmented, Google Antigravity offers a much smoother experience, actively performing the necessary linked updates across services.
• Automated Validation: A notable feature is its ability to run npm run build and npm run dev to self-test the application after upgrading packages. This ensures the app remains stable and functional post-update.
• Code-Level Awareness: The agent can parse existing source code to offer intelligent suggestions and implement direct changes.

However, the reality is that Google Antigravity feels like a "downgraded" vibe-coding experience; it acts more like a smarter but lazier employee.

Performance and Limitations

Unlike the cloud-based environment of Firebase Studio, Google Antigravity runs primarily on the local machine.

• This shift in architecture means that underpowered hardware may struggle to perform "vibe coding" tasks efficiently, as the local system must now handle the heavy lifting of indexing, agent orchestration, and environment emulation.
• On the other hand, this move represents a significant cost-saving strategy for Google. By offloading the compute requirements from the cloud to the user's hardware, Google can better ensure the long-term sustainability and scalability of the vibe coding ecosystem.

Furthermore, despite the "generous" weekly rate limits advertised for the free individual plan, I exhausted my quota quickly just performing routine maintenance.

• Having to wait a full week to resume work is a frustrating departure from Firebase Studio, where I could continuously refine an app until satisfied.
• Most disruptively, once the agent quota is reached, even basic functions like the "Publish" button or the "publish my app" chat command cease to function.

In summary, the efficiency of the Google Antigravity agent is undeniable, but the lack of quota transparency makes it difficult to rely on for full-time professional maintenance without constant fear of a week-long lockout.

Summary

My decision to pick Google Antigravity ultimately comes down to the granular control I maintain in coding mode and its reliable GitHub synchronization.

• While the level of control is acceptable, the sudden shutdown notice of Firebase Studio serves as a stark reminder: in this ecosystem, we must always be prepared to migrate platforms and refamiliarize ourselves with new tools at a moment's notice.