Back to @MetaforDevs's profile

Meta for Developers engagement report

@MetaforDevs - 324K followers on X

Measured over 15 original posts from a 30-day window, last computed on September 4, 2026.

Engagement

Middle of its size range
Per follower
0.051%
of 324K followers
Per impression
0.494%
33K views on a typical post
Reach
10.3%
of its followers see a post
Typical post
164
interactions (median)
Saved
0.136%
45 bookmarks on a typical post
Posting rate
1.43/day
active 47% of days
Peak time
19:00 UTC
Wednesday

A typical post picks up 164 interactions against 324K followers, an engagement rate of 0.051%. Measured over 15 original posts, its engagement rate beats 49% of 6,874 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 33K times each, and 0.494% of those impressions turn into an interaction. That is about 10.2% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.4 post a day over the last 30 days, with activity on roughly 47% of days. Most posts go out around 19:00 UTC, and Wednesday is the busiest day of the week. Of the 15 posts sampled, 100% carry an image or video and 67% link out. The account's strongest tracked post pulled 1.9K interactions, about 11x its own typical post. Recurring topics include #metaquest, #vr.

Measured over 15 original posts from a 30-day window, last computed on September 4, 2026. Recurring tags: #metaquest, #vr.

Compared with accounts its own size

Meta for Developers's engagement rate beats 49% of the tracked X accounts closest to it in follower count (6,874 accounts, accounts of similar size (decile 7 of 10)). A percentile is spread evenly by construction, so 50 really is the middle of that group and 90 really is its top tenth.

On engagement per impression rather than per follower it beats 29% of the same group. When those two numbers disagree, the gap is about how far its posts travel rather than how people react to them.

Where this sits in the catalog

At 0.051%, Meta for Developers sits above the 25th percentile of the 65,980 accounts in this comparison. That places it in the below the median band, which runs 0.016% to 0.1%.

p100.002%
p250.016%
p50 (median)0.1%
p750.499%
p902.09%
p99120.0%
Engagement rate as a share of followers, across the 65,980 accounts we have scanned enough to measure. The axis is logarithmic, because the top and bottom of this population are about 57,142 times apart and a linear axis would flatten everything below the median into a single point.
Show the percentile table
Engagement rate percentiles
PercentileEngagement rate
10th percentile0.002%
25th percentile0.016%
50th percentile0.1%
75th percentile0.499%
90th percentile2.09%
99th percentile120.0%

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 19:00 UTC, and Wednesday 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.

Engagement by hour posted, UTCTwenty-four bars, one per UTC hour. Each bar shows how posts published in that hour compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest hour: 19:00 UTC.
0003060912151821
Above the authors' own mediansBelowScale: plus or minus 111%Busiest hour: 19:00 UTC
Show engagement by hour posted, utc as a table
Engagement by hour posted, UTC
Hour (UTC)Vs author medianPosts
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 UTC0%116K
22:00 UTC-2%100K
23:00 UTC-1%90K
Engagement by day of weekSeven bars, one per weekday, Sunday first. Each bar shows how posts published on that day compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest day: Wednesday.
SunMonTueWedThuFriSat
Above the authors' own mediansBelowScale: plus or minus 111%Busiest day: Wednesday
Show engagement by day of week as a table
Engagement by day of week
DayVs author medianPosts
Sunday+5%393K
Monday+1%483K
Tuesday-2%520K
Wednesday-3%472K
Thursday-2%430K
Friday-3%447K
Saturday+2%393K
See what moves engagement across the whole catalogWhat counts as a good engagement rate at this size

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.

This account's posting mix compared with catalog-wide effects
FormatThis accountCatalog effect95% intervalAccounts behind it
Image or video100% of posts+111%+108% to +115%34K
Outbound link67% of posts-41%-42% to -40%32K
Typical length-+15%+14% to +16%32K
  • 100% 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.
  • 67% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts, so a large share of this account's output sits in the weakest bucket we measure.
  • Its average post runs 311 characters, which falls in the over 280 characters band. Across the catalog, posts over 280 characters run 15% above the same accounts' other posts.

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

  • Aug 10, 202611x their median

    Meet Muse Glimmer: an open-weight model built for always-on local agents. 30B parameters, Apache 2.0 and tuned for complex multi-step work so it plans, calls tools, hits errors, retries, and sees the task through long-horizon loops. Muse Glimmer is designed to balance capability against the memory and compute constraints of local hardware. We couldn’t be more excited to get this in the hands of developers. Download and start building now: https://t.co/NKBJ0SHrmU

    1.6K1905930114K viewsView on X
  • Sep 2, 20265.9x their median

    Muse Spark 1.3 is now available in Muse Code and Meta Model API. It’s tuned for the agentic builds developers actually ship, including long-running, multi-agent workflows. 🧵👇(1/4) https://t.co/aS8cuVgMuU

    86159421143K viewsView on X
  • Aug 26, 20264.7x their median

    Muse Image is now available on Meta Model API and priced for production volumes at $0.01/image. It’s an agentic image model that reasons before it renders. Each call searches the web to refine the output through iterative passes and evaluates the prompt for precise elements like charts and QR codes. Text-to-image, single-image and multi-image editing, and multi-reference composition all live in one model, so there's no multi-step pipeline to stitch together. Start building → https://t.co/Q0TSXkIp03

    629723830136K viewsView on X
  • Aug 31, 20264.4x their median

    Muse Code is now out of beta with new features and updates designed to help you work faster and smarter: sessions that message each other, workflows to orchestrate subagent teams, and an SDK in developer preview. Monthly plans are also rolling out today, starting at $5. Follow the link for the full feature download -> https://t.co/99IVBU9SB2

    59943552569K viewsView on X
  • Aug 21, 20264.1x their median

    We’re excited to bring @AIatMeta’s Muse Spark 1.2 contributor tier to OpenRouter. At $0.10/M input and $0.20/M output, It’s meaningfully cheaper than Muse Spark 1.2 and beats other comparable models on real cost, providing frontier intelligence-per-dollar. https://t.co/YNf6EprqiW

    58926272498K viewsView on X
  • Aug 5, 20263.6x their median

    Meet Muse Spark 1.2 and Muse Code, the agent built to run it against your coding challenges. Now in beta. Together they take a task from idea to production, and deploy teams of agents that plan, write and refine across your repos. Start building now: https://t.co/KdUx8eli0S https://t.co/FXHo7JXTAW

    495542911155K viewsView on X
  • Aug 18, 2026

    An AI agent found a hidden UI bug in Beat Saber's menu flow that scripted tests didn't catch. 🧠 That's Meta XR Operator: an OpenXR API layer that lets your AI agent see, test, and verify your VR app autonomously. New in Meta XR SDK v205. Try it today 👉 https://t.co/bmghUIvLjV https://t.co/JA2nSxlhKS

    1791410119K viewsView on X
  • Aug 26, 2026

    Muse Image from Meta, now on Runway. Available today alongside the world's best image and video models. Try it now at the link below. https://t.co/bA2yBNfbEc

    1262171033K viewsView on X
  • Sep 1, 2026

    Build conversation-aware features without the pipeline. Muse Voice Transcribe is now in public preview on Meta Model API. For developers building real-time speech into their products, Muse Voice Transcribe delivers competitive transcription accuracy with live speaker attribution in a single streaming model – so you can ship without stitching together helper models or paying frontier prices. Learn more and start building at https://t.co/nwJ7UFVpAQ.

    13911817.9K viewsView on X
  • Aug 3, 2026

    Imagine controlling your EV, tracking constellations, or adjusting your smart home lights, all from your AI glasses. 👓 One developer built web apps that do all of this on Meta Ray-Ban Display. Now, he's sharing his technical playbook. Watch here 👉 https://t.co/OYGecn7d9K https://t.co/NYDWdMEvrV

    851116512K viewsView on X

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

#metaquest#vr

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 X accounts - escrow-protected

PlayerSells is an escrow marketplace for X accounts. Every deal is protected, with no middleman risk.

Reading these numbers

A typical post picks up 164 interactions against 324K followers, an engagement rate of 0.051%. Measured over 15 original posts, its engagement rate beats 49% of 6,874 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 33K times each, and 0.494% of those impressions turn into an interaction. That is about 10.2% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 1.4 post a day over the last 30 days, with activity on roughly 47% of days. Most posts go out around 19:00 UTC, and Wednesday is the busiest day of the week. Of the 15 posts sampled, 100% carry an image or video and 67% link out. The account's strongest tracked post pulled 1.9K interactions, about 11x its own typical post. Recurring topics include #metaquest, #vr.

What is Meta for Developers's engagement rate on X?
Meta for Developers (@MetaforDevs) has an engagement rate of 0.051%, based on the median interactions across 15 original posts from the last 30 days against 324,390 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
Is that a good engagement rate?
At 0.051%, Meta for Developers sits above the 25th percentile of the 65,980 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 @MetaforDevs have real engagement?
Its engagement rate beats 49% of the tracked X accounts closest to it in follower count (6,874 accounts), which puts it in the middle of its size range group. Ranking inside a size band matters because engagement rate falls as accounts grow, so a raw rate would mostly re-measure the follower count. It is a starting point for a look at follower quality, not a verdict on it.
When does @MetaforDevs post?
Most posts go out around 19:00 UTC, and Wednesday is its busiest day, at roughly 1.43 posts per day across the measured window.

Keep going