Register in installer manifest for custom extensions - platform-specific setup.

GUI Best Practices

Responsive, portable, maintainable desktop applications in Rust.

How to Use This List

Apply A-B when choosing framework and sketching architecture.
Complete C-D before first beta release.
Revisit E after user reports of freezes, data loss, or install failures.

A - Architecture

Separate domain logic from UI rendering. Pure functions test without window.
One authoritative state store for security-sensitive data. JS view models mirror, not own, secrets.
Message/command enum for user intents. Avoid scattered bool toggles across modules.
Feature folders or workspace crates past ~3k LOC. main.rs god files do not scale.
Debounce persistence for text fields. Save settings 300ms after last edit.

B - UX and Performance

Never block UI on HTTP, crypto, or large file IO. Background worker + progress events.
Show progress for operations >300ms. Indeterminate spinner beats frozen window.
Handle errors with actionable messages. Map std::io::ErrorKind to user text.
Support OS dark mode or explicit theme toggle. Respect dark-light detection.
Keyboard shortcuts for primary actions. Power users expect them in desktop apps.

C - Security and Privacy

Validate all Tauri command inputs. Path traversal and injection start at IPC boundary.
Strict CSP for web UI assets. XSS must not become invoke abuse.
Store credentials in OS keychain, not plaintext config. keyring crate per platform.
Scope filesystem permissions minimally in Tauri capabilities. Default deny outbound paths.
Log diagnostics without PII or file contents. Paths may be sensitive.

D - Packaging and Release

Code sign macOS and Windows artifacts. Unsigned builds fail enterprise rollout.
Test installer on clean VM for each OS. Catch missing VC++ redist or WebView2 runtime.
Semantic version + changelog for updater. Users need to know breaking changes.
Verify updater signatures before apply. Never HTTP-only update channel.
Ship crash reporting with symbol upload. Debug otherwise useless in release builds.

E - Maintenance

Pin Tauri/iced/egui versions in CI. GUI crates evolve quickly.
Screenshot/visual regression optional but valuable for iced/egui. Catch layout breaks.
Accessibility: prefer native/web patterns when a11y required. egui gaps documented to stakeholders.
Localize strings early with fluent/gettext. Retrofit i18n is expensive.
Document auto-start, tray, and notification behavior. Support tickets follow mystery background apps.

FAQs

Best framework?

Tauri if team knows web; iced for native MVU; egui for tools - see GUI Basics.

Biggest perf mistake?

Blocking UI thread - always channel async results back to render loop.

Tauri security model?

Rust commands are trust boundary; CSP and scoped FS contain web content risks.

Testing strategy?

Unit test domain; integration test commands; manual VM install test per release.

Cross-platform parity?

Accept minor platform differences; document macOS vs Windows shortcut labels.

File associations?

Offline mode?

Queue network ops; show offline banner; sync on reconnect with conflict rules.

Large lists in UI?

Virtualize rows in web UI; paginate or window in egui/iced tables.

Updates without Tauri?

Manual download page or third-party updater - still require signature verify.

State deep dive?

State & Architecture for MVU and channels.

GUI Basics - framework map
Packaging & Distribution - release mechanics
State & Architecture - structure
Tauri - IPC security

Stack versions: This page was written for Rust 1.97.0 (edition 2024), Tokio 1.x, Axum 0.8, serde 1.0, sqlx 0.8, clap 4, and Polars 0.46+.

GUI Best Practices

Responsive, portable, maintainable desktop applications in Rust.

How to Use This List

Apply A-B when choosing framework and sketching architecture.
Complete C-D before first beta release.
Revisit E after user reports of freezes, data loss, or install failures.

A - Architecture

Separate domain logic from UI rendering. Pure functions test without window.
One authoritative state store for security-sensitive data. JS view models mirror, not own, secrets.
Message/command enum for user intents. Avoid scattered bool toggles across modules.
Feature folders or workspace crates past ~3k LOC. main.rs god files do not scale.
Debounce persistence for text fields. Save settings 300ms after last edit.

B - UX and Performance

Never block UI on HTTP, crypto, or large file IO. Background worker + progress events.
Show progress for operations >300ms. Indeterminate spinner beats frozen window.
Handle errors with actionable messages. Map std::io::ErrorKind to user text.
Support OS dark mode or explicit theme toggle. Respect dark-light detection.
Keyboard shortcuts for primary actions. Power users expect them in desktop apps.

C - Security and Privacy

Validate all Tauri command inputs. Path traversal and injection start at IPC boundary.
Strict CSP for web UI assets. XSS must not become invoke abuse.
Store credentials in OS keychain, not plaintext config. keyring crate per platform.
Scope filesystem permissions minimally in Tauri capabilities. Default deny outbound paths.
Log diagnostics without PII or file contents. Paths may be sensitive.

D - Packaging and Release

Code sign macOS and Windows artifacts. Unsigned builds fail enterprise rollout.
Test installer on clean VM for each OS. Catch missing VC++ redist or WebView2 runtime.
Semantic version + changelog for updater. Users need to know breaking changes.
Verify updater signatures before apply. Never HTTP-only update channel.
Ship crash reporting with symbol upload. Debug otherwise useless in release builds.

E - Maintenance

Pin Tauri/iced/egui versions in CI. GUI crates evolve quickly.
Screenshot/visual regression optional but valuable for iced/egui. Catch layout breaks.
Accessibility: prefer native/web patterns when a11y required. egui gaps documented to stakeholders.
Localize strings early with fluent/gettext. Retrofit i18n is expensive.
Document auto-start, tray, and notification behavior. Support tickets follow mystery background apps.

FAQs

Best framework?

Tauri if team knows web; iced for native MVU; egui for tools - see GUI Basics.

Biggest perf mistake?

Blocking UI thread - always channel async results back to render loop.

Tauri security model?

Rust commands are trust boundary; CSP and scoped FS contain web content risks.

Testing strategy?

Unit test domain; integration test commands; manual VM install test per release.

Cross-platform parity?

Accept minor platform differences; document macOS vs Windows shortcut labels.

File associations?

Offline mode?

Queue network ops; show offline banner; sync on reconnect with conflict rules.

Large lists in UI?

Virtualize rows in web UI; paginate or window in egui/iced tables.

Updates without Tauri?

Manual download page or third-party updater - still require signature verify.

State deep dive?

State & Architecture for MVU and channels.

GUI Basics - framework map
Packaging & Distribution - release mechanics
State & Architecture - structure
Tauri - IPC security

Stack versions: This page was written for Rust 1.97.0 (edition 2024), Tokio 1.x, Axum 0.8, serde 1.0, sqlx 0.8, clap 4, and Polars 0.46+.

GUI Best Practices

Buscar en la documentación

GUI Best Practices