Note: This documentation is for the old 0.5.0 version of A-Frame. Check out the documentation for the current 1.4.0 version
Some best practices for the framework:
- The core structure of A-Frame is entity-component (ECS). Place and
structure application code within purely A-Frame components for reusability,
modularity, composability, decoupling, encapsulation, declarativeness, and
testability. It’s okay to start out at first using content scripts
<script>), but look to move towards components.
- Mixins and templating are useful to reuse and reduce repeated HTML.
Performance is critical in VR. A high framerate must be maintained in order for people to feel comfortable and as if they were in another place. Here are some ways to help improve performance of an A-Frame scene:
- Use recommended hardware specifications.
- Use the stats component to keep an eye on various metrics (FPS, vertex and face count, geometry and material count, draw calls, number of entities). We want to maximize FPS and minimize everything else.
- Make use of the asset management system to benefit from browser caching and preloading. Trying to fetch assets while rendering is slower than fetching all assets before rendering.
- If using models, look to bake your lights into textures rather than relying on real-time lighting and shadows.
- Generally, the fewer number of entities and lights in the scene, the better.
- Make sure your textures’ resolutions are sized to powers of two (e.g., 256x256, 512x1024) in order to avoid the renderer having to resize the texture during runtime.
- Limit the number of faces and vertices on models.
- Some further techniques (not yet documented) include geometry instancing, geometry merging, level of detail (LOD).
- When using raycasters or colliders, select which entities are to be raycasted against rather than raycasting against every object in the scene.
- When adding continuously running behaviors, use A-Frame component
tickhandlers to hook into the global render loop. Use utilities such as
AFRAME.utils.throttleTickto limit the number of times the
tickhandler is run if appropriate.
In component tick handlers, be frugal on creating new objects. Try to reuse objects. A pattern to create private reusable auxiliary variables is with a closure. Below we create a helper vector and quaternion and reuse them between frames, rather than creating new ones on each frame. Be careful that these variables do not hold state because they will be shared between all instances of the component. Doing this will reduce memory usage and garbage collection:
Also if we continuously modify a component in the tick, make sure we pass the same object for updating properties. A-Frame will keep track of the latest passed object and disable type checking on subsequent calls for an extra speed boost. Here is an example of a recommended tick function that modifies the rotation on every tick:
Designing for VR is different than designing for flat experiences. As a new medium, there are new sets of best practices to follow, especially to maintain user comfort and presence. This has been thoroughly written about so we defer to these guides. Note that VR interaction design is fairly new, and nothing is absolute:
Some things to note:
- The common golden rule is to never unexpectedly take control of the camera away from users.
- Units (such as for position) should be considered meters. This is because the WebVR API returns pose in meters which is fed into most camera controls. By considering units as meters, we achieve expected scale.