Tag Archives: microinteraction

Mission slot

by

1

To provide the Victim Cards to the Robot Asesino, Orlak inserts it into an open slot in the robot’s chest, which then illuminates, confirming that the instructions have been received.

There is, I must admit, a sort of lovely, morbid poetry to a cardiogram being inserted into a slot where the robot heart would be to give the robot instructions to end the beating of the human heart described in the cardiogram. And we don’t see a lot of poetry in sci-fi interface designs. So, props for that.

The illumination is a nice bit of feedback, but I think it could convey the information in more useful and cinegenic ways.

In this new scenario…

  • Orlak has the robot pull back its coat
  • The chamfered slot is illuminated, signaling “card goes here.”
  • As Orlak inserts the target card, the slot light dims as the chest-cavity light brightens, signaling “I have the card.”
  • After a moment, the chest-cavity light turns blood red, signaling confirmation of the victim and the new dastardly mission.

When the robot returns to Orlak after completing a mission, the red light would dim as the slot light illuminates again, signaling that it is ready for its next mission.

These changes improve the interface by first drawing the user’s locus of attention exactly where it needs to go, and then distinguishing the internal system states as they happen. It would also work for the audience, who understands by association that red means danger.

The shape of the slot is pretty good for its base usability. It has clear affordances with its placement, orientation, and metallic lining. There’s plenty of room to insert the target card. It might benefit from a fillet or chamfer for the slot, to help avoid accidentally crumpling the paper cards when they are aimed poorly.

In addition to the tactical questions of illumination and shape of the slot, I have a few strategic questions.

  • There is no authorization in evidence. Can just anyone specify a target? Why doesn’t Gaby use her luchadora powers to Spin-A-Roonie a target card with Orlak’s face on it and let the robot save the day? Maybe the robot has a whitelist of heartbeats, and would fight to resist anyone else, but that’s just me making stuff up.
  • Also I’m not sure why the card stays in the robot. That leaves a discoverable paper trail of its crimes, perfect for a Scooby to hand over to the federales. Maybe the robot has some incinerator or shredder inside? If not, it would be better from Orlak’s perspective to design it as an insert-and-hold slot, which would in turn require a redesign of the card to have some obvious spot to hold it, and a bump-in on the slot to make way for fingers. Then he could remove the incriminating evidence and destroy it himself and not worry whether the robot’s paper shredder was working or not.
  • Another problem is that, since the robot doesn’t talk, it would be difficult to find out who its current target is at any given time. Since anyone can supply a target, Orlak can’t just rely on his memory to be certain. If the card was going to stay inside, it would be better to have it displayed so it’s easy to check.
  • How would Orlak cancel a target?
  • It is unclear how Orlak specifies whether the target is to be kidnapped or killed even though some are kidnapped and some are killed.
  • It’s also unclear about how Orlak might rescind or change an order once given.
  • It is also unclear how the assassin finds its target. Does it have internal maps with addresses? Or does it have unbelievably good hearing that can listen to every sound nearby, isolate the particular heartbeat in question, and just head in that direction, destroying any walls it encounters? Or can it reasonably navigate human cities and interiors to maintain its disguise? Because that would be some amazing technology for 1969. This last is admittedly not an interface question, but a backworlding question for believability.

So there’s a lot missing from the interface.

It’s the robot assassin designer’s job to not just tick a box to tell themselves that they have provided feedback, but to push through the scenarios of use to understand in detail how to convey to the evil scientist what’s happening with his murderous intent.

J.D.E.M. LEVEL 5

by

2

The first computer interface we see in the film occurs at 3:55. It’s an interface for housing and monitoring the tesseract, a cube that is described in the film as “an energy source” that S.H.I.E.L.D. plans to use to “harness energy from space.” We join the cube after it has unexpectedly and erratically begun to throw off low levels of gamma radiation.

The harnessing interface consists of a housing, a dais at the end of a runway, and a monitoring screen.

Avengers-cubemonitoring-07
Fury walks past the dais they erected just because.

The housing & dais

The harness consists of a large circular housing that holds the cube and exposes one face of it towards a long runway that ends in a dais. Diegetically this is meant to be read more as engineering than interface, but it does raise questions. For instance, if they didn’t already know it was going to teleport someone here, why was there a dais there at all, at that exact distance, with stairs leading up to it? How’s that harnessing energy? Wouldn’t you expect a battery at the far end? If they did expect a person as it seems they did, then the whole destroying swaths of New York City thing might have been avoided if the runway had ended instead in the Hulk-holding cage that we see later in the film. So…you know…a considerable flaw in their unknown-passenger teleportation landing strip design. Anyhoo, the housing is also notable for keeping part of the cube visible to users near it, and holding it at a particular orientation, which plays into the other component of the harness—the monitor.

Avengers-cubemonitoring-03

The monitor

In the underground laboratory, an (unnamed?) technician warns lead scientist Selvig that, “it’s spiking again,” and the camera pans down to this monitoring interface.

JDEM

Header

The header is a static barcode followed by the initialism J.D.E.M. along with its full name, the Joint Dark Energy Mission. (Sounds super cool and sci-fi, right? Turns out it is a real program between NASA and the US DOE.) Another label across the top identifies the screen as LEVEL 5 and that it belongs to PROJECT PEGASUS and NASA.

3D map

A main display shows a 3D wireframe of the tesseract, with color-coded nebula-like shapes within the cube. The wireframe (and most of the text on screen) are a bright cyan, with internal features progressing in color from the cyan through white to a blood red, all the way to lens flares near the most active areas in the cube. The color choices make for a quick read of what is “cool” and what is “hot,” so are effective for being immediate, but if the lens flares are designed into the system to indicate peakness, it’s a bad choice for obscuring other data in the display.

Note that the wireframe of the cube is also rotating slightly, which is  very helpful for a user to more fully understand 3D information from a 2D screen. It might be even better mapping with less cognitive load if the display was a volumetric projection. (VPs exist within the Marvel Cinematic Universe (MCU), but so far I believe we’ve only ever seen them in Tony Stark’s possession so perhaps he has not released it to the outside world.) Hopefully in its rotation on this monitor it does not rotate in 360°, as the regularness of the cube would make it difficult to understand where an internal anomaly might exist in the real thing. Hopefully the wireframe only wavers back and forth within a few degrees, and is oriented in roughly the same way an observer glancing at the real thing would see it in the housing, to allow for instant mapping of problem areas.

Avengers-cubemonitoring-01

Warning

Just to the left of the 3D map is a data monitoring panel. Its top label blinks a red WARNING CRITICAL ENERGY LEVELS and a percentage readout. The panel also features a key whose colors match those of the map. (As it should.) Hopefully a microinteraction allows a user to touch any part of the map, freeze the rotation, and get the percentage details of the touched point. A detail box wavers its vertical position along the key to provide a user a quick assessment of its value, and also contains a percentage readout for precision. Judging by the position of the box and the readout, it looks like the 100% mark is about halfway up the screen. Hopefully the upper part of the scale is logarithmic to accommodate massive surges in values.

Additional elements of the display include several scrolling waveforms and text boxes with inscrutable data and labels. It’s easy to imagine these as useful (say total energy values for specific electromagnetic frequencies) but they’re difficult to read, so difficult to formally evaluate.

All told, a nice display (per some assumptions) for monitoring what’s happening with the cube.

Now if only they had applied that solid design thinking to that dais vs. cage problem.

Avengers-cubemonitoring-04