4 ms·

Kagi Browser | Palo Alto, CA | Full-time, part-time | Remote We are building a new web browser for macOS/iOS. It is based on the fork of WebKit with support fo

Kagi Browser | Palo Alto, CA | Full-time, part-time | Remote We are building a new web browser for macOS/iOS. It is based on the fork of WebKit with support for WebExtensions API. That means you can run any Firefox/Chrome extension while using the full advantages of WebKit rendering engine on macOS (fastests/best energy use). Kagi is the first browser that lets you install WebExtensions on iOS! https://imgur.com/a/OPdkpoL https://imgur.com/a/OPdkpoL (this is live prototype) What we are looking for: macOS and iOS software development engineers Skills we are looking for (5+ years of experience): - Swift - C++ (for macOS only) - Javascript Novel idea, challenging problems. Join us! Email: vprelovac@gmail.com (send CV / relevant experience / availability)

saagarjha 7y ago
Unrelated to the job itself: how are you planning on getting this to comply with the App Store Review Guidelines? Also unrelated: I know it's a UI demo, but you might want to look into adding some vibrancy in your overlays :)
- freediver 7y ago
  The iOS version uses same WebKit any other browser uses, we built WebExtension support on top of it.
  - saagarjha 7y ago
    In addition to the WebKit requirement on iOS, I was curious about guideline 2.5.2, which governs downloading and execution of additional code. (I've worked heavily in this area, so I am really interested in where you're planning on taking this. If you're OK with it we can move this to email so we're not spamming the thread.)
    - freediver 7y ago
      My take on it is that every browsers' behavior by design is to download and execute additional code (JS and HTML). Web extensions are JS and HTML code so there is no change in app behavior. Worst case scenario is we have to turn it off on iOS, but we still get the macOS Webkit browser with webextension support which is still unique. Would love to hear your thoughts, my email is above.

saagarjha 7y ago

Unrelated to the job itself: how are you planning on getting this to comply with the App Store Review Guidelines? Also unrelated: I know it's a UI demo, but you might want to look into adding some vibrancy in your overlays :)

freediver 7y ago
The iOS version uses same WebKit any other browser uses, we built WebExtension support on top of it.
- saagarjha 7y ago
  In addition to the WebKit requirement on iOS, I was curious about guideline 2.5.2, which governs downloading and execution of additional code. (I've worked heavily in this area, so I am really interested in where you're planning on taking this. If you're OK with it we can move this to email so we're not spamming the thread.)
  - freediver 7y ago
    My take on it is that every browsers' behavior by design is to download and execute additional code (JS and HTML). Web extensions are JS and HTML code so there is no change in app behavior. Worst case scenario is we have to turn it off on iOS, but we still get the macOS Webkit browser with webextension support which is still unique. Would love to hear your thoughts, my email is above.