desktop-update-architect
Architect-level desktop update design — update channels and staged rollout, delta and full packages, signature verification and rollback, migration of local data on upgrade, enterprise and offline installs, and the failure behaviour when an update is half applied. Use when the app must update itself after users have installed it.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- desktop-update-architect
- license
- MIT
- metadata
- { "crusor-path": "desktop-architect/delivery-architect/desktop-update-architect", "crusor-domain": "desktop-architect", "crusor-origin": "original", "crusor-sources": "electron.build/auto-update; v2.tauri.app/plugin/updater; sparkle-project.org; learn.microsoft.com/windows/msix", "crusor-triggers": "auto update, updater, update channel, delta update, rollback, staged rollout, forced update, electron-updater, sparkle, app upgrade", "crusor-verified-on": "2026-10-30" }
- description
- Architect-level desktop update design — update channels and staged rollout, delta and full packages, signature verification and rollback, migration of local data on upgrade, enterprise and offline installs, and the failure behaviour when an update is half applied. Use when the app must update itself after users have installed it.
- compatibility
- electron-updater, Tauri updater, Sparkle, MSIX, MSI, snap/flatpak
03 SKILL.md 正文
Desktop Update Architect
An updater is the only code that runs before your code exists. If it is wrong, users lose data, not just a feature.
When to use
- Shipping an app that updates itself.
- Adding channels (stable/beta), staged rollout, or forced-update policy.
- Data migrations tied to app versions.
When NOT to use
- Store-distributed apps where the store handles updates (still read the data migration sections).
- Web apps — deployment is the update.
Decision 1 — Mechanism
| Mechanism | Fit |
|---|---|
| built-in auto-updater (Squirrel/electron-updater/Tauri) | consumer apps, frequent releases |
| OS package (MSIX/MSI, pkg, snap/flatpak) | enterprise, managed fleets, admin control |
| Sparkle/appcast | macOS apps outside the store |
| manual download | rarely; support cost is permanent |
- Sign every package; the updater must verify the signature before applying.
- Update over HTTPS with an integrity hash and a pinned key.
- Enterprise/MDM deployments: respect "managed, do not self-update" and provide a silent install path.
Decision 2 — Channels and rollout
- Channels: stable, beta, internal. The channel is a persisted setting, not a build-time flag alone.
- Staged rollout by percentage or cohort, with a halt switch on error/crash-rate telemetry.
- Never auto-update a fleet on a Friday afternoon; schedule windows are part of the design.
- Version checks are cheap; package downloads are not. Poll on startup then daily.
Decision 3 — Applying an update
- Download in the background, apply on restart with a clear prompt.
- Delta updates where supported; full package as fallback.
- The apply step must be atomic: staging area + swap, not overwrite-in-place.
- Crash during apply → next launch detects the half-state and repairs or rolls back.
- Refuse to update while unsaved work exists, or offer "save and restart".
- Rollback keeps the previous version installed until the new one reports healthy.
Decision 4 — Data migrations
- Schema version stored in the local database, not inferred from app version.
- Migrations forward-only, idempotent, and wrapped in a transaction where possible.
- Back up the database before a migration; keep it until the first successful launch on the new version.
- A downgrade path is a real scenario (rollback after a bad release): either support reading the older schema or refuse to start with a clear message.
- Test migration on a real, large user database — not the dev fixture.
Decision 5 — Failure behaviour
- Offline or blocked CDN: continue working, retry later, never block launch.
- Signature mismatch or corrupt download: discard, log, alert, do not retry blindly.
- Update loop (fails, restarts, retries): bounded attempts, then surface a diagnostic and a manual link.
- Telemetry: version adoption, failure rate per stage, time-to-update after release.
Failure modes at scale
- Signature check disabled in a build "temporarily"; it never comes back.
- Migration crashes at launch for 5% of users with the oldest data.
- Rollback impossible: the new version upgraded the database irreversibly.
- Forced update with no offline path, bricking air-gapped customers.
- Crash at apply time leaving a half-installed app that will not start.
Verification receipts
- Signed package verified on a machine with the signature check enabled.
- Staged rollout halted mid-flight and confirmed.
- Migration tested on a real production-size database copy.
- Rollback rehearsed: install previous version, data intact.
- Update failure injection: corrupt package, offline, and interrupted apply.
04 同仓库更多 Skills
interaction-patterns-architect
Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.
design-system-ops-architect
Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.
design-handoff-architect
Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.
content-microcopy-architect
Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.
ui-ux-implementation-architect
Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.
test-strategy-architect
Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.