AI / Google Antigravity Gemini Fundamentals Interview Questions
What are the key deprecated and shut-down Gemini models developers should know about?
Staying current with model deprecations is critical for production applications. The Gemini API has seen significant deprecations throughout 2025-2026, and applications referencing deprecated model IDs will receive errors after shut-down dates.
| Model(s) | Shut-down date | Notes |
|---|---|---|
| All Gemini 1.0 models | Multiple dates in 2025 | Now return 404 errors; migrate to 2.x or 3.x |
| All Gemini 1.5 models | Multiple dates in 2025 | Now return 404 errors; migrate to 2.x or 3.x |
| Gemini 2.0 Flash | June 1, 2026 | Returns errors; migrate to 2.5 Flash or 3.x |
| Gemini 2.0 Flash-Lite | June 1, 2026 | Returns errors; migrate to 2.5 Flash-Lite or 3.x |
| Gemini 3 Pro Preview | Deprecated March 9, 2026 | Short notice; illustrates preview risk |
| Imagen (all versions) | June 30, 2026 | Migrate to Nano Banana (gemini-3-image family) |
| Veo 2.0 models | June 30, 2026 | Migrate to Veo 3.1 family |
# How to detect if your code is using deprecated models: # Run this to audit model IDs in your codebase: import re, glob deprecated = [ "gemini-1.0", "gemini-1.5", "gemini-2.0-flash", "gemini-2.0-flash-lite", "gemini-3-pro-preview", "gemini-3.0", "imagen", "veo-2" ] for file_path in glob.glob("**/*.py", recursive=True): with open(file_path) as f: content = f.read() for dep in deprecated: if dep in content: print(f"DEPRECATED model ID found in {file_path}: {dep}") # Best practice: centralise model IDs in config # config.py: GEMINI_MODEL = "gemini-3.5-flash" # update here only when migrating GEMINI_EMBED_MODEL = "gemini-embedding-exp-03-07"
More Related questions...