IdeaWell

Project ideas from Hacker News discussions.

Apple's new 'Switch to Safari' campaign details why you should ditch Chrome

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Three prevalent themes in the discussion

1. iOS forces all browsers to use Safari/WebKit, limiting real choice

Many commenters point out that Apple’s policy prevents alternative rendering engines on iOS, making every browser essentially a “Safari Lite” wrapper.

  • JohnTHaller: “iOS does not allow third party browser engines. Every browser you download from the iOS App Store is using 'Safari Lite' under the hood.”
  • TheDong: “First let us install other browser engines on iOS, and then we can talk.”
  • j45: “On iPhone, for the longest time, every browser has been forced to be Safari's engine underneath. Firefox, Chrome, etc are all forced to run Safari underneath.”

2. Safari is praised for speed and low power use, but criticized for quirks, limited extensions, and UX shortcomings

Users acknowledge Safari’s performance advantages over Chrome yet complain about missing power‑user features, odd tab behavior, and extension limitations.

  • pipolo: “Safari's performance (both speed and power use) keep me on it vs. Chrome, but I do wish we could have some of the more power-user-friendly features.”
  • bensyverson: “Safari is faster, uses less RAM and is more power-efficient.”
  • InfiniteQwert: “give me Split Tabs outside of Fullscreen you cowards.”
  • nitin7: “Yeah. I'm typing this on my safari which shows both vertical tabs and the horizontal tabs - looks so weird. And I always end up clicking a tab and then typing away, and Safari starts switching me to tabs starting with whatever letter I type - very annoying.”

3. Calls for Safari to be open‑source, cross‑platform, or for Apple to open its ecosystem

Several participants say they would consider Safari only if it were available on other platforms or released as open source; otherwise they view it as another walled‑garden tool.

  • drnick1: “I would consider Safari, if Apple open sourced it and it ran on Linux.”
  • glimshe: “If Safari worked in all major OSs like Chrome, Brave and Firefox, I could consider that.”
  • ur‑whale: “Safari is not the solution until they make it fully (FULLY) open‑source, because all Apple trying to do is replace the king of enshitification hill by their own.”

🚀 Project Ideas

Generating project ideas…

SafariLabs – Cross‑platform Safari‑like Browser

Summary

  • Provides a Safari‑compatible browsing experience on Windows and Linux using WebKitGTK/WPE, letting developers test Safari‑specific quirks without Apple hardware.
  • Delivers power‑user UI enhancements (vertical tabs, split‑tab groups, built‑in content blocker) while preserving WebKit’s speed and efficiency.

Details

Key Value
Target Audience Web developers, QA engineers, and power users who need Safari‑like browsing on non‑Apple OS
Core Feature WebKitGTK/WPE based browser with Safari‑style UI, vertical tabs, split‑tab groups, and a configurable content blocker
Tech Stack WebKitGTK (or WPE/WebKit), GTK4, Rust (or C++), optional SQLite for history
Difficulty Medium
Monetization Hobby

Notes

  • HN users lament: “Safari is the browser with the largest number of rendering bugs … I have to pay money, to buy their hardware to see if my site will work on Safari.” and “If Safari worked in all major OSs like Chrome, Brave and Firefox, I could consider that.”
  • Enables cross‑platform testing, reduces reliance on costly Mac hardware, and encourages broader WebKit contributions from the open‑source community.

PWA Persist – iOS Helper App to Extend PWA Data Lifetime

Summary

  • Allows iOS PWAs to retain local storage beyond the 7‑day limit by using background fetch to periodically refresh the hidden WebKit view.
  • Gives users a reliable, app‑like experience for home‑screen web apps without losing state or needing frequent re‑login.

Details

Key Value
Target Audience iOS users who depend on PWAs for productivity, news, or offline tools (e.g., Twitter Lite, Spotify Web)
Core Feature Background‑fetch wrapper that silently re‑opens the PWA in a WKWebView to reset the 7‑day timer and sync data to iCloud/Keychain
Tech Stack Swift, BackgroundFetch API, WKWebView, iCloud Key‑Value store
Difficulty Medium
Monetization Hobby

Notes

  • Commenters urged: “First stop blocking iOS pwas from simply installing to the home screen, and don't clear out data in 7 days. Then we'll talk about your browser being better.”
  • Solves a concrete friction point for PWA adoption on iOS, sparking discussion about Apple’s background‑execution limits and potential policy changes.

TabZen – Safari Extension for Vertical Tabs, Split View & Enhanced Ad‑Blocking

Summary

  • Adds a vertical tab sidebar, split‑screen tab groups, and a rule‑based content blocker that works around Safari’s Manifest V3 limitations.
  • Brings Chrome‑level tab management and ad‑blocking power to Safari while keeping its battery‑friendly performance.

Details

Key Value
Target Audience macOS/iOS power users frustrated with Safari’s tab handling and weak ad‑blocker support
Core Feature Sidebar with draggable vertical tabs, split‑view tab groups, and a content blocker that converts uBlock‑style lists to Safari Content Blocker rules
Tech Stack Safari WebExtension (HTML/CSS/JS) + native helper app (Swift) for rule conversion
Difficulty Medium
Monetization Hobby

Notes

  • Users asked: “I would... if it had vertical tabs” and “give me Split Tabs outside of Fullscreen you cowards.” Ad‑blocking frustrations were also highlighted: “Safari web extensions never supported blocking webRequest.”
  • Directly addresses the top UI and ad‑blocking pain points, likely to generate enthusiastic discussion and adoption among Safari‑loyalists seeking Chrome‑like features.

Read Later