Skip to content

Feature request: Safari extension support for PearPass #557

Description

@aerisvagrant

Hi PearPass team,

I would like to request an official Safari extension for PearPass.

Requested feature

Please consider adding Safari support for the PearPass browser extension, ideally for macOS first, and iOS/iPadOS if technically feasible.

The Safari extension should support the same core workflows as the existing browser extension where possible:

  • Autofill saved logins and identities.
  • Detect login forms and suggest matching vault entries.
  • Create and use passkeys on websites that support WebAuthn.
  • Generate strong passwords.
  • Communicate with PearPass Desktop through the native app bridge or an equivalent Safari-compatible mechanism.
  • Respect the existing local-first and end-to-end encrypted PearPass security model.

Suggested implementation direction

Since Safari supports Web Extensions, it may be possible to reuse part of the existing PearPass browser extension codebase and adapt the packaging, permissions, native messaging / app bridge, and distribution flow for Safari.

The minimum useful version would be:

  • Safari extension for macOS.
  • Works with the PearPass Desktop app.
  • Supports autofill for logins and identities.
  • Supports vault unlock / vault selection flow consistently with the existing extension.
  • Provides clear setup instructions for pairing the Safari extension with the desktop app.

Future improvements could include:

  • iOS/iPadOS Safari support, if Apple platform constraints allow it.
  • Passkey creation and authentication parity with the existing browser extension.
  • App Store distribution for easier installation and updates.

Why this matters

Safari is the default browser on macOS, iOS, and iPadOS. Without Safari support, users in the Apple ecosystem need to switch browsers just to use PearPass autofill and passkey workflows.

An official Safari extension would make PearPass more viable as a daily password manager for Mac users and would improve browser coverage alongside Chrome/Chromium and Firefox-related work.

Thanks for considering this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions