Editor’s note: This article has been updated in May 2026 to reflect the latest developments in blogging and digital publishing.
In September 2008, a Chinese developer named Feng Huajun quietly shipped a $9 blogging app called BlogPress to the App Store. It supported Blogger, WordPress, Movable Type, TypePad, and Windows Live Spaces. It could do inline image editing, something neither the official WordPress nor TypePad apps could manage at the time. And it could cross-post a single article to multiple blogs simultaneously. The app was not famous. It was not backed by venture capital. But its existence posed a question that the blogging establishment was not prepared to answer: what happens when a solo developer building for a phone can outmaneuver the feature set of platforms that employ hundreds of engineers?
That question, first raised in the earliest days of the iPhone App Store, turned out to be one of the most durable structural questions in digital publishing. Nearly two decades later, the pattern it revealed continues to repeat: mobile-native tools built by small teams or individuals routinely challenge the assumptions of dominant platforms. The story of BlogPress is not just a historical curiosity. It is a case study in how platform power shifts when publishing moves closer to the device in a creator’s hand.
What BlogPress Actually Did Differently
The context matters. In mid-2008, the iPhone App Store had just launched. Most established blogging platforms treated mobile as an afterthought or a marketing exercise. Jason Kincaid, writing for TechCrunch, noted that Six Apart had introduced an iPhone version of their BlogIt software, allowing users to quickly post updates to blogs, Twitter, Pownce, FriendFeed, Jaiku, and Facebook. But the key detail was telling: BlogIt was a web app, not a native one.
As Scott Gilbertson observed at Wired, Six Apart had expanded BlogIt beyond Facebook and onto the iPhone, but clarified that it was still a web app, not the native application the company had demoed at Apple’s WWDC. The distinction between a web app wrapped in a browser and a native application built for the device’s hardware was enormous in 2008, and it remains significant today. Native apps could access the camera directly, handle images with far greater flexibility, and offer a writing experience that felt designed for the screen rather than squeezed into it.
BlogPress, by contrast, was fully native. The app featured an inline rich-text editor that allowed images to be placed within the body of a post rather than attached as separate uploads. This was a technical achievement that required working around limitations in the iPhone SDK’s text framework. The official WordPress and TypePad apps did not offer this capability. A single developer, working independently, had shipped a feature that two well-funded platform companies had not.
The app also supported multi-platform publishing. A blogger who maintained presences on both Blogger and WordPress could compose once and publish to both. This cross-posting function was, at the time, unique among iPhone blogging tools. It reflected an understanding that many serious bloggers did not live inside a single platform ecosystem but instead maintained distributed presences across several services.
The Structural Lesson: Why Small Tools Threaten Big Platforms
The conventional assumption in 2008 was that blogging platforms held the power. Blogger had Google’s infrastructure. Six Apart had TypePad and Movable Type. WordPress was growing rapidly. These companies controlled the publishing layer, the hosting, the templates, the reader networks. A mobile app, in this framing, was merely a convenience feature, a lightweight front end to the real product.
BlogPress challenged that framing by demonstrating something that has since become a recurring theme in the creator economy: the writing interface is not a secondary concern. It is the product. For a blogger composing on a commuter train or capturing a thought while traveling, the tool that sits between the idea and the published post is the most important piece of technology in the stack. If that tool is better on a third-party app than on the platform’s own offering, the platform’s grip loosens.
This dynamic has played out repeatedly in the years since. The rise of tools like Ulysses, iA Writer, and Mars Edit showed that writers often preferred dedicated composition environments over the built-in editors of their publishing platforms. The pattern intensified as mobile devices became primary computing devices for millions of creators. By the mid-2020s, the idea that a blogging platform’s web-based editor is “good enough” has become a liability rather than a safe assumption.
What BlogPress revealed early was that platform lock-in weakens when the creative act migrates to a different application layer. If the tool where writing happens is decoupled from the platform where publishing happens, then switching platforms becomes dramatically easier. The blog post composed in BlogPress could go to Blogger or WordPress or TypePad with equal ease. The platform became interchangeable. The app became the constant.
What the Incumbents Got Wrong
The mistake Blogger and Six Apart made in 2008 was not a lack of awareness. Both companies recognized that mobile mattered. Six Apart demoed a native app at WWDC. Blogger had mobile posting capabilities. The error was subtler: they treated mobile blogging as a reduced version of desktop blogging rather than as a distinct creative mode with its own requirements and possibilities.
This reductive thinking manifested in specific design choices. Images as attachments rather than inline elements. Stripped-down text editors that removed formatting options. The assumption that mobile posts would be short status updates rather than substantive articles. These choices reflected a mental model in which “real” blogging happened at a desk and mobile was for quick notes.
Feng Huajun did not share that assumption. His development of an inline image editor, his support for multiple blogging backends, and his implementation of cross-posting all suggested a vision of mobile blogging as a first-class creative activity. The app was priced at $9, a signal that it was a professional tool rather than a throwaway utility. The pricing strategy itself carried an argument: mobile blogging is worth paying for because mobile blogging is real blogging.
This miscalculation by incumbents is a pattern that persists in digital publishing. Platforms routinely underestimate the sophistication of their most committed users. They optimize for the median case, for the casual poster, for the user who might churn. Professional bloggers and serious publishers, meanwhile, gravitate toward tools that respect their workflow. When platforms fail to serve power users on the devices those users actually carry, third-party tools fill the gap. And once a creator’s workflow lives in a third-party tool, the platform’s strategic position erodes.
The App Store as a Publishing Ecosystem Disruptor
BlogPress’s journey through Apple’s review process is itself instructive. Feng described three rejections before approval. The first involved a Picasa Web Album integration issue. The second was a disagreement over whether displaying raw HTML during editing was a feature or a bug. The third concerned a camera orientation problem in landscape mode. Each rejection added roughly a week of delay.
The frustrations were real, but Feng’s conclusion was measured. He noted that the App Store solved a bundle of practical problems that independent developers on other platforms had to manage alone: distribution, payment processing, copy protection, and discoverability. The trade-off between editorial control by Apple and infrastructure provided by Apple was, in his assessment, favorable for developers.
This observation anticipated a debate that would define the next decade of platform economics. The App Store’s role as gatekeeper created friction, but it also created a marketplace where a solo developer in China could reach iPhone users worldwide without building a marketing apparatus, a payment system, or an anti-piracy framework. For blogging tools specifically, this meant that any developer who understood the needs of bloggers could compete with established companies on a relatively level distribution surface.
The long-term implication for publishers is worth noting. The App Store model, and the mobile app ecosystem it spawned, created a permanent alternative distribution channel for writing tools. Blogging platforms can no longer assume that their built-in editors will be the default composition environment. The competitive surface expanded from “which platform has the best features” to “which tool, on which device, offers the best writing experience,” and that expansion has never reversed.
What This Means for Publishers Now
The BlogPress story offers several grounded takeaways for anyone who publishes online professionally, particularly those managing their own blogs or building audience-driven businesses.
First, the composing environment matters more than most platform strategies acknowledge. Publishers who evaluate blogging platforms solely on hosting, SEO features, or template quality may be overlooking the most consequential variable: how well the platform supports the actual act of writing, on the actual devices used for writing. A platform with excellent SEO tools but a mediocre mobile editor is vulnerable to the same competitive dynamic that BlogPress exploited in 2008.
Second, cross-platform publishing capability remains strategically important. The ability to compose once and distribute to multiple endpoints, which BlogPress offered as a native feature, has become a standard expectation among professional publishers. Tools like Buffer, Zapier integrations, and headless CMS architectures all descend from the same insight: tying content creation to a single distribution channel is a fragility, not a feature.
Third, the history of blogging tools suggests that the most meaningful innovations often come from independent developers rather than platform incumbents. WordPress itself began as a fork of an existing project. Ghost emerged from a Kickstarter campaign. Substack was built by a small team that saw an opening the major platforms had ignored. Publishers who pay attention only to what their current platform offers and ignore the independent tool ecosystem risk missing the next shift in how publishing actually works.
The quiet case that BlogPress made in 2008 was not really about one iPhone app. It was about the structural vulnerability that emerges whenever a dominant platform treats the creative workflow as secondary to the distribution infrastructure. That vulnerability has not been resolved. If anything, as publishing becomes more mobile, more distributed, and more reliant on tools that creators choose for themselves, the lesson has only grown sharper. The platforms that survive long-term will be those that take the writing experience as seriously as a solo developer working alone on an app that nobody expected to matter.
