The installer is too big to download
The base Electron runtime is already around seventy megabytes, and shipping unused locales, source maps and node_modules on top can easily double it.
Installer trimmed by half or more
Working with Electron?
Most Electron apps that reach us build fine on the original developer's laptop and nowhere else. The signing cert is missing, notarization keeps getting rejected, or the installer is a quarter of a gigabyte. We get the build pipeline working and the download sized sensibly.
What it is
Electron is a framework for building cross-platform desktop apps with web technologies, bundling Chromium, Node.js and the V8 engine into a single installable program. It was originally created at GitHub for the Atom editor in 2013, then open-sourced under the MIT license, and now lives under the OpenJS Foundation.
It is the engine behind Visual Studio Code, Slack, Discord, Figma desktop, Microsoft Teams, 1Password, Obsidian and Notion, which gives a sense of what it can be pushed to. Releases track Chromium's cadence on an eight-week major release line, and electron-builder and electron-forge are the common toolchains for packaging, signing and publishing updates.
The honest version
No technology is all upside. This is where Electron earns its place and where it tends to cause trouble.
Sound familiar?
The Electron problems that bring people to us, and what you have once each one is fixed.
The base Electron runtime is already around seventy megabytes, and shipping unused locales, source maps and node_modules on top can easily double it.
Installer trimmed by half or more
Hardened runtime entitlements, missing signatures on helper binaries, or a stale Apple Developer certificate chain are the usual reasons the staple never completes.
Signed and notarized on every build
A code signing certificate the update framework cannot read, a feed URL that returns the wrong content type, or a version number that does not advance.
Updates install quietly in the background
Renderer out-of-memory, a GPU process that aborts, or an unhandled rejection in the main process that takes the whole window down.
Crashes reported with stack traces
A Content Security Policy that blocks the preload script, a path that works in development but not inside the packaged ASAR archive, or a renderer that throws before anything paints.
Boots cleanly on a fresh machine
Renderer with full Node access, no contextBridge, remote content loaded without a content security policy, and no isolation between the web layer and the system.
Preload script with a locked-down API
A direct-download build that assumes capabilities the sandboxed build is not entitled to, or a provisioning profile that does not match the signing identity.
Two build targets, one codebase
A release script that only runs on one person's laptop, certificates that are not in version control, and a CI pipeline that has not run in months.
Reproducible builds, documented
What we do
Call us for one failed release, or hand us the whole desktop app.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes, this is one of the most common ways Electron projects reach us. We get the project building on a fresh machine, move signing certificates into our control, document the release steps, and put the CI pipeline back together so the next release does not depend on one person's laptop.
The short version is a hosted update feed, signed and notarized binaries on both platforms, and electron-updater configured against matching channel names. The long version is where the problems live, and we have shipped it enough times to know where each one hides.
Every window is a browser process with its own renderer, so some overhead is unavoidable. The parts that are not unavoidable are renderers that keep large objects alive, extra hidden windows nobody remembers opening, and development tools shipped into production. All of those can be measured and cut back.
Usually we can cut the installer down by a significant amount. Shipped locales nobody uses, source maps left in release builds, duplicated node_modules and uncompressed assets are the common culprits. We measure before and after so the saving is visible.
You need an Apple Developer ID certificate installed in the build environment, the hardened runtime with the right entitlements, and a notary workflow that staples the ticket to the app after Apple approves it. We set this up end to end and wire it into continuous integration.
Estimates are always free of charge. Describe the app and what is going wrong and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: