Isolation and reliability
Each module is initialized in a protected context. An exception at startup doesn’t block the app from launching — the other modules keep working.
Five layers with clear boundaries. The core knows nothing about modules, and modules know nothing about each other — they communicate only through service contracts.
Module loader, service registry, event bus, settings, background tasks and logging. The core knows nothing about specific modules.
Main window, dock manager, tab system, menus, toolbars and status bar. It defines how the workspace comes together.
Domain modules: each registers its own panels, commands, settings and permissions. They communicate only through service contracts.
Frameless window with Aero Snap, native notifications, tray, updates and installer. A Linux version is planned.
Public API, a module template, module development separate from the application, plugin signing.
Each module is initialized in a protected context. An exception at startup doesn’t block the app from launching — the other modules keep working.
Lazy panel loading, list virtualization for hundreds of thousands of rows, background tasks and repository-level caching.
Plugins are attached as separate assemblies and registered in the core registry at startup. No need to rebuild the app.
We’ll show how DockStudio fits into your existing landscape and what can be carried over from your current app.
We reply during business hours. If it's urgent, Telegram is the fastest way.