Re:AR.js: Efficient Augmented Reality for the Web
by mkeblx on Wednesday September 20, 2017 @06:41PM
(#15299007)
Yes, they could have done the same thing with an Android WebView. But the Chrome team is actively working on implementing WebVR (which also want to support many AR use cases) so they already have a native (= higher performance, lower latency, etc) implementation to modify with some smaller changes to use the ARCore API.
But the WebARonARCore repo is a whole freaking clone of the entire Chrome browser!
Isn't there a much simpler way to extend an off-the-shelf Chrome component like they did with WKWebView on iOS, without rebuilding the entire honking browser?
I know there is a WebView chrome component for Android -- why didn't they simply use that, the same way as they did with WKWebView on iOS? Performance? Does it require features the WebView Chrome component doesn't support?