Show HN: A modern Jupyter client for macOS

Original Article ↗ Hacker News Discussion ↗

App goals & design

  • A macOS-focused Jupyter client aimed at being fast, minimalist, and “Sonoma-native” in look-and-feel.
  • Built on top of jupyter-server, using existing Python kernels, config, and .ipynb files; currently local-only with plans for remote servers.
  • Includes OpenAI-based multi-cell generation (user’s API key), Black formatting, virtualenv UI, and easy image/table export.

Electron vs native / platform scope

  • Original Swift implementation was abandoned due to lack of mature native code-editor components; Electron allowed a feature-complete editor quickly.
  • Some welcome Electron as a pragmatic choice and value features over tech purity; others strongly dislike Electron for bloat and app size, pushing for Tauri, native WebKit, or fully native Swift.
  • Several question why an Electron app is macOS-only and request Windows/Linux support.

Features, gaps, and requests

  • Praised for aesthetics, quick startup, and focused-notebook experience.
  • Critiques: few clear advantages over VS Code/JupyterLab for power users; missing GitHub Copilot, robust LSP-level completion, remote connections, widget/Plotly support, and custom keybindings.
  • Requested features include:
    • Remote Jupyter servers and kernels.
    • Better environment/kernel detection (matching VS Code’s automatic venv discovery).
    • Safer behavior around auto-installing ipykernel (prompting, respecting poetry/pipenv/nix).
    • Drag-and-drop data files that auto-generate load/preview code.
    • RStudio-like / Quarto-style literate workflow, CSV/table conveniences, and notebook “calculator” usage.

Usability, workflows, and audience

  • Target users seen as scientists/analysts who find IDEs heavy or confusing and want a simple desktop notebook.
  • Others prefer existing setups: VS Code notebooks, JupyterLab Desktop, QtConsole, vim/emacs integrations, or RStudio/Quarto.
  • Some value mental separation: a lightweight, single-purpose notebook app instead of a full IDE.

Privacy, licensing, and business model

  • Lack of visible privacy/telemetry policy and unclear business model are blockers for professional use.
  • Multiple commenters encourage an open-source codebase with paid binaries or similar indie-friendly monetization.

Broader Jupyter commentary

  • Discussion branches into Jupyter’s strengths (interactive exploration, shareable analyses) and weaknesses (statefulness, out-of-order execution, reproducibility), with some advocating alternatives like Quarto.