Handspring Blazer for Palm OS: Early Mobile Web Browsing



Long before smartphones made full web browsing routine, Handspring's Blazer was one of the first browsers to bring real HTML pages — not just stripped-down WAP decks — to a pocket-sized handheld. This is a historical restoration of the PalmGear listing for Handspring Blazer, the web browser that shipped on Handspring's Visor and Treo devices and later carried on under palmOne after Handspring merged into Palm in 2003. Blazer has been dead software for many years — its supporting proxy infrastructure was shut down in 2005 — and this page exists purely as a historical record, not a download source or an endorsement of current compatibility.

What Was Handspring Blazer?

Blazer was a web browser for Palm OS handheld computers, developed and marketed by Handspring, Inc. It let users on Handspring's Visor and Treo devices — and, for a period, other Palm OS handhelds — visit ordinary websites over a modem or wireless data connection, rather than being limited to sites specifically formatted for mobile phones. Handheld Computing Magazine reportedly named the original Blazer 1.0 its "Best Browser of 2000," a claim Handspring itself repeated in later PalmGear product descriptions.

The archived PalmGear listing restored here (product ID 36176, titled "Handspring Blazer - English UK") was a listing for Blazer version 2.0, priced as $19.95 shareware with a minimum requirement of Palm OS 3.5. A near-identical, separately catalogued PalmGear listing (product ID 33508) also sold Blazer 2.0; see the investigation notes at the end of this project for how the two listings relate.

From Bluelark Systems to Handspring

Blazer did not start out as a Handspring product. The original version was developed by a company called Bluelark Systems and released in November 2000. Handspring acquired Bluelark Systems just a month later, in December 2000, and folded the browser into its own product line under the Blazer name. Blazer 1.0 differentiated itself from competing Palm OS browsers of the era through progressive rendering (showing the top of a page while the rest was still loading) and support for HTML alongside the WAP and i-Mode (cHTML) markup languages used by many "mobile-friendly" sites of the time.

Handspring moved quickly to license the technology outward as well as bundle it with its own hardware. In April 2001, wireless ISP OmniSky became the first company to license Blazer's browser and proxy technology for its own service. The following month, Microsoft's MSN struck a content deal to become the default home page inside Blazer, supplying MSN MoneyCentral, Expedia, and MSNBC content optimized for the small screen. In September 2001, Handspring also licensed Blazer to Sprint PCS, which bundled it at no cost with Palm OS smartphones sold through Sprint, including the Kyocera QCP-6035 and Samsung I300.

Version History

Blazer went through several major architectural changes over its lifetime — most significantly, the switch away from a server-side proxy model starting with version 3.0. The table below summarizes what could be verified from contemporary press releases, PalmInfoCenter coverage, and encyclopedic summaries.

Note: Details for versions 4.1 through 4.5 above come from encyclopedic secondary sources (Wikipedia and its mirrors) rather than a primary Handspring/palmOne/ACCESS press release located during this research. Treat those specific version numbers and feature attributions as reasonably reliable but not fully primary-source verified.

The Proxy Server Architecture

Blazer 1.0 and 2.0 relied on a server-side proxy operated by Handspring (and later, under license, by partners such as OmniSky and Sprint PCS). Rather than a Palm OS device fetching and rendering a raw web page itself — well beyond what the hardware of the time could handle efficiently — Blazer sent the request through Handspring's proxy, which fetched the real page, transcoded it (recompressing images, reflowing tables and layout, and converting content into a format the handheld could render quickly), and sent back a much smaller, optimized payload. Handspring and OmniSky's April 2001 licensing announcement described this approach as being able to show "the first screen of almost any Web site in less than five seconds" over then-current wireless and dial-up connections, while the page continued loading progressively.

This proxy dependency was also Blazer 1 and 2's eventual undoing: because the browser could not render arbitrary pages on its own, it stopped working entirely once the proxy infrastructure was retired. Starting with Blazer 3.0 in 2003, Handspring (and later palmOne) moved away from this model, licensing ACCESS Co.'s NetFront browser engine to render pages natively on the device, which removed the hard dependency on a company-run proxy server for basic browsing.

Blazer and the Treo Line

Blazer shipped as the built-in web browser on essentially every Handspring and, later, palmOne Treo smartphone. What could be confirmed about specific version-to-device pairings:

Blazer was also licensed outside the Treo line — for example, to Sprint PCS for bundling with non-Handspring Palm OS smartphones, and later used on palmOne's Tungsten T5 and Tungsten E2 handhelds (which were not phones, but did support wireless or cradle-based data access).

This PalmGear Listing: Specifications

The specific PalmGear catalog entry this article restores (prodID 36176) listed the following details as of its archived snapshots:

Note that this PalmGear listing states a Palm OS 3.5 minimum, which is slightly higher than the Palm OS 3.1 floor commonly cited in broader summaries of Blazer's earliest releases; Handspring's own 2.0 product description on PalmGear specified "a minimum of 8MB of memory and Palm OS version 3.5 or higher" for that version specifically. Both figures come from period-accurate sources and are not necessarily in conflict — different Blazer versions had different minimums.

According to Handspring's description text preserved in this listing, Blazer 2.0 supported: multiple markup languages including HTML, WAP (WML/HDML), cHTML (i-Mode), and xHTML; adaptive text and image resizing for small screens; 16-bit (65,500-color) images where the handheld supported it; 128-bit SSL encryption for secure sites; full cookie support for site personalization; organizable bookmarks; and configurable HTTP proxy servers. A contemporary PalmInfoCenter review of Blazer 2.0 separately noted the browser did not support JavaScript and lacked copy-and-paste between applications — limitations that would later be addressed in the NetFront-based 3.0 release.

Licensing and Pricing

Both archived PalmGear listings for Blazer 2.0 (prodID 36176 and prodID 33508) priced it identically at $19.95 as shareware, distributed through PalmGear and Handango, with a 30-day money-back guarantee mentioned in Handspring's own description text. Blazer was, however, frequently given away for free when bundled: it shipped at no extra charge with Handspring's own devices (starting with the Treo 180), was offered free to VisorPhone Wireless Internet Access Suite purchasers as early as version 1.1, and was made available at no cost to Sprint PCS subscribers with compatible Palm OS smartphones starting in September 2001.

The Palm–Handspring Merger and palmOne

Palm, Inc. and Handspring announced a merger in June 2003; shareholders approved it that October, and the combined handheld-device business was rebranded palmOne. Blazer's development did not stop at the Handspring/PalmSource split — it continued under palmOne. This is documented directly: Blazer 3.0, built on ACCESS NetFront v3.0, shipped with the Treo 600 in October 2003 (the first Treo released after the merger was announced), and palmOne — not Handspring — was the company named in ACCESS Co.'s subsequent press releases about Blazer 4.0 (December 2004, debuting on the Tungsten T5) and about NetFront powering the Treo 650. In other words, Blazer survived the Handspring–Palm consolidation and remained palmOne's (and later Palm, Inc.'s, after the palmOne name was retired in 2005) default browser through the rest of the Palm OS Treo line.

End of Life

Blazer 1.0 and 2.0 depended entirely on Handspring/Palm's proxy servers to render pages. When that proxy infrastructure was shut down — reported as occurring around September 22, 2005 — both versions stopped working entirely, since they had no ability to fetch and render pages without it. This did not affect Blazer 3.0 and later, which rendered pages locally using the licensed NetFront engine rather than depending on a remote proxy. Blazer 4.5, released in May 2006 with the Treo 700p, was the last version released; it was never updated to support Adobe Flash, which meant it could not play embedded Flash video (including YouTube) directly, a limitation later devices worked around via mobile-optimized, non-Flash versions of those sites. Palm OS itself was discontinued as a maintained platform in the years that followed, and Blazer has not been updated since.

Frequently Asked Questions

Key Takeaways

• Blazer originated at Bluelark Systems (November 2000) and was acquired by Handspring one month later, in December 2000.
• This PalmGear listing (prodID 36176, "Handspring Blazer - English UK") documents version 2.0, submitted November 27, 2001, priced as $19.95 shareware requiring Palm OS 3.5.
• Blazer 1.0 and 2.0 relied on a Handspring-run compression/transcoding proxy server to render pages quickly on limited hardware.
• Starting with Blazer 3.0 (Treo 600, 2003), Handspring — and then palmOne — rebuilt the browser on ACCESS Co.'s NetFront engine, dropping the proxy dependency and adding JavaScript support.
• Blazer continued as palmOne's default Treo/Tungsten browser after the 2003 Palm–Handspring merger, through versions up to 4.5 (Treo 700p, May 2006), the final release.
• The original proxy infrastructure was shut down around September 22, 2005, permanently disabling Blazer 1.0 and 2.0.
• Blazer is discontinued, unmaintained software with no working proxy or update path; this article is a historical record only.