#08 (Due 3/30)

This two-part set of deliverables, due March 30, consists of a brief speed project that requires no coding or software development, and a virtual sculpture project (to be completed in Unity) that is simple, as Unity apps go, but requires some consideration.


Part 1. #JustALine Speed Project

This is a continuation of the JustALine Speed Project we started in class. The purpose of this assignment is to get you “warmed up” to thinking about designing AR experiences. 

Google’s JustALine Android app is a simple AR tool that allows you to draw [static] white lines in space. In collaboration with a partner, use this sketching tool to mock up a prototype of an AR experience or environment. Allot yourselves no more than one hour to come up with the concept and draw the sketch prototype.

Document your design with (A) a screenshot or screengrabbed video/GIF from the Android device itself; (B) an over-the shoulder photo, video, or animated GIF showing your sketch in context; and (C) a brief written text explaining how a “full-fledged” version of your AR concept might operate. (If you wish, you can make “before/after” drawings in order to illustrate a change of state.) Feel free to let your imaginations roam widely, and don’t worry about whether or not you have the skills or knowledge to implement your concept: assume that it’s possible to have plausible technical features like face detection, speech-to-text, etc., if you need them.

For example, here is a sketch for a simple “Limbo” experience made using JustALine. This is the “screenshot” taken directly from the phone. (Google around for ‘how to screenshot’ or ‘how to record screen’ on Android.)

And here is the “over-the-shoulder” shot, showing the Limbo design in its context of use. This indicates that the phone is held vertically, at approximately eye-level (but you shouldn’t take that for granted; it could be otherwise in your design!)

If this were your project, you might write some additional text about how the Limbo app would work. For example: perhaps your concept calls for the use of body-detection (such as OpenPose) to understand whether or not the player clears the path….

I do acknowledge that the JustALine app makes certain things easy to prototype, and other things could be difficult to mock up with it. Just make the most interesting thing you can with it. Just so you know, there is no commitment implied with this prototype, i.e. the design you make is not necessarily a sketch for your final project.

Now: 

  • Create a blog post, with the title nickname1-nickname2-arsketch.
  • Give your blog post the Category, 08-arsketch.
  • Provide a very brief one-sentence description of your concept (like a tweet), and list the nicknames of the collaborators who made it.
  • Include the screenshot image (or screengrabbed video or animated GIF) media.
  • Include the over-the-shoulder media (preferably video or animated GIF, please).
  • Include a brief text about your concept: how it would be experienced, etc.
  • No need to document the same project twice. It’s fine if one of the collaborators blogs the project, and the other collaborator just links to the other one’s documentation page.

Part 2. A Brief Video About A Site-Specific Virtual Sculpture

The site is a place where a piece should be but isn’t. (Robert Smithson)

In this project, you will collaborate with a partner to create a simple AR app in Unity, and document it in a brief video.

Create a custom Unity AR app, in order to:

  • place and view a virtual object of your choice,
  • at a scale of your choice,
  • in a specific location of your choice,
  • with a programmatic behavior of your choice.

Justify your decisions. Document your work. It is assumed that your project will run on a mobile device, but if necessary, it could be possible to use your laptop instead. Use this project as an opportunity to learn how to do something new in Unity.

  • Your object may be appropriated, recycled, or constructed (with the only restriction that it may not be a white cube). For example, you could download a readymade 3D model from yobi3D, or you could model something in Rhino or Maya. You might conceive of your object as a “sculpture”, “monument”, “installation”, “decoration”, etc. or as something else entirely (“anomaly”, “natural formation”, etc.)
  • Your location may be public, private, generic, etc. (with the only restriction: it may not be the STUDIO classroom). For example, your site could be a prominent and unique location (the CMU Fence), or it could be a generic-seeming place (a supermarket meat section), or it could be a very personal spot (your bedroom, or the palm of your hand).
  • Your programmatic behavior should be some code you have written that makes the object do something. For example, it could spin (rotate) in place, or bob up and down, sinusoidally; it could emit a shower of particles (like a fountain); it could change size whenever the viewer gets close; it could swap out for a variant whenever the viewer looks away and looks back .

Document your project with screenshot/screengrabbed media, as well as with over-the-shoulder media.

  • Create a blog post, with the title nickname1-nickname2-arsculpture.
  • Give your blog post the Category, 08-arsculpture.
  • Provide a very brief one-sentence description of your project, and list the nicknames of the collaborators who made it.
  • Include the screenshot image (or screengrabbed video or animated GIF) media.
  • Include the over-the-shoulder media (preferably video or animated GIF, please).
  • Include a brief text about your project. Discuss the relations you have established between object, environment, and viewer. Why is this object in this place?
  • It’s fine if one of the collaborators blogs the project, and the other collaborator just links to the other one’s documentation page.

Consider: unusual monuments, etc.