30 ms·

Are you sure? I have Chrome on my iPad.

sansnomme 7y ago
They run Safari/Webkit underneath. The core engine is not Chrome code. What you use is the value-added trinkets like bookmark sync, different UI design. The important bits are still controlled and locked down.
- IggleSniggle 7y ago
  If Safari for iOS could just add "Find in Page" like exists in Chrome for iOS, I would switch today. Chrome shows it's possible. Why can't my mobile browser have Find in Page? It's far more valuable in mobile, because you can see so much less of the screen.
  - briandear 7y ago
    It does. Type into the address bar, scroll to the bottom of results.
  - donarb 7y ago
    It does offer Find in Page, you tap the address bar to bring up the keyboard, type the word you’re searching for, then scroll down to the bottom of the search results to see if the word was found. Tapping that line gives you a way to navigate through all found results.
    - IggleSniggle 7y ago
      Well hot damn, it sure does. Thank you.
  - deleted 7y ago
    [deleted]
deleted 7y ago
[deleted]
jamesgeck0 7y ago
You have an app wrapping an iOS web view widget with some customized networking code. Apple's App Store policies prohibit Google from shipping a full browser engine.
- st3fan 7y ago
  No you can’t actually customize the networking anymore. On iOS Apple controls the whole web stack. Content, networking, JavaScript.
  - saagarjha 7y ago
    You are free to use the POSIX networking APIs in lieu of CFNetwork (or Network).
    - st3fan 7y ago
      Yes of course. But you cannot replace the networking that WKWebView uses.
hn_throwaway_99 7y ago
Any other non-Safari browsers on iOS/iPad are forced to use the same underlying WebView rendering technology for actual display of web pages. So Chrome on iOS is really just a wrapper around a WebView that adds things like Google login integration.
- dwaite 7y ago
  They are forced to use JavaScriptCore, in the sense that you can't execute JIT-compiled code except for within that one blessed, sandboxed framework. I don't believe they have ever been limited in porting, but have decided the performance hit for using their own javascript engines (or compatibility issues in leveraging Apple's) aren't worth the effort.
  - jakub_g 7y ago
    Even more, the WebView on iOS is not Safari. It's dumbed-down Safari that does not support certain features that Safari supports (service workers and all PWA-related stuff). So it's not equal competition at all.
    - chrisseaton 7y ago
      I'm pretty sure it's exactly the same code base just with some minor feature flags.
      - NicoJuicy 7y ago
        Not that minor, there are indeed 2 different engines. One for Safari and one for the rest.
        saagarjha 7y ago
        Right, but that comes out of the exact same code with some minor feature flags.
        zapzupnz 7y ago
PretzelFisch 7y ago
That is a chrome skin over safari
deleted 7y ago
[deleted]

They run Safari/Webkit underneath. The core engine is not Chrome code. What you use is the value-added trinkets like bookmark sync, different UI design. The important bits are still controlled and locked down.

IggleSniggle 7y ago
If Safari for iOS could just add "Find in Page" like exists in Chrome for iOS, I would switch today. Chrome shows it's possible. Why can't my mobile browser have Find in Page? It's far more valuable in mobile, because you can see so much less of the screen.
- briandear 7y ago
  It does. Type into the address bar, scroll to the bottom of results.
- donarb 7y ago
  It does offer Find in Page, you tap the address bar to bring up the keyboard, type the word you’re searching for, then scroll down to the bottom of the search results to see if the word was found. Tapping that line gives you a way to navigate through all found results.
  - IggleSniggle 7y ago
    Well hot damn, it sure does. Thank you.
- deleted 7y ago
  [deleted]

deleted 7y ago

[deleted]

jamesgeck0 7y ago

You have an app wrapping an iOS web view widget with some customized networking code. Apple's App Store policies prohibit Google from shipping a full browser engine.

st3fan 7y ago
No you can’t actually customize the networking anymore. On iOS Apple controls the whole web stack. Content, networking, JavaScript.
- saagarjha 7y ago
  You are free to use the POSIX networking APIs in lieu of CFNetwork (or Network).
  - st3fan 7y ago
    Yes of course. But you cannot replace the networking that WKWebView uses.

hn_throwaway_99 7y ago

Any other non-Safari browsers on iOS/iPad are forced to use the same underlying WebView rendering technology for actual display of web pages. So Chrome on iOS is really just a wrapper around a WebView that adds things like Google login integration.

dwaite 7y ago
They are forced to use JavaScriptCore, in the sense that you can't execute JIT-compiled code except for within that one blessed, sandboxed framework. I don't believe they have ever been limited in porting, but have decided the performance hit for using their own javascript engines (or compatibility issues in leveraging Apple's) aren't worth the effort.
- jakub_g 7y ago
  Even more, the WebView on iOS is not Safari. It's dumbed-down Safari that does not support certain features that Safari supports (service workers and all PWA-related stuff). So it's not equal competition at all.
  - chrisseaton 7y ago
    I'm pretty sure it's exactly the same code base just with some minor feature flags.
    - NicoJuicy 7y ago
      Not that minor, there are indeed 2 different engines. One for Safari and one for the rest.
      - saagarjha 7y ago
        Right, but that comes out of the exact same code with some minor feature flags.
      - zapzupnz 7y ago

PretzelFisch 7y ago

That is a chrome skin over safari

deleted 7y ago

[deleted]