WebView performance significantly slower than PWA(issues.chromium.org)
33 pointsby denysonique10 hours ago5 comments
  • qingcharles4 hours ago
    It's amazing bugs like this persist, even with the significant resources of several megacorps allocating legions of full-time developers to the codebase.
  • londons_explore3 hours ago
    Summary: In certain circumstances webview rendering is slow because it has to integrate with the android rendering API incase an app wishes to synchronize some App UI with web UI.

    This isn't a limitation in chrome itself, which means chrome rendering has better performance for these specific operations (animations mostly).

    Personally I think the chrome rendering path should always be used, and apps which want to draw under/over web content will have to deal with a frame or two of delay.

  • AndrewDucker2 hours ago
    How about they let us opt out of using it at all and just let us use our own browser?
  • joecool10293 hours ago
    To save you having to read a really long comment thread: https://engineering.fb.com/2022/09/30/android/launching-a-ne...

    Basically, FB's engineering replaced it with a full chromium based webview and explained the reasons android webview sucks ass.

    • cosmotic42 minutes ago
      My understanding of the system webview is that applications can share the resource instead of each using their own copy, reducing memory usage and improving multi-tasking. Facebook's solution seems to side step that benefit. I use the fb browser much less frequently than my normal browser, and id rather not use the fb browser at all. I imagine this is true for most users, so the security benefit seems overstated.
  • napolux4 hours ago
    unfortunately nobody cares :(