/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Q&A with Threads engineers Jesse Chen and Zahan Malkani on building the app with Instagram's tech stack, handling Threads' unexpectedly intense launch, and more

The Threads app was downloaded by more than 100M people on launch week.  How did the engineering team build the app, and handle an unexpectedly intense launch?

The Pragmatic Engineer Gergely Orosz

Context & Ripple Effects

Threads’ launch had already outpaced expectations, with 70 million signups reported within two days, before the app reached more than 100 million downloads in its first week. This engineering account explains how an Instagram-based technical foundation was tested by that demand.

The launch also preceded coverage arguing that Threads’ early traction validated demand for another text-conversation platform. Later reporting frames the product’s evolution around engagement, real-time content and community rather than its launch spike alone.

First-order effects

  • Using Instagram’s tech stack gave the Threads team a production foundation while concentrating launch-scale operational demands on shared platform systems.
  • The unexpectedly large first-week audience made reliability and capacity handling immediate priorities for Threads engineers and Instagram’s supporting infrastructure.

Second-order effects

  • A launch built atop an existing social platform raises the competitive bar for new text apps: distribution and mature infrastructure can matter as much as a standalone product concept.
  • The early surge created pressure to convert signups into durable participation, a question reflected in later coverage of Threads’ focus on engagement and real-time content.

Third-order effects

  • If large social platforms can repeatedly repurpose existing identity, distribution and infrastructure into new formats, standalone challengers may face a more structural disadvantage at launch.
  • Threads’ later community-oriented positioning suggests the lasting contest is not simply user acquisition; it is whether a scaled network can establish a distinct conversational use case.

The trend: Social platforms are increasingly using shared technical and social infrastructure to launch adjacent products quickly, then differentiating them through the communities and behaviors they cultivate.

Discussion

  • @aaronrosspowell Aaron Ross Powell on threads
    Meta continues to reaffirm their commitment to full ActivityPub federation with Threads and when that finally rolls out, it will be an extraordinarily big deal.  Like “fundamentally changed the nature of social media for the better and inoculate our networks against enshitificati…
  • @0xjessel @0xjessel on threads
    our launch was the load test :)
  • @mikehos3 Mike on threads
    It's nice to get an inside look from @0xjessel and @zahanm, looking forward to reading it
  • @c0up @c0up on threads
    5 months?!  Epic given what normally takes (and doesn't even ship) in 5 months in big tech
  • @globalfamilyapp @globalfamilyapp on threads
    Apparently Threads is working towards joining ActivityPub too... but I honestly don't know if that's a good or bad thing.  But yes, I'm keeping an eye on everything because I have no idea which ones will be around in a few years.
  • @zahanm Zahan Malkani on threads
    That's right, data portability is an important part of our ActivityPub work.
  • @alexanderbellgram @alexanderbellgram on threads
    I'm impressed that load testing was done on the fly!  👏🏻
  • @camroth Cameron Roth on threads
    Shoutout to @0xjessel and @zahanm for their focal point of today's Pragmatic Engineer interview on building @threads with @gergelyorosz_!
  • @carnage4life Dare Obasanjo on threads
    An awesome behind the scenes overview of the process of launching Threads from an engineering point of view from Gergely Orosz.  Happy to have played a small part in connecting Gergely and the Threads engineering team. https://newsletter.pragmaticengineer.co m/ ...
  • @katecaloia Kate Caloia on threads
    Love reading about the behind the scenes and insight into the building process!
  • @0xjessel @0xjessel on threads
    i've been a long time subscriber to @gergelyorosz_ pragmatic engineer's newsletter and been a huge fan of his articles.  today, i'm excited to join @zahanm in his latest post to share some of the unique engineering challenges we faced when we built this app over the span of just …
  • @pragmatic_eng @pragmatic_eng on x
    Meta did something pretty unbelievable: built an app - Threads - from start to launch in 5 months with a small team. And then pulled the biggest launch the company had seen: 100M users in 5 days. How did this look from the inside? Here are the details: https://newsletter.pragmati…
  • @surajr_ Suraj on x
    I mean they are building on top of dozens of other world class frameworks, services, and backend infra that they've already built out from their other apps. Lots of heavy lifting done already, and not much (new) scalability challenges. Launch week users is a crappy metric. How mu…
  • @hughdurkin Hugh Durkin on x
    Fascinating interview by @GergelyOrosz from @Pragmatic_Eng with the team that built @Meta's latest product, Threads. Incredible that they went from 0 to 100m users in 5 months with (at peak) just 60 engineers. A masterclass in prioritisation 👉 https://newsletter.pragmaticengineer…
  • @bartekci Bartek Ciszkowski on x
    @GergelyOrosz @Pragmatic_Eng Hard to beat small, high quality, focused teams. I bet they benefit greatly from the supports one would find in a larger org: excellent tooling, infra (playgrounds etc), internal mentorship .. the list goes on. And the usual big org barriers were like…
  • @ablenessy Attila Blénesi on x
    @GergelyOrosz @Pragmatic_Eng I look forward to learning more... Nice to see a Compose app (at least on Android) built from the ground up at that phase. Focused teams with clear goals, minimal external dependencies can deliver fast. Still, no EU tho... has it been 3 months since i…
  • @gergelyorosz Gergely Orosz on x
    Learned that the Threads app was built in 5 months (!!), project started with maybe a dozen (senior) engineers. On launch week, it hit 100M downloads / new users. This speed is... very fast. More details from the Threads engineering team coming in today's @Pragmatic_Eng issue.