Micro.blog

Every few years, someone tries to fix social media by subtracting from it. Almost all of them fail, because subtraction alone isn’t a product — it’s a mood board. Micro.blog is the exception, and the reason is structural rather than philosophical: it doesn’t just remove the bad parts of a timeline, it relocates the timeline on top of infrastructure that has outlived every social network to date. Your posts aren’t rows in someone’s database. They’re blog entries, on a domain, syndicated by RSS and ActivityPub.

Built by Micro.blog, LLC — the small, independent shop that grew out of Manton Reece’s long-running crusade against the “your content is our inventory” model — the app is the mobile front door to a hosted blogging service that has been running since 2017. Positioning is where it gets interesting. This isn’t a Twitter clone chasing refugees, and it isn’t a Mastodon client chasing federation nerds. It sits in a category of roughly one: a publishing tool wearing a social interface. You open it expecting a feed. You post something offhand about your commute. That’s now a permalinked entry on a website with your name on it, complete with a feed other software can read.

The market context matters. We are deep into the post-Twitter fragmentation era, where Bluesky, Mastodon, Threads, and a dozen also-rans are competing for the same exhausted user. Micro.blog’s answer is to opt out of the competition entirely by cross-posting to all of them. Publish once; let Mastodon, Bluesky, Tumblr, and LinkedIn have copies. The canonical version stays home.

It also runs about $5 a month after a 10-day trial, which is either the most refreshing thing about it or the reason some people will delete it on day eleven. The store ratings tell part of that story: 4.4 out of 5 on iOS from 56 ratings. Small, devoted, and likely bruised by the checkout page.

• Chronological, algorithm-free timeline: Posts from people and sites you follow, in the order they were published. No engagement ranking, no ads, no “you might like.” What you follow is what you get.
• No likes, no follower counts: The two metrics that industrialized social performance are simply absent. There is no scoreboard to game, which changes what people post.
• Real hosted blog behind every post: Short microblog posts and long-form articles live on the same site, with Markdown, custom themes, categories, photos, and Pages.
• Open syndication by default: Every post exits via RSS and ActivityPub, making your blog readable from Mastodon and any feed reader without extra plumbing.
• Cross-posting: Automatic mirroring to Mastodon, Bluesky, Tumblr, and LinkedIn from a single compose box.
• Client for external sites: Already run a WordPress or Micropub-compatible blog? The app works as a publishing client for it, and can pull existing feeds into your timeline.
• Bookshelves and microcasts: Track what you’re reading; publish short-form podcasts with hosting included.

The Loop

The core interaction is deceptively plain: read the timeline, tap compose, publish. What makes it worth examining is what the app doesn’t do at each step.

There’s no pull-to-refresh dopamine engine, because nothing is being withheld and re-served. There’s no notification cascade, because there are no likes to notify you about. Replies exist, but the absence of a public approval metric changes the character of the conversation in a way that’s hard to overstate from the outside. On mainstream platforms, the reply box is a stage. Here it’s closer to a comment thread on a friend’s site — because it literally is one.

The publishing flow is the real feature. You type, you hit post, and the entry exists at a URL you control. Markdown is handled without ceremony. Photos upload to your own media library rather than a platform CDN that may or may not exist in five years. Switch a toggle and the same composer produces a 2,000-word essay instead of a 200-character aside — the app treats both as the same object type, which is the right call and exactly what Twitter-era muscle memory keeps you from expecting.

Onboarding Friction

This is where Micro.blog stumbles, and it’s worth being blunt about it. The app is free to download and effectively useless after ten days unless you subscribe. Users don’t discover this in a preamble; they discover it when the trial ends and the compose button stops meaning anything. That’s the most predictable complaint a design like this invites, and it’s a self-inflicted wound. The pricing itself is defensible — hosting, bandwidth, media storage, and podcast delivery cost real money, and $5/month for all of it is competitive against any comparable blog host. The presentation of that pricing is the problem. A paid service disguised as a free social app will always feel like a bait-and-switch, even when the underlying deal is fair.

There’s a second friction point that’s more philosophical than technical. The timeline is small. Follower counts are hidden, discovery is deliberately quiet, and the community skews toward writers, developers, and the indie-web faithful. If you arrive expecting to find your existing social graph, you’ll find a handful of people and a lot of silence. Micro.blog’s counterargument is that the timeline was never the point — your site is — but that argument lands better with someone who already wanted a blog than with someone who wanted a network.

Interoperability as a Strategy

The smartest architectural decision here is refusing to be a walled garden in either direction. ActivityPub means Mastodon users can follow your blog natively; they never need an account. RSS means feed readers work. Cross-posting means your Bluesky audience still sees you. And the Micropub/WordPress client mode means Micro.blog can be your posting app even if you never host a byte with them — an act of confidence bordering on recklessness for a subscription business, and one that earns a lot of goodwill.

The practical effect is that leaving is easy. Export your posts, point your domain elsewhere, keep your URLs. That’s an unusual thing to build on purpose, and it’s strong evidence that the ownership pitch isn’t marketing.

Where the Design Philosophy Strains

Not every subtraction is a win. Without likes, you get almost no ambient signal that anyone read what you wrote — some will find that liberating, others isolating, and Micro.blog offers little middle ground. Discovery of new people to follow is thin, leaning on curated Discover feeds that can’t compensate for the absence of a recommendation engine. And the recently expanded Pages and Photos tabs, which make a full website “come alive” from the phone, also expose the tension in the product: the more site-management surface the app absorbs, the less it behaves like the calm little reader it sells itself as.

The aesthetic is restrained to the point of austerity, and it works. Typography carries the interface — sensible line lengths, generous whitespace, text that’s clearly meant to be read rather than scanned. There’s no skeuomorphism, no gradient flourishes, no animated engagement bait. Buttons are where you’d expect them.

On iOS it reads as a native app rather than a wrapped web view: standard navigation patterns, proper share-sheet handling, and a timeline built for straightforward scrolling. Image handling is the one place where the machinery shows, since media goes to your own hosting — a design that trades convenience for ownership, and one where a weak connection will make itself felt.

The store screenshots do the product no favors — they show a text feed, which is accurate and completely unpersuasive. That’s a marketing failure, not a design one, but it contributes to the download-then-bounce pattern the ratings reflect.

The gap here is real. iOS is the flagship — it holds a 4.4/5 and reads like the version the team actually uses. The design follows platform conventions closely, and the newer Pages and Photos tabs are integrated cleanly.

Android trails in its ratings, and the delta isn’t about features so much as fit and finish. The design points to a rougher experience: less polish in navigation, more friction in the editing and upload paths, and an app that follows platform conventions less faithfully than its iOS sibling. For a service whose entire value proposition is “post effortlessly, from anywhere,” any hesitation in the compose path is disproportionately costly. Android users are getting the same backend through a noticeably thinner client.

Both platforms benefit from the same escape hatch: because everything is standards-based, you can post via email, via a third-party Micropub app, or straight from the web when the native client annoys you.

Micro.blog is a small app carrying an unfashionable argument: that the durable version of your writing should live at an address you control, and that the social layer is a convenience wrapped around it, not the other way around. It makes that argument credibly, because the plumbing is designed to work — open syndication, easy export, and a client mode that lets you use the app while paying them nothing for hosting.

The flaws are honest ones. The paywall arrives too abruptly for an app distributed through stores full of free things. The community is quiet enough that newcomers may mistake it for empty. And Android deserves a better client than it appears to be getting, given both versions cost the same.

But the core is sound in a way most social products aren’t. Delete Bluesky and your posts vanish with the company. Delete Micro.blog and your site keeps serving at your domain. That’s not a feature — it’s the whole thesis, and it’s the argument that gives this category its future. Pay the five dollars, or don’t. Just know that what you’re buying isn’t a feed. It’s an exit.