Explore the work 01 / INTERFACE ENGINEERING
A desktop that preserves the work.
A shared workspace for tools, records, and documents—with window behavior that keeps the work intact.
Try the working showcaseSELECTED ENGINEERING / MICHEAL CUNNINGHAM
The work.
And how it works.
A closer look at custom interfaces, connected business systems, and authoring tools from my platform work.
Explore the work 
Explore the work 02 / BUSINESS APPLICATIONS
Keep the customer in context.
Customer records, project work, and inventory meet in a workspace designed around the next useful action.
Try the working showcase
Explore the work 03 / AUTHORING & APPLIED AI
An editor that belongs to the product.
Structured documents, customer references, and reviewable writing assistance live in the same working surface.
Try the working showcase01 / Selected engineering work
The interface. The platform.
The intelligence inside it.
My work spans Nexus RMM, the wider ElementalOS architecture, and custom component systems. Desktop-style workspaces, business operations, document authoring, device management, and AI—all parts of an application people can actually work in.
01 / CUSTOM INTERFACES & COMPONENTS
A desktop experience.
Inside the application.
A browser-based desktop interface with overlapping windows, a persistent taskbar, an application launcher, and file management. Documents and tools share a workspace instead of sending the user through a trail of disconnected pages.
- Window focus, resizing, minimizing, maximizing, and restoring
- Desktop and context menus, calendar popovers, and application views
- Reusable React components, shared styling, and composed workspaces
Nexus Desktop · Custom desktop shell and component work
Desktop shellThe shared application environment
Window managementFocus · resize · minimize · restore
Application views
Files & documents
Editors & terminal
Settings & workspaces
Shared components
Taskbar & launcher
Context menus
Calendar & slideouts
Custom behavior, reusable components, one coherent interface.
02 / BUSINESS PLATFORM ENGINEERING
PMO. CRM. Inventory.
Built to connect.
My platform work includes both business modules and the shared architecture underneath them: identities, permissions, relationships, and data.
Project management & PMO
Project workspaces, planning, task organization, schedules, and the relationship between project work and service tickets.
Projects · Tasks · Planning · Ticket relationshipsCRM & customer operations
Leads, qualification-to-deal workflows, contacts, customer records, imports, and the context connecting customer activity to the rest of the platform.
Leads · Deals · Contacts · Customer contextInventory & procurement
Asset and license records, purchase orders, vendor contacts, and procurement workflows connected to the organizations and systems they support.
Assets · Licenses · Vendors · Purchase orders03 / CUSTOM EDITORS
An authoring system,
inside the product.
Custom document and proposal editing with rich text, structured content, and business context. My work goes beyond an editable field to the tools people use to create, reuse, and deliver documents.
- Custom tables, reusable blocks, templates, and configurable toolbars
- Slash commands, record bindings, speech-to-text, and inline agents
- PDF generation for quotes, contracts, invoices, and tickets
- Checklists, structured records, and integrated e-signing
Document workflows · Rich authoring · Business records
04 / AI-NATIVE APPLICATIONS
AI that belongs
in the workflow.
I’ve built AI into application surfaces and architected the connections between models, business context, and tools. The interaction belongs where the user is already doing the work.
- Inline assistance inside editors and application workspaces
- Tenant-scoped AI connections and tool integrations
- Shared customer, document, ticket, and project context
- Advisory and assisted workflows with controlled execution
Context. Permission. Action. Evidence.
What the assistant can see and do is part of the application architecture.
05 / UEM & SYSTEMS INTEGRATION
Where software meets
the systems around it.
My device-management work spans endpoint operations, inventory, enrollment, and the integration architecture connecting external systems to a shared application.
Endpoint operations
Windows agents, patching, remote shell and access, signed scripting, and device lifecycle workflows.
Connected platforms
Microsoft 365, Google Workspace, Jamf, RMM tooling, and network-controller integrations.
UEM architecture
Cross-platform enrollment, policy, inventory, and command workflows with tenant and permission boundaries.
02 / The engineering behind the work
How it gets built.
How it stays accountable.
Developer tooling & delivery workflows
I’ve worked on the development environment as well as the product: Forge’s code, wireframe, and canvas workspaces, plus the workflow around planning, implementation, review, and release.
- Engineering workspaces
- Repository navigation, editors, terminals, and visual design surfaces.
- Development lifecycle
- Issues, branches, pull requests, review, CI, and release evidence.
- Maintainable delivery
- Reusable components, readable code, documented decisions, and tests of the behavior that matters.
Compliance, governance & safety engineering
Governance work includes the application controls and evidence needed to understand who acted, what they were allowed to do, and what the system actually changed.
- Identity & isolation
- Role-based access, tenant boundaries, PostgreSQL row-level security, and two-factor authentication.
- Controlled actions
- Signed automation, approval boundaries, and constrained AI actions.
- Evidence & recovery
- Audit records, execution history, recoverable failures, and reviewable changes.
Something you want to build?
Let’s work through it.Work directly with me on the architecture, the application, and the details that make it useful.