r/electronjs

I’ve been building Summer Browser for the past two years
▲ 2 r/electronjs+1 crossposts

I’ve been building Summer Browser for the past two years

I’ve spent the last two years building Summer Browser, with the goal of giving users more control over their browser.

It’s free, collects no browsing data, supports Chrome extensions, and adds Summer Apps — native Node.js apps and widgets that run within the browser.

It also rethinks parts of the normal browser UX, particularly the omnibox, with suggestion cards designed around frequent and repeated navigation.

Current usage: ~4,000 downloads, ~300 MAU and ~25 DAU.

Windows is available now and macOS has been submitted to the App Store.

I’m posting it here because I’m interested in criticism from people who care about browsers: missing features, architectural concerns, UX problems, or things you think I’ve simply gotten wrong.

Feature requests are welcome as well.

https://summerbrowser.com

Windows: https://apps.microsoft.com/detail/9p9jjwnl2z29

macOS: https://apps.apple.com/il/app/summer-browser/id6759205260

u/ImprovementOwn873 — 3 days ago

Engineering an Offline-First Sync Engine for a Retail ERP with Electron, SQLite, and Prisma

Hi everyone, I wanted to share some architecture details from my recent project, Manzoma ERP. Since I'm targeting retail stores with spotty internet, a standard cloud-only SaaS wasn't an option.

The Architecture:
I used Electron as the shell, React 19 for the UI, and Prisma/SQLite for the local data layer.

The Sync Challenge:
The hardest part was handling the transition from offline to online without creating data conflicts in the inventory (3,000+ SKUs). I built a custom background sync worker that uses a version-based reconciliation logic.

It’s currently battle-tested and has processed over $30k in live volume. Happy to answer any questions about the Electron setup or the sync logic!

reddit.com
u/ThisisKebo — 3 days ago
▲ 14 r/electronjs+5 crossposts

I built an open-source Windows app that turns your PC history into visual recaps. PC Recap 1.1 is out

Hey, I’m the developer of PC Recap.

Most computer-usage trackers answer, “How productive was I?” I wanted something that answered, “What did this part of my life on my PC actually look like?”

PC Recap records active application usage and turns it into visual Today, Week, Month, Year, All-Time, Decade, and On This Day recaps.

Version 1.1 is the biggest update so far:

  • Day Replay lets you scrub through a recorded day
  • Recap Studio creates stories for years, seasons, decades, or custom dates
  • Automatic eras detect phases like a gaming era or coding era
  • Memory Pins let you attach your own context to a period
  • Historical Recovery can find limited pre-installation clues without pretending they are exact usage time
  • ActivityWatch and ManicTime sessions can be imported
  • Search, comparisons, time formatting, chart tooltips, and app detection are much clearer
  • Tracking is more resilient to crashes, restarts, pauses, and closing the window

PC Recap is now open source under GPL v3. Everything is stored locally in SQLite. There is no account, desktop telemetry, cloud activity storage, or external AI API. A new archive starts empty, with no fake statistics.

ActivityWatch is still the stronger choice if you need Linux/macOS support, browser extensions, editor plugins, or an extensible tracking ecosystem. PC Recap is aimed at a different experience: less productivity dashboard, more personal digital time capsule. It can also import ActivityWatch sessions if you want to use both.

PC Recap is currently a Windows 10/11 x64 beta. The installer is unsigned, so Windows may display a SmartScreen warning.

Website: https://pcrecap.online
Source: https://github.com/TheAgencyMGE/pc-recap
Version 1.1: https://github.com/TheAgencyMGE/pc-recap/releases/tag/v1.1.0

I’d especially appreciate feedback on tracking accuracy, the new Day Replay, and whether the recaps become interesting after a few days of real use.

u/Admirable-Put7423 — 4 days ago

Desktop wrapper for DeepSeek Harness: why I chose Electron (practical choice)

Electron may be heavier, but this project is not just “a WebView wrapper.”

It’s a lightweight desktop shell that bundles Node.js runtime, manages DSH versions, and handles local process lifecycle, while keeping the official DeepSeek Harness experience intact (no changes to DSH itself).

I’m shipping it as an open-source app here:
https://github.com/qufei1993/dsh-desktop

I also learned a lot while building skills-hub, including practical macOS issues users may hit with unsigned builds and system security settings (sometimes requiring steps like xattr -cr in some contexts).
Given the current scope, Electron feels like the more straightforward and maintainable path.

I did consider Tauri, but since DSH is still Node-dependent, we would still need a Node sidecar, which increases complexity for version and process management.

So for now I’m choosing pragmatism: make it easy to run, easy to upgrade/switch versions, and consistent across macOS + Windows.

https://preview.redd.it/3qfzhhfqgmjh1.png?width=2642&format=png&auto=webp&s=e4d0ae73604457ca883aa0a22af94c80b7e229a6

https://preview.redd.it/9oj4glargmjh1.png?width=2596&format=png&auto=webp&s=0a0c5486147768238ac492b2a9294d978605170d

reddit.com
u/Due-Revolution-124 — 5 days ago
▲ 43 r/electronjs+1 crossposts

Built MeshDrop: An open-source, zero-cloud P2P file sharing desktop app (Electron + React + Hyperswarm)

Hey r/electronjs community! 👋

I wanted to share a desktop app I’ve been building called **MeshDrop a zero-cloud, peer-to-peer file-sharing application designed for direct, end-to-end encrypted file transfers without central servers or user accounts.

💻 Tech Stack & Architecture

Since this is an Electron subreddit, here is a breakdown of how the project is structured:

P2P Core (`@mesh/core`): A standalone, platform-agnostic P2P engine written in pure Node.js running directly inside the Electron **Main Process**. It handles Hyperswarm discovery, `@hyperswarm/secret-stream` E2E encryption, `corestore` replication, and HMAC-SHA256 challenge UI / Renderer:** React 19 + Vite + Tailwind CSS + Lucide icons.

IPC Bridge: Safe contextBridge IPC pattern (`window.bridge`) forwarding engine events (pairing states, transfer progress, peer diagnostics) from Main to Renderer.

Packaging & Auto-Updates:** Configured with `electron-builder` (NSIS assisted installer + standalone portable single-file `.exe`) and integrated with `electron-updater` for differential updates.

CI/CD:Multi-platform matrix build pipeline on GitHub Actions (`windows-latest`, `macos-latest`, `ubuntu-latest`).

⚡ Main Features

  1. One-Time DROP Codes:** Quick 6-digit challenge code pairing for fast, ad-hoc file transfers between untrusted or guest devices.

  2. Trusted Peer Pairing:** Persistent zero-trust authorization to pair your own devices securely.

  3. Portable & Installer Builds: Option for single-file portable `.exe` (runs without installation) or per-user NSIS installer.

  4. Zero Cloud / Zero Account: No registration, no tracking, no central storage

📦 Links & Testers Needed

I just published **v1.0.0-beta.1** and would love to get feedback on the Electron architecture, IPC design, and P2P performance across different networks!

* 📦 **Release Downloads (Win/Mac/Linux):** https://github.com/aamirali51/MeshDesk/releases/tag/v1.0.0-beta.1

* 💻 **GitHub Repository:** https://github.com/aamirali51/MeshDesk

Any feedback, code reviews, or bug reports are greatly appreciated! Let me know what you think! 🙌

u/aamirali51 — 9 days ago

How was VS Code built with Electron without React/Vue/etc.? How is it so dynamic?

VS Code is an Electron app, but from what I understand, its UI isn't built with React, Vue, Angular, etc. It seems to use HTML/CSS/JavaScript/TypeScript more directly.

So how does VS Code create such a large, highly dynamic UI without a frontend framework?

reddit.com
u/NoTutor4458 — 10 days ago
▲ 23 r/electronjs+7 crossposts

[Beta] Swaya: A local desktop media organizer built for heavy data hoarders & collectors

Let’s be real - if you hoard terabytes of movies, TV shows, anime, documentaries, music videos, or other local media, organizing everything eventually turns into a mess of inconsistent filenames, duplicate files, missing metadata, and chaotic folder structures.

I wanted a fast, native desktop application that keeps large offline media libraries organized while remaining fully local and responsive.

Over the last year, I built Swaya, a Windows/Linux media suite (Electron/React 19 + Python FastAPI/SQLite) designed specifically for collectors with massive libraries.

Powerful Metadata Matching: Automatically identifies movies, TV shows, and other media from messy release filenames using GuessIt, then fetches posters, artwork, cast, genres, ratings, and metadata from TMDb and OMDb.

Collection Insights: Track watch history, completion progress, metadata coverage, timestamps, library statistics, and discover what you watch most.

Privacy Mode: A single click instantly hides posters, thumbnails, and sensitive folders behind blurred placeholders, making it easy to browse your library in shared environments.

Integrated Playback: Built-in MPV player wrapper with support for VLC and MPC-HC, including real-time playback progress synchronization.

Built for Large Libraries: Designed to handle huge collections with thousands of files while keeping browsing smooth and responsive.

I'm opening a closed beta and looking for 20-30 people with large, messy media collections to throw their worst folder structures at Swaya, stress-test the metadata matching, and help uncover edge cases, performance issues, and UI freezes.

If you're interested in helping test it, leave a comment or send me a DM and I'll send you a beta invite.

Transparency, AI & Privacy:

Development: AI assistants were used for testing, debugging, and boilerplate refactoring. The application's architecture, features, and business logic were designed and implemented by me.

Privacy: Swaya has zero telemetry, zero analytics, and zero call-home servers. Everything stays on your machine, and API requests are made directly from your computer using your own API keys.

Verification: If you're cautious, feel free to monitor the application with Wireshark or GlassWire, or request read-only GitHub access to inspect the code.

Additional metadata providers: Swaya also supports StashDB, FansDB, and ThePornDB for users who maintain compatible libraries.

u/abszolut — 12 days ago