IdeaWell

Project ideas from Hacker News discussions.

An Update on Orion for Linux and Windows

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Three prevalent themes in the HN discussion

  1. Resource allocation – Kagi should focus on search, not a browser
    Many commenters feel the company is spreading itself too thin and would rather see effort put into improving Kagi search.
  2. “So as a non‑Apple‑using Kagi subscriber since Beta, I kind of wish they'd just concentrate on search - the thing I'm paying for.” – petepete
  3. “I feel the same way… if I could choose I’d rather the company focus on Kagi development.” – frenchtoast8

  4. “They expanded into too many domains and spread themselves too thin and that doesn't give me confidence.” – ClaraForm

  5. Mixed views on Orion’s value and niche
    Opinions diverge on whether Orion fills a useful role (performance, extensions, Apple‑ecosystem sync) or whether its purpose is unclear, especially on Linux/Windows.

  6. “Anecdotally, the niche it solved for me… was 'Safari for optimal performance on mac, but with proper extensions like ublock'.” – TheCapeGreek
  7. “I've never understood what niche Orion is supposed to fill… on Linux, a proprietary browser is a major deal‑breaker for most people.” – RandomGerm4n

  8. “For me, as battery‑efficient as Safari, but with better chrome and access to ffox extensions ecosystem.” – shakow

  9. Concerns about the open‑source strategy (Linux/Windows ports vs. closed macOS)
    Users worry that releasing only the Linux and Windows code while keeping macOS proprietary will lead to drift, poor stewardship, and little community uptake.

  10. “Sad that the other two platforms won't have the same stewardship as Orion on macOS. Especially since we're likely to see drift from the core WebKit implementation between them now.” – qmarchi
  11. “I don't understand the decision to open source the Linux and Windows ports, but not the MacOS version… Then someone else could have picked up the task of keeping the Linux and Windows forks in sync with their MacOS work.” – arppacket
  12. “Agreed, the open source Linux and Windows versions feel pretty much DOA without the ability to reference and port the macOS source code.” – 4lun
  13. “It's ironic (and sad) that they'd both abandon it and open source it at the same time… abandoning it kinda kills motivation for anyone to contribute.” – WhyNotHugo

🚀 Project Ideas

Orion‑X: Unified WebKit Browser with Cross‑Platform UI

Summary

  • A single‑source WebKit browser that shares the Orion macOS codebase while delivering native‑looking UI on Linux and Windows via a thin abstraction layer.
  • Solves the “DOA” feeling of the Linux/Windows ports by keeping them in lock‑step with macOS updates and enabling community contributions.

Details

Key Value
Target Audience Power users who want a privacy‑focused, non‑Chromium browser with Chrome‑extension‑like capabilities across macOS, Linux, and Windows
Core Feature Shared WebKit rendering engine + platform‑specific UI kit (Swift/SwiftUI for macOS, GTK/Qt for Linux, WinUI for Windows) driven from a common core
Tech Stack C++/Objective‑Core (WebKit), SwiftUI (macOS), GTK 4 (Linux), WinUI 3 (Windows), CMake build system, GitHub Actions CI
Difficulty Medium
Monetization Hobby

Notes

  • “I don't understand the decision to open source the Linux and Windows ports, but not the MacOS version… they should have moved their Orion development into the open.” – arppacket
  • Provides a clear upstream for Linux/Windows contributors, reducing fragmentation and giving macOS users confidence that the project isn’t being abandoned.

WebKit‑Chrome Extension Bridge

Summary

  • A compatibility layer that unpacks Chrome extensions and runs their content scripts, background pages, and APIs inside any WebKit‑based browser (Safari, Orion, etc.).
  • Addresses the frequent request for Chrome‑extension support on Orion and other WebKit browsers without requiring a Chromium fork.

Details

Key Value
Target Audience Users of Safari, Orion, or other WebKit browsers who need specific Chrome extensions (e.g., uBlock Origin, privacy tools)
Core Feature Translates Chrome extension manifests to WebKit‑compatible scripts, provides a shim for chrome.* APIs using WebKit’s extension infrastructure
Tech Stack Rust (core bridge), JavaScript/TypeScript (shim), WebKit extension APIs, distributed as a native macOS/Linux/Windows bundle
Difficulty High
Monetization Hobby

Notes

  • “I’ve never understood what niche Orion is supposed to fill… People who value privacy would be more likely to use an open-source browser. Firefox and Brave already serve that purpose. Maybe it's less important to Mac users, but on Linux, a proprietary browser is a major deal-breaker.” – RandomGerm4n
  • Enables privacy‑conscious users to keep their preferred WebKit browser while still accessing the Chrome extension ecosystem they rely on.

Kagi Search Assistant Browser Plugin

Summary

  • A lightweight browser extension that sets Kagi as the default search engine, integrates the Kagi AI assistant directly into the address bar/context menu, and provides instant answer cards.
  • Gives the Orion‑style Kagi experience to users of Firefox, Brave, Safari, or any other browser, letting them keep their preferred UI while benefiting from Kagi’s search quality.

Details

Key Value
Target Audience Kagi subscribers (and potential subscribers) who like the assistant but don’t want to switch browsers
Core Feature Omnibox integration: Kagi search suggestions, AI‑assisted answers, one‑click access to Kagi Assistant, optional ad‑blocking toggle
Tech Stack WebExtension manifest (Chrome/Firefox/Safari), TypeScript, React for UI, communicates with Kagi APIs over HTTPS
Difficulty Low
Monetization Revenue-ready: Freemium (free for verified Kagi subscribers, $2/mo for non‑subscribers)

Notes

  • “I like Orion, and I use it on some of my devices. But if I could choose I’d rather the company focus on Kagi development.” – frenchtoast8
  • Provides a low‑friction way to get the Kagi assistant without abandoning a favorite browser, addressing the desire for Kagi‑centric features while retaining browser choice.

Read Later