The date came and went without a model

Google announced Gemini 3.5 Pro in mid-May at its developer conference and said the model would arrive the following month. June passed. Bloomberg reported on 16 July that the model is months behind schedule, and that Google is still taking time to improve it.

The sticking point is code. Google updated the data used to train Gemini late in June specifically to lift its coding skills, and, in the words of people familiar with the work, the results were disappointing. A Google spokesperson said the company is currently testing 3.5 Pro and an upgraded Flash model with partners.

No new launch date has been given. That is the fact worth carrying out of this story, because a missing date is not a small version of a date.

Two hundred billion dollars in one session

Alphabet closed down 4.4 percent on Thursday 16 July, ending the session at an unofficial 354.46 dollars and erasing roughly 200 billion dollars of market value. The decline dragged the wider indices to their session lows: the S and P 500 fell 0.51 percent to 7,533.77 and the Nasdaq Composite lost 1.47 percent to 25,881.95.

Nothing shipped that day and nothing broke. A report that a model is late moved a company by the size of a mid-cap index. The market has stopped paying for announced capability and started paying for delivered capability, and that repricing is the part of this story that outlives the model.

The release pattern is the real roadmap

Look at what Google has actually shipped in the 3.5 line: Flash, and an upgraded Flash now in testing. Gemini 3.5 Flash remains the only member of the series that customers can use, while the flagship stays in the lab. Gemini 3.1 Pro, still the current Pro, dates from February.

Google's own statement is the clearest signal here. Asked about a delayed frontier model, the company answered that it ships quickly across a wide range of models while keeping them highly cost-effective. That is a true sentence about the cheap tier, offered in place of an answer about the expensive one.

A vendor's release pattern is harder to spin than its roadmap, because a shipped model either exists or does not. Google is currently a vendor that reliably ships fast, cheap models and unreliably ships frontier ones. Plan against the pattern.

Ten employees, two rivals, one quarter

Ten current and former Google employees told Bloomberg they were concerned the company is losing ground while Anthropic and OpenAI ship models that outperform Gemini. That is not a market rumour, it is the people building the thing describing the gap from the inside.

The competitive frame matters less to an owner than the timing frame. Rivals released models that beat Gemini on code inside the same quarter in which Gemini's own coding work disappointed. Whatever the eventual quality of 3.5 Pro, the window in which it would have arrived first has already closed, and Google is now shipping into a comparison rather than setting one.

What to do before your next planning cycle

Strike unreleased model names from your plans and put capabilities in their place. A requirement that reads "a model that passes our code-review suite at 90 percent" survives a delay; a requirement that reads "Gemini 3.5 Pro" becomes a hole in a spreadsheet the moment a vendor slips.

Then price the delay you are already exposed to. Name the fallback you have actually tested on your own tasks, date the review, and tell any customer whose deliverable depends on an unreleased model before they read about it. The cost of a slipped launch is small when your plan expected it and large when your plan promised it.

The bottom line: Google will very likely ship a strong 3.5 Pro, and it will very likely be late again. Build the schedule that is true in both cases.