Times Square Interactive AdsDecember 2005 - January 2006
Client: PlayMotion / AT&T
The operation of the camera application was split up into many parts. It starts with a "voice site" that people call and prompts them to press buttons. This is done via a configurable 3rd-party web service that can interact with our application by sending web requests to a server and receiving responses. Another programmer and I jointly configured the voice site, with me primarily focusing on its interaction with our application. I also created web scripts that the voice site interacted with in order to hold callers in a waiting queue while someone else is in control.
My main responsibility was the server application that listened for and responded to messages from the voice site. It also controlled the motion of the camera. I had to design several different methods of controlling the camera with a phone and iteratively refine them through user-testing, with final selection by the client. I had to consider factors such as whether the camera motion was continuous with a stop button or in discrete steps. Which is more appropriate for pan versus tilt? What should the speed or step size be? How should that vary depending on the zoom? The goal was for someone on the street to be able to find themselves in under 60 seconds. When the time is up, my camera control program was responsible for uploading the photos and sending the caller a text message with the URL.