Milestones
List view
**SnapDock Phoenix** marks the beginning of a new era for SnapDock. After the experimental and feature‑heavy v3 series, Phoenix represents a full architectural rebirth — shedding Electron, modernizing the entire codebase, and laying a stable foundation for the future of the project. Phoenix will run alongside SnapDock v3 for as long as needed. The v3 branch will continue receiving maintenance updates while Phoenix evolves toward stability. Once Phoenix is ready, it will replace v3 as the mainline version. --- ## **Goals & Deliverables** ### **1. Migration to Tauri (Native Engine)** Phoenix replaces Electron with **Tauri**, delivering: - dramatically reduced memory usage - faster startup times - native system integration - improved security - smaller bundle sizes - a long‑term maintainable architecture This is the core of the Phoenix transformation. --- ### **2. Full TypeScript Rewrite** The entire codebase will be rewritten from JavaScript to **TypeScript**, providing: - strict typing - safer refactoring - clearer API boundaries - more predictable behavior - better tooling and editor support This rewrite is essential for long‑term stability and scalability. --- ### **3. Tailwind UI Modernization** Phoenix replaces custom CSS with **Tailwind**, giving SnapDock: - consistent styling - cleaner component structure - faster UI development - reduced CSS complexity - a modern, scalable design system This sets the stage for future UI improvements without CSS debt. --- ### **4. Native Multi‑Channel Updater** Phoenix introduces a **custom updater** designed to support: - stable - beta - edge - RC - and custom channels This updater works **outside** of store ecosystems, allowing: - v3 and v4 to update independently - strict version boundaries - safe migrations - controlled experimental releases - Snap Store channel alignment This solves the limitations of Electron’s updater and ensures v4 can evolve safely. --- ## **Project Identity** **Phoenix** symbolizes SnapDock’s rebirth — rising from the Electron era into a cleaner, faster, native foundation with room to scale. It is not just a rewrite; it is the beginning of SnapDock’s stability era. --- ## **Revenue Angle (Non‑Blocking Future Exploration)** SnapDock will always remain **free**. However, Phoenix introduces the groundwork for optional future services such as **SnapDock Publish** — a potential document‑publishing portal allowing users to share documents publicly without needing to build their own website or hosting infrastructure. This is exploratory and not part of the core v4 deliverables, but Phoenix’s architecture makes it possible. --- ## **Branch Strategy** - **`v4-phoenix`** — active development branch - **`v3-maintenance`** — Electron era, maintained until Phoenix is stable - **`v2-classic`** — permanent legacy branch - **`main`** — will point to Phoenix once stable Phoenix will run alongside v3 until fully stable. --- ## **Summary** SnapDock Phoenix v4.x.x is the largest evolution in SnapDock’s history. It replaces the engine, the language, the UI system, and the updater — creating a modern, native, stable foundation for everything SnapDock will become. ---
No due date