Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AR] Different behaviour on smartphone web browser and compiled app #102

Open
AlbaneseRemy opened this issue Jan 18, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@AlbaneseRemy
Copy link

AlbaneseRemy commented Jan 18, 2024

I don't know if I can call that a bug, but the behaviour is kind of messed up.

I have an app that basically works on three different platforms (ios, android and web browser)
In the app, I have a model viewer widget, in which I display a gltf file.

When using it on a mobile web browser (to check on a smartphone, you can compile your app on localhost on your computer, and create a bridge with inspect tool from chrome to connect to it through your smartphone web browser), the AR mode works perfectly fine.

But when I compile the app directly on my smartphone, the AR mode opens the google AR app which is laggy, and less permissive than the browser one (can't zoom in as much as in browser, longer to detect a plane surface...)

Is there a way to open for example a webview, or to redirect to a web page rather than the google app?

  • Device: Samsung Galaxy S20 & Samsung Galaxy A50
  • OS: Android 13 or S20, Android 11 for A50
  • Browser Chrome
@AlbaneseRemy AlbaneseRemy added the bug Something isn't working label Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant