Skip to content

Why I Love Electron

Electron gives me one thing:
presence.

  • App icon in the tray
  • Background daemon controller
  • Hook for system notifications
  • Simple launcher for PWA if needed

I Don’t Use Electron for UI

Most of my interfaces are PWA-based.
They’re portable, responsive, and work across all devices.

But Electron fills the gap:

Native presence without the bloat.

What I Do Use It For

  • DDP-based controller wrappers
  • System tray menu to toggle behavior
  • Auto-launch with OS boot
  • Notifications tied to daemon events
  • Packaging extensions + daemons + Meteor UI together

Just one icon — and I’m connected.

Meteor + Electron = 💡

Because my p2p logic lives in Meteor (with DDP),
Electron becomes just a bridge to the native system.

// In Electron main.js
const { app, Tray, Menu } = require('electron');
const DDPClient = require("ddp");

let ddp = new DDPClient({ host: 'localhost', port: 3000 });

ddp.connect(() => {
  tray.setContextMenu(Menu.buildFromTemplate([
    { label: "Next Song", click: () => ddp.call('media.skip') },
    { label: "Pause", click: () => ddp.call('media.pause') }
  ]));
});

No clutter, no heavy UI, just control.

Sovereign, Local, Lightweight

I can build a daemon, package it with Electron, and give it a name + icon.

No cloud dependencies. No complicated UX. Just fast local utility — exactly what I need.

Final Thought

Electron isn’t about writing “native” apps. It’s about giving my daemons a voice.

An icon. A controller. A signal.

That’s all I need.