Skip to content
Big Picture

Electron, Tauri, and other Cross-Platform Desktop Apps

Cross-platform desktop applications built with Electron, Tauri, or similar frameworks ship the same codebase to Windows, macOS, and Linux. These applications benefit from unified release governance that coordinates updates across platforms while respecting platform-specific requirements.

Big Picture provides platform-agnostic release governance. You publish releases once, and Big Picture coordinates deployment across Windows, macOS, and Linux according to platform-specific policies and staged rollout rules.

When This Scenario Applies

Section titled “When This Scenario Applies”

This scenario applies when you ship:

  • Electron-based applications
  • Tauri applications
  • Other cross-platform desktop frameworks
  • Applications that target Windows, macOS, and Linux from a single codebase

Big Picture manages release governance and licensing for cross-platform applications, coordinating updates across platforms while maintaining platform-specific controls.

How Big Picture Addresses This

Section titled “How Big Picture Addresses This”

Unified Release Governance

Section titled “Unified Release Governance”

You publish releases once through Big Picture, specifying which platforms each release supports. Big Picture coordinates deployment across platforms according to:

  • Platform-specific update policies
  • Staged rollout rules that can vary by platform
  • Channel assignments that may differ by platform
  • Tenant policies that can specify platform-specific requirements

This creates a unified release process while respecting platform differences.

Platform-Specific Considerations

Section titled “Platform-Specific Considerations”

Big Picture supports platform-specific policies and requirements:

  • Code signing requirements differ by platform (Windows code signing, macOS notarization, Linux package signing)
  • Update mechanisms vary by platform (Windows installers, macOS DMG, Linux packages)
  • Enterprise deployment tools differ by platform (Intune/SCCM for Windows, MDM for macOS, package managers for Linux)

Big Picture’s policy system allows you to specify platform-specific update actions (AUTO_INSTALL, NOTIFY, MANAGED_BY_IT) while maintaining unified release governance.

Cross-Platform Release Coordination

Section titled “Cross-Platform Release Coordination”

When releasing updates that affect multiple platforms:

  • Publish releases with platform-specific artifacts
  • Configure staged rollouts that can progress independently by platform
  • Set platform-specific policies that reflect IT requirements for each platform
  • Coordinate version numbering across platforms while allowing platform-specific patch versions

Big Picture tracks deployment status per platform, giving you visibility into how updates progress across Windows, macOS, and Linux.

Native Module Compatibility

Section titled “Native Module Compatibility”

Applications with native modules must ensure compatibility across platforms. Big Picture supports:

  • Platform-specific release channels for testing native module compatibility
  • Staged rollouts that allow platform-specific testing before broader deployment
  • Version pinning that allows customers to stay on compatible versions while issues are resolved

This helps manage the complexity of native module compatibility across platforms.

Key Considerations

Section titled “Key Considerations”

Code Signing Across Platforms

Section titled “Code Signing Across Platforms”

Each platform has different code signing requirements:

  • Windows requires code signing certificates and timestamping
  • macOS requires notarization through Apple’s notary service
  • Linux typically uses package signing through distribution-specific mechanisms

Big Picture verifies signatures on update decisions but does not perform code signing. You handle platform-specific signing as part of your build process, and Big Picture verifies signatures when making update decisions.

Update Mechanisms

Section titled “Update Mechanisms”

Different platforms use different update mechanisms:

  • Windows applications often use installers or update frameworks like Squirrel
  • macOS applications typically use Sparkle or custom update mechanisms
  • Linux applications may use package managers or custom update mechanisms

Big Picture works with any update mechanism. It provides signed update decisions that your application’s update mechanism can act on, regardless of platform.

Enterprise Deployment

Section titled “Enterprise Deployment”

Enterprise customers may use different deployment tools per platform:

  • Windows: Intune, SCCM, or Group Policy
  • macOS: MDM solutions or manual deployment
  • Linux: Package managers, configuration management tools, or manual installation

Big Picture’s MANAGED_BY_IT mode works across platforms, allowing IT departments to deploy updates through their preferred tools while maintaining vendor control over release decisions.

Version Coordination

Section titled “Version Coordination”

Coordinate version numbering across platforms while allowing platform-specific patch versions when needed. Big Picture supports semantic versioning and can track platform-specific versions while maintaining a unified release identity.

Next Steps

Section titled “Next Steps”