Maintenance & Stability

← Back to SnapDock Index

Introduction

SnapDock is built around a long-term support philosophy. The goal is to provide a stable, predictable Markdown editor that behaves the same every time you open it. This section explains how updates work, what platforms are supported, and what to expect from the Classic lifecycle.

Update Channels

SnapDock includes a simple update indicator in the top-right corner of the window.

• Theme color → You’re on the latest version
• Yellow → A new update is available

When an update is available:

1. Click the “Update” button to download the latest release.
2. SnapDock will automatically restart after updating.

Important Notes

• Updating is optional — SnapDock continues working even if you stay on an older version
• Updates are designed to be small, safe, and non-disruptive
• SnapDock never forces updates

This keeps the experience predictable and user-controlled.

Known Issues

SnapDock is stable, but a few limitations exist:

• PDF export does not include natural page breaks.
• macOS builds are still in testing.
• Linux .deb and .AppImage builds are undergoing quality testing.
• Rapid file-tree switching may cause unsaved changes to be overwritten in rare cases.

These issues are monitored and addressed as part of ongoing maintenance.

Platform Support

SnapDock currently supports:

• Windows — fully supported
• Linux (.deb) — stable
• Linux (AppImage) — included and supported
• macOS — planned, in testing

Flatpak is not supported at this time. It may be considered for SnapDock 3.0 but is not part of the current Classic roadmap.

Classic Philosophy

SnapDock is an Classic-focused application, meaning:

• No major rewrites
• No framework churn
• No experimental UI changes
• No sudden feature removals

Updates focus on:

• Bug fixes
• Performance improvements
• Security patches
• Small quality-of-life refinements

This ensures SnapDock remains reliable for years without shifting under your feet.