Electron Developer - Desktop Companion App for Music Hardware

Overview We're building a companion desktop application (macOS and Windows) for a purpose-built music hardware device. The app is the primary management tool for the device — users configure it, organize their content, and sync everything to the unit before use. This is not a secondary feature. The desktop app is the main interface between the user and the device, and it needs to feel and behave like a polished, professional application. We're looking for a developer who has shipped production Electron apps and understands what that means: correct code signing, notarization, auto-updates, and cross-platform behavior from day one — not retrofitted at the end. The scope is well-defined. We have a detailed product specification, a component-level style guide, and fully built HTML/CSS/JS prototypes covering approximately 98% of screens and interactions. The developer's job is to build the Electron application from those assets — not to design or define the product. Engagement structure Work is organized into four milestones with a clear dependency chain. Each milestone must be complete and stable before the next begins. We're open to one developer handling the full scope or different developers across milestones — but every handoff needs to leave the codebase in a state the next person can build on without rearchitecting. Submit your proposal including per-milestone or project pricing and a brief breakdown of your approach to each one. Milestone 1 — Foundation and Architecture Electron shell, main/renderer IPC structure, workspace file format (read, write, and safe atomic saves), device communication layer stubbed against a mock so later milestones can drop in a real device without rework, and the full distribution pipeline: code signing, macOS notarization, auto-update via electron-updater. Deliverable includes a handoff document covering all architectural decisions and assumptions the next milestone depends on. Milestone 2 — Content Library and Import Full CRUD for the two primary content types and their parent/child relationship. All list, organize, edit, and delete interactions per the prototypes. File import pipeline: accept multiple input formats, convert automatically to the required output format on import, and manage copies within the workspace. Milestone 3 — Configuration and Settings Per-item configuration screens and global application settings, organized across multiple tabs. Built on the stable content library from M2. First-run onboarding flow. Milestone 4 — Device Connectivity and Sync Real device integration using the communication layer stubbed in M1. Auto-detect on connection, device status display, sync protocol (diff calculation, staged file transfer, atomic commit, error handling), and firmware update flow. This milestone can be scoped separately or handled by a specialist — candidates without device connectivity experience should note that in their proposal rather than skipping the application. What we're looking for • Shipped at least one Electron app to end users on macOS or Windows • Handled code signing and notarization personally, not handed it off • Comfortable working from existing HTML/CSS/JS prototypes as the UI reference • Strong understanding of Electron's main/renderer process model and IPC • Experience with safe file I/O — atomic writes, crash recovery, data integrity The kind of developer this suits: • You care about how an app feels, not just whether it works • You write code you'd be comfortable handing to someone else • You flag problems early rather than working around them silently • You've built something you're genuinely proud of