Motion Recorder Motion Recorder

A web-application to record and save sensor cassettes

Adtile's Motion Recorder is a web-application that runs in any mobile web-browser and records sensor data cassettes (motion cassettes).

How to Use the Motion Recorder application

  1. Open the Adtile Motion Recorder in the desired web-browser on a mobile device.
  2. To begin recording press the
  3. To stop recording press the
    button again. The data is saved in a new motion cassette file. The file name will be a large integer representing the current time in milliseconds.

Recommendations for Recording High Quality Sensor Data

Before opening the Motion Recorder consider the type of motion desired to be recorded. What feature are you testing for? Is it a simple motion or a more complex motion? Can you fully describe the exact solution for how the motion should trigger the feature being tested? Remember, the cassette has to be recorded only once; however, it could be replayed many times in the future. This is why careful consideration must be taken to guarantee the appropriate motions are captured without any erroneous data artifacts. Although seemingly tedious, these steps will help maintain a high quality recording library. Cassettes can be used for automated functional testing, feature optimization, machine learning, and testing device functionality when the device is not available, etc.

Laboratory testing should be as objective as possible. This particular type of lab testing has an inherent subjective side due to each user’s individual motion traits and feel. Using a robotic exact motion will give the lab worker greater knowledge and repeatability of the motion. Where as collecting actual user data, together with their experience response, will enable the lab worker to map exact motion measurements to human perceived motion measurements.

  1. Be aware of the initial position of the device before opening the Motion Recorder application.
  2. Hold the device steady and gently press the
    button to start and stop. This is to prevent unwanted bumps in the recorded data.
  3. Allow some time to pass before pressing the
    button to start recording. This allows the sensors to completely fire-up.
  4. After pressing the
    button, wait a second before beginning the desired motion. This will guarantee the beginning of the motion is fully captured in the cassette data.
  5. Move the device in a controlled fashion. Steady mechanical motions are optimal for testing basic feature behavior. More natural motions are desired for designing features for robust user experiences.
  6. After completing the motion, wait a second before pressing the
    button to stop recording. This will guarantee the end of the motion is fully captured in the cassette data.
  7. Press the
    button to confirm that the recording is satisfactory and keep it in your data repository, or press the
    button to clear the cassette and try recording the desired motion again. Start by capturing single simple motions per cassette. Then move on to more complex motions.
  8. Rename the cassette with an appropriate filename. The filename should distinguish the device manufacturer, model, operating system, web-browser, feature being tested, a compact description of the motion, and recording persons name.

    1. General naming convention. <device>-<os>-<browser>-<feature>-<motion>-<person>.txt

    2. Example, iphone4-ios7.1.2-safari-flick-Right5-medium-johnSmith.txt. This example represents 5 flicks to the right at “medium speed”, to be used to test the horizontal tilt feature.

  9. Document the exact feature behavior that should be triggered for each type of motion.

    1. Example from above, iphone4-ios7.1.2-safari-flick-Right5-medium-johnSmith.txt. A Javascript array describing the exact output of the tilt feature is: [4,4,4,4,4] where DIRECTION_RIGHT=4 represents the returned parameter value {direction: DIRECTION_RIGHT }.