Google for Developers engagement report
@googledevs - 2.6M followers on X
Measured over 16 original posts from a 30-day window, last computed on October 25, 2026.
Engagement
A typical post picks up 589 interactions against 2.6M followers, an engagement rate of 0.023%. Posts are seen about 71K times each, and 0.828% of those impressions turn into an interaction. That is about 2.76% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.5 posts a day over the last 30 days, though only 40% of days saw any activity at all. Most posts go out around 16:00 UTC, and Tuesday is the busiest day of the week. Of the 16 posts sampled, 50% carry an image or video, 44% are part of a thread and 25% link out. The account's strongest tracked post pulled 19K interactions, about 32x its own typical post.
Measured over 16 original posts from a 30-day window, last computed on October 25, 2026. Recurring tag: #devfest.
Where this sits in the catalog
At 0.023%, Google for Developers sits above the 10th percentile of the 204,424 accounts in this comparison. That places it in the bottom 25% band, which runs below 0.024%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.004% |
| 25th percentile | 0.024% |
| 50th percentile | 0.143% |
| 75th percentile | 0.677% |
| 90th percentile | 2.55% |
| 99th percentile | 82.4% |
This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built
Posting timing
This account posts most often around 16:00 UTC, and Tuesday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.
Show engagement by hour posted, utc as a table
| Hour (UTC) | Vs author median | Posts |
|---|---|---|
| 00:00 UTC | -1% | 89K |
| 01:00 UTC | -2% | 90K |
| 02:00 UTC | -3% | 88K |
| 03:00 UTC | -4% | 94K |
| 04:00 UTC | -5% | 76K |
| 05:00 UTC | -4% | 75K |
| 06:00 UTC | -5% | 86K |
| 07:00 UTC | -5% | 93K |
| 08:00 UTC | -4% | 108K |
| 09:00 UTC | -4% | 124K |
| 10:00 UTC | -3% | 129K |
| 11:00 UTC | -3% | 141K |
| 12:00 UTC | -3% | 154K |
| 13:00 UTC | -3% | 167K |
| 14:00 UTC | -4% | 173K |
| 15:00 UTC | -2% | 176K |
| 16:00 UTC | -3% | 171K |
| 17:00 UTC | -3% | 159K |
| 18:00 UTC | -2% | 149K |
| 19:00 UTC | -2% | 141K |
| 20:00 UTC | -1% | 131K |
| 21:00 UTC | 0% | 116K |
| 22:00 UTC | -2% | 100K |
| 23:00 UTC | -1% | 90K |
Show engagement by day of week as a table
| Day | Vs author median | Posts |
|---|---|---|
| Sunday | +5% | 393K |
| Monday | +1% | 483K |
| Tuesday | -2% | 520K |
| Wednesday | -3% | 472K |
| Thursday | -2% | 430K |
| Friday | -3% | 447K |
| Saturday | +2% | 393K |
Formats this account uses
Its own posting mix on the left, and what each of those formats does across every account we track on the right. Only formats where the effect clears our publish test appear here, so an empty row is a format we could not measure rather than one that does nothing.
| Format | This account | Catalog effect | 95% interval | Accounts behind it |
|---|---|---|---|---|
| Image or video | 50% of posts | +111% | +108% to +115% | 34K |
| Outbound link | 25% of posts | -41% | -42% to -40% | 32K |
| Typical length | - | no effect | -2% to -1% | 42K |
- 50% of this account's sampled posts carry an image or video. Across the catalog, posts with an image or video run 111% above the same accounts' other posts.
- 25% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts.
- Its average post runs 245 characters, which falls in the 180 - 280 characters band. Across the catalog, posts of 180 to 280 characters match the same accounts' other posts almost exactly.
These are catalog-wide differences applied to this account's own posting mix, not a measurement of how each format performs for this account specifically. We keep one median per account, not one per format per account, so the second thing is not something this data can tell you.
Best tweets
- Oct 15, 202632x their median
We’re rolling out Gemini 4 Argon in Antigravity to paid Google AI Pro subscribers today. Demand has been incredible and we've scaled capacity deliberately to get here. We’ve rolled out a separate weekly-only Argon quota for Pro on top of the existing Gemini bucket for 3.8 Flash so you have the best of Gemini for all your tasks.
- Jul 30, 20266.8x their median
Today we’re bringing AI image generation with Nano Banana to Google Earth, letting you virtually reimagine anywhere in the real world. 🍌 https://t.co/zsgvAnbYrl For the first time, you can generate custom images using Google Earth’s satellite, aerial, and 3D imagery. 🌎 https://t.co/yed45vLZOo
- Oct 13, 20264.7x their median
📣 Gemini 4 Argon is here! Built to solve your hardest problems, Argon excels at real-world software engineering, enterprise workflows, cybersecurity defense, and scientific reasoning. By reliably handling routine tasks like everyday debugging to complex problems like codebase migrations, it frees developers to focus on architecture and product innovation. See what you can build with Argon ↓
- Sep 2, 20263.9x their median
We gave @nunudotai early access to Gemini 3.8 Flash and they took it to the Mun 🚀 As part of their upcoming gaming benchmark, they tasked several AI models to reach the Mun in the game Kerbal Space Program. Rather than build the rocket piece by piece, 3.8 Flash reverse engineered the spacecraft file format, wrote the code to generate an optimal rocket, loaded it in, and piloted it to a smooth landing on the Mun via text commands. Check it out here:
- Sep 24, 20262.6x their median
Gemma 4 is now running locally on-device in the @Antigravity SDK. 🙌 Build fully local or hybrid multi-agent workflows that pair cloud models with a @GoogleGemma 4 workforce. Audit, patch, and test your code with total data privacy and zero API fees—all powered by LiteRT under the hood.
- Aug 21, 20261.9x their median
Run and manage your @Antigravity sessions remotely 💫 Starting today, Google AI Pro and Ultra subscribers can access active sessions and drive their agents from any modern supported browser or mobile device across iOS and Android. So now, you can kick off those long, complex sessions running without being tied to your machine. Get started and check out the docs → https://t.co/Vw5j5dZ2Cp
- Aug 13, 20261.9x their median
Introducing Gemini 3.7 Flash ⚡— our most intelligent workhorse model yet for coding and agents. Gemini 3.7 Flash delivers better intelligence for complex workflows and is available with an introductory price of half the original 3.6 Flash cost per million tokens ($0.75/1M input tokens and $3.75/1M output tokens) through the end of the year. Now available across Google @Antigravity and the Gemini API via @GoogleAIStudio and @AndroidStudio. Learn more ↓ https://t.co/b26zwZihOP
- Sep 3, 20261.8x their median
Gemini 3.8 Flash and @Antigravity just made building complex developer tools a whole lot easier. From procedural game design to multi-platform UI and deep architectural mapping. 🧵 Here are 3 things you can build ↓
- Oct 16, 20261.7x their median
Reconstructing ancient ruins in 3D with Gemini 4 Argon 🏛️ Using Google @Antigravity and Blender MCP, see how Gemini 4 Argon supports digital heritage preservation by turning raw, fragmented archaeological data into fully explorable 3D worlds. https://t.co/ySvI57WIlq
- Aug 18, 20261.7x their median
Gemini 3.7 Flash is here and the community is moving FAST. ⚡️🏃♂️ From powerful new integrations to creative dev tools, we’ve rounded up some of our favorites below. Check out what they're building and get inspired 🧵↓
Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.
Recurring topics
The most frequent hashtags in the sampled posts. They describe what this account writes about; they are not a performance signal, and the catalog-wide breakdown on the hub shows how little hashtag count moves.
Buy or sell Twitter (X) accounts - escrow-protected
PlayerSells is an escrow marketplace for Twitter (X) accounts. Every deal is protected, with no middleman risk.
Reading these numbers
A typical post picks up 589 interactions against 2.6M followers, an engagement rate of 0.023%. Posts are seen about 71K times each, and 0.828% of those impressions turn into an interaction. That is about 2.76% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.5 posts a day over the last 30 days, though only 40% of days saw any activity at all. Most posts go out around 16:00 UTC, and Tuesday is the busiest day of the week. Of the 16 posts sampled, 50% carry an image or video, 44% are part of a thread and 25% link out. The account's strongest tracked post pulled 19K interactions, about 32x its own typical post.
- What is Google for Developers's engagement rate on X?
- Google for Developers (@googledevs) has an engagement rate of 0.023%, based on the median interactions across 16 original posts from the last 30 days against 2,578,742 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.023%, Google for Developers sits above the 10th percentile of the 204,424 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
- Does @googledevs have real engagement?
- There is not yet enough sample to rank this account against others of its size.
- When does @googledevs post?
- Most posts go out around 16:00 UTC, and Tuesday is its busiest day, at roughly 1.53 posts per day across the measured window.