Skweezer Mobile RSS Feeds: Bringing the Web to Phones in 2006

By 2006, RSS feeds were one of the default ways people followed news and blogs, and phones and PDAs were common enough that people wanted that same habit on the go. Most phones of the era weren't built for it — screens were small, cellular data was slow and often billed by the kilobyte, and the web was still designed almost entirely for desktop monitors. Into that gap stepped proxy-based services that tried to squeeze ordinary web pages down to something a phone could actually load, and Skweezer, from a company called Greenlight Wireless, was one of the more prominent. Mobility Today covered Greenlight Wireless's announcement that Skweezer added RSS support, and that original coverage survives in the Wayback Machine — giving a rare first-hand look at how a mobile-optimization service talked about RSS before smartphones made most of this unnecessary.

What Was Skweezer?

Skweezer was a free web portal that reformatted ordinary websites so they'd load faster and display more sensibly on the small screens and slow connections typical of mid-2000s PDAs and phones. A user visited skweezer.net from whatever browser their device already had, entered an address or search terms, and got back a "skweezed" version of the page — no app, no download. It's usually described, then and now, as a transcoding proxy: a server that sits between the phone and the destination website, rewrites the page along the way, and hands the phone something lighter to render.

Who Made Skweezer?

Mobility Today's own contemporary coverage identifies Greenlight Wireless as the company behind Skweezer, describing it as "a leading innovator of wireless technologies, providing ASP and server-component solutions for enterprise-level businesses and wireless carriers," with Skweezer as its "consumer-oriented" service. Some later reference material instead credits a separate company, Skweezer, Inc., as the original developer. This piece won't try to untangle the exact corporate history — what's clearly documented in Mobility Today's own reporting is that Greenlight Wireless was publicly announcing and marketing Skweezer when this RSS feature launched.

Why Mobile Browsing Needed Help

It's easy to forget how rough mobile browsing was in the mid-2000s. Screens on a typical PDA or feature phone were a few inches across, cellular data was slow and often metered, and the phones had limited memory and weak processors even by the standards of a few years later. The web wasn't designed around any of that — it assumed a keyboard, a mouse, and a fast wired connection. A page that loaded instantly on a desktop could take a painfully long time on a phone, if it rendered usably at all. That mismatch is the entire reason transcoding services like Skweezer existed.

How Skweezer Reformatted Pages

Mobility Today's own coverage from around this period describes a few different ways to view a page through Skweezer, depending on the device and connection involved:

Beyond that general description of the three view modes, this article won't invent specifics about exactly which page elements got stripped or how images were compressed technically — those particular engineering details aren't confirmed in the surviving contemporary coverage.

Why RSS Mattered in the Mid-2000s

RSS — Really Simple Syndication — hit its stride as a mainstream idea right around this period. Rather than repeatedly checking favorite sites for updates, a reader could subscribe to a feed and get a running list of headlines and summaries in one place. Growth was dramatic: by some counts there were a few hundred thousand RSS feeds in early 2004, and well over ten million by August 2005. Bloglines was widely considered the leading RSS reader of the era, and Google Reader had just launched in 2005 too. For anyone keeping up with blogs and news without manually revisiting each one, RSS had become the obvious way to do it — exactly why a mobile-optimization company would want its service to handle feeds well.

The Mobility Today Article

The original article, headlined "Skweezer now supports RSS newsfeeds," is recoverable through the Wayback Machine, and it tells a more precise story than a casual retelling might assume. The underlying press release carries an Irvine, California dateline of February 21, 2005, and Mobility Today's own posting is credited to David Ciccone and dated Wednesday, February 23, 2005 — not later in 2006. That date matters, since Skweezer's RSS support and the separate Bloglines Mobile partnership below are two different events roughly a year and a half apart. The article states plainly that Greenlight Wireless added RSS support "prompted by a recent survey of Skweezer users, which put mobile RSS access at the top of users wish list for the service" (quoted verbatim, missing apostrophe and all) — a user-requested feature, not part of a larger partnership announcement. Notably, the 2005 article makes no mention of Bloglines at all, no pricing is mentioned anywhere in it, and it doesn't spell out a specific list of supported devices beyond describing Skweezer generally as working on PDAs and cell phones. Where this article can't confirm a detail from the original piece, it says so rather than guessing.

What the RSS Feature Actually Did

Per the recovered text, the headline capability was straightforward: "Skweezer users can now read RSS feeds on their wireless handheld devices, such as PDA's or cell phones, without using a stand-alone RSS Reader." That phrasing indicates Skweezer built its own in-portal way of displaying feed content, rather than simply linking out to a separate reader app. Feed content was "compressed and reformatted with Skweezer's wireless optimization technology," and feeds could be bookmarked inside Skweezer for quick access from its homepage. What the article doesn't spell out is exactly how deep that reading experience went — a full aggregator with folders and read/unread tracking, or a simpler headline-list layered on Skweezer's existing reformatting engine. Given Skweezer's core business was reformatting linked content rather than running a dedicated feed-reader product, the more conservative reading is that it primarily let users browse headlines and open the linked stories in Skweezer's compressed format — but that's an inference from context, not something the article states outright. The article separately indicates registration wasn't required simply to browse or search, though a free personalized account was tied to Skweezer Mail, its bundled e-mail feature; whether an account was needed to save bookmarked feeds specifically isn't stated.

The September 2006 Bloglines Integration

Separately from Skweezer's own 2005 RSS feature, Greenlight Wireless and Bloglines announced an integration in September 2006, documented in independent contemporary blog coverage from that month. Bloglines Mobile already existed as a lightweight way to read feeds on a phone before this — feed content is generally small enough to display reasonably well on a handset without much help. What the integration specifically improved was what happened next: following an outbound link from a feed item to the source website, described in contemporary commentary as having been "practically useless" on mobile before the change, since that external page hadn't been through any optimization at all. After the integration, clicking through from a Bloglines Mobile feed item ran the destination page through Skweezer's reformatting first, and Bloglines set up a dedicated Skweezer-branded portal for searching posts, feeds, or the broader web. So the September 2006 announcement wasn't Skweezer gaining RSS reading for the first time — Bloglines was the reader, and Skweezer supplied the optimization layer applied specifically to links clicked from within it, with each product staying otherwise distinct.

Bandwidth, Taps, and Why Feeds Fit Small Screens

Set against the constraints above, feed-based reading was a genuinely sensible fit for mid-2000s devices. A page of headlines and short summaries is inherently lighter than a full page of navigation and imagery, so it loaded faster and cost less on a metered connection. It also cut down on navigation — rather than typing a URL, waiting for a homepage to load, and hunting for a story, a feed reader could present the interesting content directly, with fewer taps in between. Pairing that with a proxy service like Skweezer extended the benefit one step further, since the linked full stories a reader eventually opened were also compressed and reformatted rather than dropped onto a small screen unoptimized.

Skweezer vs Opera Mini

Opera Mini is a genuinely useful comparison, and not just because both tackled small screens and slow connections. Opera Mini was itself proxy-based, compressing pages on Opera's servers before sending them to the phone, which made it philosophically closer to Skweezer than to a conventional browser. Where the two diverged was RSS specifically: Opera Mini 3, which beta-launched November 1, 2006, and reached final release November 28, 2006, added its own built-in news reader for subscribing to and reading RSS feeds directly inside the browser. That's a genuinely different shape of feature — a browser vendor building feed reading into the client itself, rather than a portal service reformatting pages and feeds server-side. Neither approach is being declared better here; they arrived at "mobile devices need help with RSS" from different architectural starting points, on timelines a little over a year and a half apart.

Skweezer vs Dedicated RSS Readers

Dedicated mobile RSS reader apps existed in this period too, generally requiring a download and install rather than running through a browser. Skweezer's pitch was the opposite — no software to install, just a site visited through whatever browser a phone already had. The trade-off ran both ways: a dedicated app could offer deeper feed management and offline access, while a browser-based portal offered lower friction to start and worked across more devices without device-specific builds.

Skweezer vs WAP and Mobile-Specific Sites

Before responsive design existed, some sites built dedicated mobile or WAP versions of themselves — but that required the site's own operator to build and maintain a second version, and plenty of sites never bothered. A proxy service like Skweezer sidestepped that almost entirely: it worked on essentially any site, without needing that site's owner to do anything differently, since the reformatting happened on Skweezer's own servers rather than the destination site's. That generality was Skweezer's core pitch against dedicated mobile sites — broad compatibility instead of depending on individual operators to build mobile versions of their own content.

Skweezer vs Modern Responsive Design

Responsive web design — flexible layouts that automatically adapt to whatever screen they're viewed on — didn't take hold as a mainstream approach until years after Skweezer's RSS feature launched, and it fundamentally changes this comparison. A responsively designed site doesn't need a third-party proxy to reformat it, because the site already adapts. That's the central reason proxy-based mobile optimization mattered as much as it did in the mid-2000s: the web mostly wasn't adapting to mobile on its own yet, so an external layer had to do that work instead. Once responsive design and genuinely capable smartphone browsers became standard, much of the problem Skweezer solved simply stopped being a problem for actively maintained websites.

What Happened to Skweezer

Skweezer kept adding features for a few years after its RSS support launched, and the rough shape of that timeline is verifiable from reference material and contemporary coverage, even where exact technical detail isn't:

As smartphones with real, capable browsers became the norm, and as more of the web adopted responsive or otherwise mobile-friendly design on its own, the specific job a transcoding proxy did became less necessary for most everyday browsing. It's part of a broader pattern — other mobile-optimization and compression tools from roughly the same era have similarly faded in relevance as the underlying problem they were built to solve gradually disappeared.

FAQ

What was Skweezer?

A free, proxy-based web portal that reformatted and compressed ordinary websites so they'd load faster and display more usably on mid-2000s PDAs and cell phones.

Who created Skweezer?

Mobility Today's own 2005 coverage credits Greenlight Wireless. Some later reference sources instead credit a separate company, Skweezer, Inc., as the original developer — the exact corporate history isn't fully resolved here.

What did Skweezer do to webpages?

Reformatted and compressed them through a proxy server, offering view modes such as an image-light "PDA View" and an image-free "Text-only View" depending on the device and connection.

What were Skweezer RSS feeds?

In February 2005, Greenlight Wireless announced Skweezer could read RSS newsfeeds directly within its portal, without a separate stand-alone reader app, with feeds bookmarkable from the Skweezer homepage.

Could Skweezer read RSS feeds on a phone?

Yes — that was the core claim of the February 2005 announcement: reading RSS feeds on a PDA or cell phone through Skweezer itself, not through a separate reader application.

How did Skweezer work with Bloglines?

Separately, in September 2006, Bloglines Mobile integrated Skweezer's optimization technology so links clicked from within a feed item opened in a reformatted, mobile-friendly version instead of an unoptimized desktop page.

Why was mobile web optimization necessary in 2006?

Phones had small screens, slow and often expensive cellular data, and limited memory and processing power, while most websites were still built for desktop screens and fast wired connections — a mismatch that made many pages slow or unusable on a handset.

Was Skweezer similar to Opera Mini?

Both were proxy-based, compressing pages on a server before sending them to the phone, but Opera Mini was a full browser that later added its own built-in RSS reader (Opera Mini 3, November 2006), while Skweezer was a browser-agnostic portal site.

What happened to services like Skweezer?

As smartphones with capable native browsers became standard and more sites adopted responsive design on their own, demand for third-party transcoding proxies declined; reference sources describe Skweezer as inactive today.

Why are mobile web proxies less necessary today?

Because the problem they solved — desktop-oriented sites rendering poorly on small screens — is now largely addressed at the source, through responsive design and far more capable smartphone browsers.

Did the original Mobility Today article mention pricing?

No — the recovered February 2005 article doesn't mention pricing, and other contemporary Mobility Today coverage describes the core service as free to use.

Did Skweezer require registration to read RSS feeds?

The article doesn't say registration was required simply to browse or search; a free account was tied to Skweezer Mail specifically, and whether an account was needed to save bookmarked feeds isn't stated.

Reading the actual 2005 announcement rather than a secondhand summary makes clear that Skweezer's RSS story is really two separate moments: a February 2005 feature addition that let Skweezer read feeds inside its own portal, and a September 2006 partnership that instead brought Skweezer's page-optimization technology to an already-established reader, Bloglines Mobile. Both were reasonable answers to a genuine problem of their moment — phones that couldn't comfortably handle the modern desktop web — and both became largely unnecessary once smartphones and responsive design solved that problem from a different direction entirely.