Roadmap

THE OBJECTIVES

A Brief Schedule of Milestones and Deliverables (Subject to change)

April 20 - April 26

    • Finalized Project Specifications

    • iOS AR Application

      • Learn Unity and get familiar with interface

      • Learn ARKit plugin in Unity to create a basic AR game

    • PC Oculus Application

      • Familiarize with Unity and built in XR settings

      • Load Maya models to create a simple application

        • Move around / VR teleportation

April 27 - May 3

  • iOS AR Application

    • Build portal in AR to load existing Maya model

    • Focus on 2 ancient gods parts

  • PC Oculus Application

    • Refine interaction with VR environment

      • Collision detection and maneuverability

May 4 - May 10

    • iOS AR Application

      • Add more interactive functions within the portal

        • Playing audio / video

    • PC Oculus Application

      • Implement interactable elements

        • Audio recordings

        • Grabbable objects

May 11 - May 17

    • iOS AR Application

      • Add functions to enable user interaction with models

    • PC Oculus Application

      • Add menu options and additional tools

        • Flashlight object, Scene change / reset

May 18 - May 24

    • iOS AR Application

      • Finish project report

    • PC Oculus Application

      • Add guided tour experience

May 25 - May 31

    • iOS AR Application

      • Use Vuforia to build a cross platform version of the application

    • PC Oculus Application

      • Support multiple scenes and additional levels

June 1 - June 7

    • iOS AR Application

      • Refine Maya model by adding more texture and ancient relics

        • Feathered Serpent Decorations

      • Launch to App Store

    • PC Oculus Application

      • Polish application and improve user experience


THE CONSTRAINTS

The Potential Risks Encounterable and Goal Feasibility

  • Unfamiliarity with Unity Engine and learning a new tool to use

    • Need to learn and assume that goals are achievable

  • Features are sequentially implementable

    • Potentially can be roadblocked by core feature

  • Heavily subjective user interaction

    • Projects aim to provide significant sensory input to user, may be overwhelming or undesirable

  • Significant work required to port assets into Xcode projects

    • Delayed workflow and compatibility issues