> For the complete documentation index, see [llms.txt](https://ms-kb.msd.unimelb.edu.au/next-lab/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ms-kb.msd.unimelb.edu.au/next-lab/augmented-reality/resources/platforms-hardware.md).

# Platforms (Hardware)

This article introduces AR Platforms available at the Next Lab.

## Overview

There are two types of platforms that you can use to access the AR technology and develop content: handheld devices such as mobile phones or [Microsoft Hololens](/next-lab/augmented-reality/resources/platforms-hardware/microsoft-hololens.md)  headsets. The Next Lab has several Hololens headsets available for loan through RefTab (students need to undertake a Mixed Reality Induction prior to loaning out this equipment). 

Using software such as [Unity and Unreal](https://app.gitbook.com/@msd-makerspaces/s/next-lab/~/drafts/-M8DVJZFirWdRBR-baN3/augmented-reality/unity-and-vuforia) using the [Vuforia](https://app.gitbook.com/@msd-makerspaces/s/next-lab/~/drafts/-M8DVJZFirWdRBR-baN3/augmented-reality/unity-and-vuforia) AR Engine, AR applications can also be developed for iOS and Android.

These different platforms have different intended uses, as well as different limits in their compatibility and requirements. They also have different inherent functionality, advantages, disadvantages. 

Most students will loan out a Microsoft HoloLens in order to use [Fologram](https://fologram.com/).

### Available platforms:

| Hardware     | Software                                                     | Primary Intended Use                                                                                                                                                                             |
| ------------ | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **HoloLens** | <p>Fologram for Rhino</p><p><br>Fologram for Grasshopper</p> | <p> • Viewing Rhino geometry in AR<br> • Mapping and Designing using Tracking Components in AR</p><p> • Fabricating Rhino and Grasshopper Geometries without the need for plans and sections</p> |
|              | Vuforia                                                      | • AR content creation                                                                                                                                                                            |
|              |                                                              |                                                                                                                                                                                                  |
| **Mobile**   | Fologram for Mobile                                          | <p> • Viewing Rhino geometry in AR</p><p> • Fabricating Rhino and Grasshopper Geometries without the need for plans and sections</p>                                                             |
|              | Vuforia                                                      | • AR content creation                                                                                                                                                                            |

## Articles in this section:

{% content-ref url="/pages/-LXv-JNgCoEgIvABtByz" %}
[Microsoft Hololens](/next-lab/augmented-reality/resources/platforms-hardware/microsoft-hololens.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LXv-LySmM9M2bZzKQGu" %}
[Mobile](/next-lab/augmented-reality/resources/platforms-hardware/mobile.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LXv-nS-gTe4urcmqVhN" %}
[Software Packages](/next-lab/augmented-reality/resources/unity-and-vuforia.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ms-kb.msd.unimelb.edu.au/next-lab/augmented-reality/resources/platforms-hardware.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.