Search Unity

  1. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  2. Improved Prefab workflow (includes Nested Prefabs!), 2D isometric Tilemap and more! Get the 2018.3 Beta now.
    Dismiss Notice
  3. Want more efficiency in your development work? Sign up to receive weekly tech and creative know-how from Unity experts.
    Dismiss Notice
  4. Participate with students all over the world and build projects to teach people. Join now!
    Dismiss Notice
  5. Build games and experiences that can load instantly and without install. Explore the Project Tiny Preview today!
    Dismiss Notice
  6. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice
  7. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice

Web based AR.js vs native -pros and cons

Discussion in 'AR/VR (XR) Discussion' started by eco_bach, Dec 6, 2018 at 5:25 PM.

  1. eco_bach

    eco_bach

    Joined:
    Jul 8, 2013
    Posts:
    1,018
    Trying to get a better understanding of some of the limitations of web based AR over native solutions.

    Does it depend on the complexity of the 3d content you are trying to bring to life?

    Has anyone reading this developed in both and can comment?
     
  2. Mal_Duffin

    Mal_Duffin

    Joined:
    Jan 22, 2015
    Posts:
    33
    Native can use the newer mobile ARCore / ARKit tech, WebAR is currently marker based as the default browsers can't access this information ( there are custom builds if you google ). You can use a third party like http://6thwall.com/ to add AR feature tracking to your content ( check out https://www.intothespiderverse-ar.com/ for an example, and to get an idea of what browsers support AR on various mobile devices )
     
  3. eco_bach

    eco_bach

    Joined:
    Jul 8, 2013
    Posts:
    1,018