EN
Back to the archive

The archive · Product Ideas · Technical decision · 2007–2009

BBSmart Email Viewer: a UI-stack trick made BlackBerry's top-selling app

To fix BlackBerry's broken HTML email, a solo dev covered the native viewer with his own screen and drove its hidden menus; the app sat at #1 for years.

BBSmart

The ideaIntercept every email the user opens, cover the native viewer with your own HTML-rendering screen, and run the hidden app's own menus to keep all native functions.substantial

What it had to solve

BlackBerry's pitch was email, but its native client rendered HTML mail as tag soup, and no APIs existed to build a rival client or to swap a core app. Around 2007, before the iPhone and Android app stores, the 23-year-old Neil Sainsbury set out to make BBSmart Email Viewer anyway.

How it works

In the mid-2000s BlackBerry was the business email device, yet its native email client could not render HTML messages and would choke, spitting out tag soup. There were no APIs for building an alternative email client and none for substituting a core app the way Android later allowed. Sainsbury, a young developer at his company BBSmart, decided the problem was worth a hack.

The first trick was a listener. BBSmart registered for email-open events on the mail session, and when the user opened a message the handler used the global UiApplication reference to reach the current UI stack. It then pushed its own screen, an HTMLField showing cleaned-up formatted email, directly on top of the native display screen, which stayed open in the background. Closing the email popped both screens, so the swap was invisible to the user.

The second trick kept every native function. Reply, attachments and jumping between unread emails had no public APIs, so BBSmart reached back into the hidden native screen, pulled out its menu, found the matching menu item by name, and invoked it. From the user's perspective BBSmart Email Viewer was a seamless in-place replacement of the built-in mail client that also rendered HTML email properly.

Released in 2007 and sold through fragmented channels like MobiHand, Handango and carrier webstores, the app went straight to the top of the best-seller lists and stayed there for one to two years. It produced several enterprise license purchases above 10,000 seats and one mass US-carrier deployment, and it made Sainsbury a known name in the small BlackBerry developer world.

Why it lands

  • The problem was undeniable: BlackBerry sold itself on email while its own client mangled HTML mail, so an alternative viewer had a ready and desperate audience.
  • The mechanism inverted the platform's weakness: no API replaced core apps, yet the live UI stack was reachable from a listener, so the swap was built from the screen layer downward.
  • Borrowing the hidden app's own menu gave full parity: invoking the native Reply and attachment items meant no re-implementation of device or server integration and nothing users had to relearn.
  • Seamlessness made it sellable: because both screens were popped on close, the product read as the natural mail experience, not an add-on bolted onto the phone.

What it did

BBSmart Email Viewer jumped to the top of the major BlackBerry storefronts on release in 2007 and stayed literally #1 day in, day out for one to two years, with glowing press reviews, several 10,000+ license enterprise purchases, and one mass deployment by a US carrier. Sainsbury later joined BlackBerry's Developer Relations team and ran it; his 2020 tell-all drew 234 points and 68 comments on Hacker News.

Their siteBBSmart Email Viewer source code on GitHub

What you can take

When a platform denies what users need, look for a seam in the running app: intercept the trigger moment, cover the native screen with yours, and borrow the hidden app's own functions.

Since then

Sainsbury kept the mechanism secret for years while developers emailed weekly asking how it worked; a rival eventually copied the app almost verbatim, he says. He kept shipping successors like BBSmart Alarms Pro, then joined BlackBerry's Developer Relations team and later directed it. In March 2020, with commercial interests expired, he open-sourced the code and explained the trick; the post hit the Hacker News front page, where commenters called it a business built on a hack. The BlackBerry era was closing, yet the case stands as a best-seller assembled from one unsupported API observation.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe the brief you are staring at, and see who has been given the same problem.

Free account · 3 free questions · no card

Related cases