Jump to content

VR --> A-Frame vs BablyonJS


Recommended Posts

I am currently trying to develop some vr apps for Google Cardboard, Rift etc...

I guess at the end of the day it is clear that BabylonJS looks more developed than A-Frame, but A-Frame is built by Mozilla, which means:

1). It will likely stay around for some time (though it is built on top of ThreeJS, not sure what happens when that stops being developed).
2). Will stay open and remain with an open license
3). Will follow new specs as they are released, and contribute to them
4). Possibly better experience for VR since that is there focus

I do like that BabylonJS seems more powerful though. Any thoughts, pros-cons?


Link to comment
Share on other sites

  • 1 month later...

A-Frame and BabylonJS are build for 2 seperate goals.

A-Frame: Build a scene

BabylonJS: Build a game (and you can ofcourse also build a scene)

I looked at A-Frame a while back, but for example, there is no build in way available at this moment for getting custom input from the mouse/keyboard. You have the default keyboard behaviour, and that's about it. Also no physics for A-Frame.

Also A-Frame is building your scene in HTML (with proper classes defined.) BabylonJS is.. JS.




Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...