Bluesky's Drafts Feature: A Case Study in Decentralisation's Cost

Bluesky shipped drafts last week—a feature so basic that its absence until now tells you everything about the platform's struggle to keep pace. For a service that's positioned itself as the cultural and technical antidote to Elon Musk's X, launching the ability to save unfinished posts in February 2026 isn't just late. It's a red flag about what happens when ideological commitment to decentralisation collides with the brutal realities of product-market fit.

The infrastructure tax of decentralisation

Bluesky's 42 million figure, drawn directly from its public API, represents total registrations, not active users. The company hasn't disclosed monthly or daily actives, which tells you most of what you need to know about retention. Threads, by contrast, reported over 300 million monthly actives in late 2025, according to Meta's disclosures.

X doesn't release user numbers anymore, but third-party estimates from Sensor Tower and Apptopia suggest it still commands several hundred million monthlies despite the exodus narratives. The gap matters because Bluesky's decentralised AT Protocol—its core differentiator—appears to be slowing feature development relative to centralised competitors.

Building on a federated architecture means every new feature must work across multiple instances, handle edge cases in ways that centralised platforms don't, and maintain compatibility with third-party clients. That's a noble engineering challenge. It's also expensive, slow, and increasingly hard to justify when users just want to save a bloody draft.

Dating apps know this dynamic well. Decentralised dating has been pitched repeatedly over the past five years—most recently by the Alovoa and Mainstream projects—and has gained almost no traction. The reason isn't lack of interest in alternatives; it's that decentralisation introduces friction at every layer of the user experience, from onboarding to moderation to something as simple as cross-instance messaging. Bluesky is discovering that ideology doesn't compound into network effects.

What's still missing

Drafts may be live, but Bluesky still lacks private accounts and extended video support—both baseline features for mainstream social adoption. Private accounts, in particular, are a significant omission for any platform hoping to attract users who want control over their audience. The company outlined plans in late 2025 to prioritise algorithmic feed refinement, follow recommendations, and real-time interactions in 2026, but the roadmap reads more like a 2019 to-do list than a 2026 product strategy.

The timing is critical. High-profile migrations to Bluesky—driven largely by dissatisfaction with X's moderation collapse and Threads' uneven rollout—created a narrow window in 2024 and early 2025 when momentum could have translated into platform switching. That window is closing.

Users who signed up expecting a fully-formed alternative are now bouncing between platforms, and Bluesky's feature gaps make it easy to drift back to X or settle into Threads.

When Bumble launched in 2014, it had one differentiator—women message first—but it also had the full feature set users expected from Tinder. When Hinge repositioned in 2016 as "designed to be deleted," it didn't ask users to tolerate a stripped-down experience while it built out basics. Bluesky is asking its refugees to wait, and refugees don't wait.

The retention risk

The real question isn't whether Bluesky can ship drafts or private accounts. It's whether the company can ship them fast enough to convert its 42 million sign-ups into a retained, engaged user base before the next migration wave—inevitably back to a competitor with fewer technical constraints.

This matters for dating because the same dynamics are playing out in the swipe-to-chat layer. Match Group (MTCH) and Bumble (BMBL) may be legacy players, but they're also feature-complete. Upstarts like Snack, Feels, and others pitch themselves on novelty—video-first, vibe-based, anti-swipe—but they're competing against apps that already have chat, push notifications, moderation infrastructure, payment rails, and all the unglamorous plumbing that makes a social product usable at scale.

Bluesky's drafts problem is the same problem every challenger faces: you can win the narrative and still lose the product war. Bluesky's roadmap suggests it understands the urgency. The company has committed to refining its Discover feed, improving follow recommendations, and making the platform feel more responsive in real time. Whether it can execute on that backlog while also maintaining the decentralised ethos that attracted its core user base is an open question. The longer it takes, the more likely those 42 million registrations remain just that—registrations, not a platform.