How Apple Built Developer Support for Mac OS 9 Sherlock
When Apple launched Mac OS 9 in 1999, it turned Sherlock from a local file search tool into an extensible Internet search engine known as Sherlock 2. To ensure the utility gained widespread utility, Apple actively courted third-party developers and web services to build custom search plugins. By utilizing an accessible, text-based specification, integrating built-in distribution mechanisms, providing extensive documentation, and offering prominent placement within the operating system, Apple lowered the barrier to entry and motivated thousands of developers to expand the Sherlock ecosystem.
Accessible, Text-Based Plugin Architecture
Apple eliminated the technical friction of plugin development by
basing Sherlock plugins on plain text files using the .src
extension. Instead of requiring developers to write, compile, and debug
complex C or C++ binaries using CodeWarrior, Apple created an HTML-like
markup format.
A standard .src file only required developers to
define:
- The target search engine URL and form parameters
(
<search>). - Input fields and user-facing options
(
<input>). - Delimiters to parse and isolate return results
(
<interpret>).
Because the format was interpreted at runtime, any webmaster or hobbyist could create a functioning search plugin in minutes using a basic text editor like SimpleText.
Built-In Visibility via "Channels"
Sherlock 2 introduced themed search "Channels," categorizing search queries into distinct interfaces such as Internet, People, Shopping, News, and Reference. Apple leveraged this interface by partnering directly with major brands—including Amazon, eBay, Barnes & Noble, and CNN—and bundling their plugins directly into the operating system.
Seeing these high-profile integrations demonstrated the commercial value of Sherlock plugins to other developers. Inclusion in a user's channel menu provided direct desktop access to external websites without requiring the user to open a web browser first, incentivizing businesses to write custom plugins to drive traffic to their platforms.
Frictionless Distribution and Installation
Apple built frictionless installation mechanisms to make distributing
plugins easy for third parties. Developers could distribute
.src files directly from their websites via standard HTTP
links. When an end user clicked a link associated with the Sherlock MIME
type (application/x-sherlock-search-plugin), Mac OS
automatically recognized the file and installed it into the
Internet Search Sites folder within the System Folder.
Alternatively, developers could instruct users to simply drag and
drop the .src file (and an optional 16x16 icon file) onto
their active Sherlock window to install it instantly.
Comprehensive Developer Documentation and Sample Code
Apple actively supported developers through the Apple Developer Connection (ADC). The company published detailed reference guides that broke down the entire Sherlock plugin specification, explaining form field encoding, variable passing, and regular expression-like parsing tags. Apple also provided pre-configured templates and sample plugins that developers could reverse-engineer to support their own search engines and online catalogs.