Top Qs
Timeline
Chat
Perspective

Site-specific browser

Software application dedicated to accessing a single website From Wikipedia, the free encyclopedia

Site-specific browser
Remove ads

A site-specific browser (SSB) is a software application dedicated to accessing pages from a single source (site) on a computer network such as the Internet or a private intranet. SSBs typically simplify the more complex functions of a web browser by excluding the menus, toolbars and browser graphical user interface associated with functions that are external to the workings of a single site.[1]

Thumb
Screenshot showing Wikipedia website running in a site-specific browser window created by Fluid on Mac OS X
Thumb
GNOME Web (previously called Epiphany) showing Wikipedia in Web Application mode

Modern site-specific browsers range from simple browser windows without navigation controls to sophisticated desktop applications built with frameworks like Electron that bundle entire browser engines. This evolution has enabled many popular desktop applications to be built using web technologies, effectively making them advanced site-specific browsers.[2]

Remove ads

History

Summarize
Perspective

Early development

One of the earliest examples of an SSB was MacDICT, a Mac OS 9 application that accessed various websites to define, translate, or find synonyms for words typed into a text box. However, the first general-purpose SSB is considered to be Bubbles, which launched in late 2005 on the Windows platform.[3] Bubbles introduced the term "Site Specific Extensions" for SSB userscripts and created the first SSB JavaScript API.

In 2007, Mozilla announced Prism (originally called WebRunner), a project to integrate web applications with the desktop.[4] That same year, Todd Ditchendorf, a former Apple Dashboard engineer, released Fluid for macOS.[5]

On 2 September 2008, Google Chrome was released with a built-in "Create application shortcut" feature, bringing SSB functionality to mainstream users.[6] This feature allowed any website to be launched in a separate window without the browser interface.

Modern era

The landscape of site-specific browsers changed dramatically with the introduction of Electron in 2013 (originally called Atom Shell).[7] Electron combined Chromium and Node.js into a single runtime, enabling developers to build desktop applications using web technologies. This framework has since powered applications used by hundreds of millions of users, including Visual Studio Code, Slack, Discord, and Microsoft Teams.[8]

In 2015, the concept of Progressive Web Apps (PWAs) was introduced by Google engineers Alex Russell and Frances Berriman, representing a parallel evolution in web-to-desktop technology.[9] While PWAs share similar goals with SSBs, they follow web standards and can be installed directly from browsers.

More recently, alternative frameworks like Tauri have emerged, offering significantly smaller application sizes by using the system's native web renderer instead of bundling Chromium.[10]

Remove ads

Technical implementation

Site-specific browsers can be implemented through various approaches:

Browser-based SSBs

The simplest form of SSB is created through browser features that allow websites to run in separate windows without the standard browser interface. Modern Chromium-based browsers offer "Install as app" or "Create shortcut" functionality that creates a dedicated window for a specific website. These SSBs share the browser's underlying engine and resources but operate in isolated windows.

Framework-based SSBs

More sophisticated SSBs are built using application frameworks:

  • Electron: Bundles a complete Chromium browser with Node.js, resulting in applications of 85MB or larger. Each Electron application runs its own browser instance, providing full access to system APIs but consuming significant resources.[11]
  • Tauri: Uses the operating system's native web rendering engine (WebView2 on Windows, WebKit on macOS, and WebKitGTK on Linux), resulting in applications typically 2.5-10MB in size.[12]
  • Other frameworks: Include Neutralino.js (ultra-lightweight using system browser), Wails (Go-based), and the Chromium Embedded Framework (CEF).
Remove ads

Comparison with Progressive Web Apps

While site-specific browsers and Progressive Web Apps (PWAs) share the goal of bringing web content to the desktop, they differ in several key aspects:

More information Aspect, Progressive Web Apps ...

Applications

Site-specific browsers have become the foundation for many popular desktop applications:

Communication and collaboration: Many modern communication tools are built as SSBs, including Slack, Discord, Microsoft Teams, and WhatsApp Desktop. These applications benefit from web-based development while providing desktop integration.

Development tools: Visual Studio Code, used by 73.6% of developers according to Stack Overflow's 2024 survey,[14] is built with Electron, as are Atom and GitHub Desktop.

Productivity software: Applications like Notion, Obsidian, and various project management tools use SSB technology to provide consistent experiences across platforms.

Remove ads

Security and performance

Memory usage

Framework-based SSBs, particularly those using Electron, are known for high memory consumption. Studies show Electron applications typically use 120-300MB at baseline, with complex applications consuming significantly more.[15] This is approximately 5-10 times more memory than equivalent native applications.

Security considerations

SSBs can provide security benefits through process isolation, where each application runs in its own sandboxed environment. However, bundling an entire browser engine also means each application must be updated independently to patch security vulnerabilities. Research presented at the Network and Distributed System Security (NDSS) Symposium has identified various security challenges specific to Electron applications.[16]

Bundle sizes

The choice of framework significantly impacts application size:

  • Electron applications: 85MB+ (includes full Chromium)
  • Tauri applications: 2.5-10MB (uses system WebView)
  • Browser-based SSBs: No additional download (uses existing browser)
Remove ads

Software

Summarize
Perspective

Browser support

Most modern browsers provide some form of SSB functionality:

Standalone tools

Active

  • WebCatalog (Windows, macOS, Linux) - Manages multiple SSBs with isolated storage
  • Fluid (macOS) - Pioneering SSB creator for Mac
  • Unite (macOS) - Creates SSBs with customization options
  • Coherence X (macOS) - Advanced SSB creation tool
  • Pake (cross-platform) - Open-source SSB creator
  • Wavebox (cross-platform) - Workspace browser with SSB features

Discontinued

  • Mozilla Prism - Cross-platform SSB creator (discontinued 2011)
  • Nativefier - Command-line SSB creator (discontinued 2023)
  • Epichrome - macOS SSB creator (discontinued 2021)

Development frameworks

  • Electron - Most popular framework, bundles Chromium and Node.js
  • Tauri - Rust-based framework using system WebView
  • Chromium Embedded Framework (CEF) - C++ library for embedding Chromium
  • Neutralino.js - Lightweight framework using system browser
  • Wails - Go-based framework for web frontends
Remove ads

See also

References

External links

Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.

Remove ads
Remove ads