Bottom Line: Micro.blog is the rare social app that refuses to be one — it trades likes, follower counts, and algorithmic feeds for a real website you actually own, and charges you honestly for the privilege. The iOS app is polished and purposeful; the Android build lags, and the paywall lands harder than it should.
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, and they arrive, but the absence of a public approval metric changes the character of the conversation in a way that's hard to overstate until you've lived in it for a week. 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 within a second 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 exactly right 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 single most consistent complaint across both stores, 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 the strongest 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 users find that liberating, others find it 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 reviewers rightly praise for making 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.