Tweak #1

Contextualise: How to present the information architecture without cluttering the display?
Communicate: Use transition effects to tell a story.

Before: The “usual” way of highlighting information.

<div id="myElement">
    <a href="myURL">Maps</a>
</div>

var myIcon = document.getElementById( "myElement" );

addEventListener("mouseover", mouseOver );
function mouseOver(event) {
    myicon.style.transform = "scale3d(1.20, 1.20, 1.20)"; // node;
    mylink.style.border = "solid 1px black"; // link
}

Tweak #2

Contextualise: How to reveal information hierarchy quickly?
Communicate: Stagger the entrance of containers progressively.

Before: A “typical” page load

Tier-two. The middle container shows summary information and related topics for users who are interested to find out more.

Tier-three. If users are indeed engaged, they can trigger the far-left container to reveal more information (see the demo from part-four of our story).

Initiate the “start/hidden” position of all containers.

rightContainer.style.transform = "translate3d(50vw, 100vh, 0)";
middleContainer.style.transform = "translate3d(25vw, 100vh, 0)";
leftContainer.style.transform = "translate3d(0vw, 100vh, 0)";

Sequence the entrance towards the “end/show” position.

rightContainer.style.transform = "translate3d(50vw, 0vh, 0)";
setTimeout(() => {
    middleContainer.style.transform = "translate3d(25vw, 0vh, 0)";
}, 200);
setTimeout(() => {
    leftContainer.style.transform = "translate3d(0vw, 0vh, 0)";
}, 400);

• setTimeout delays code execution to emulate the staggered animation effect.
• The “start/hidden” position of each container is 100vh (from the top). The “end/show” position will be 0vh.
• keyframes or transition-delay can produce similar results.
• Select an easing transition to create butter-smooth animations.

Tweak #3

Contextualise: How to maximise the view and navigation space.
Communicate: Autohide unused UI elements during navigation events.

Before: Visible navigation space is halved. While users can view content on the “sticky” container, it is not needed in the midst of a navigation event itself.

fadeOutSticky(){
    rightContainer.style.opacity = "0";
};

// reusing event listener (from part-one discussion)
canvas.addEventListener("mousedown", handlerGrab, false);

function handlerGrab(event) {

    if (event.which == 1) {
        ...
        fadeOutSticky();
    };
    ...
}

Tweak #4

Contextualise: How to “not-block” active elements
Communicate: Autohide blocking elements in response to interaction events.

Fadeout the minimap so that it won’t “block” the mouse cursor when users are “panning” the canvas (a navigation feature discussed in part-two).

canvas.addEventListener("mousemove", handlerMouseMove, false);
function handlerMouseMove(event) {
    if (event.which == 3) {
        if ( boundingbox(event.clientX, event.clientY, minimap) != false) {
            minimap.style.visibility = "hidden";
        } else {
            minimap.style.visibility = "visible";
        }
    }
}

boundingbox is a custom function to determine if the mouse cursor is currently hovering over the minimap.

function boundingbox(ClientX = 0, ClientY = 0, element) {
    if (element.getBoundingClientRect) {
        var rect = element.getBoundingClientRect ();
        y = rect.top;
        xR = rect.right;
        yB = rect.bottom;
        xL = rect.left;
        boxHeight = yB - y;
        boxWidth = xR - xL;
    }
    if ( ClientX <= (xR) && ClientY <= (yB) ) {
        return true;
    } else return false;
 }

Tweak #5

Contextualise: How to use the “hidden dimension” to reveal a deeper information architecture?
Communicate: Emulate a see-through effect by manipulating the opacity level of the “above” element. The content of both the above and underneath layers are visible to help users visualise a more complete picture.

You can broaden the navigation view or create a sense of visual depth with just the opacity value. Notice the semi-visible layer underneath the minimap (top-left) and the sticky container (right-hand side)?

Tweak #6

Contextualise: How to show related information only when it’s relevant (without a page reload).
Communicate: Hide the information by default, but show on mouse focus.

A little background on the Google Cloud Platform (GCP). In the GCP world, PubSub is tightly integrated with other GCP products. While PubSub may be categorised under Big Data, it is also a key integration point for many GCP products. How can we feature this contextual relationship without cluttering the view? It’s not so complicated once we do this.

The technique is similar to how we would highlight the nodes (discussed in part-one of the story).

“Hide” the dotted line.

dottedLine.style.borderRight = "1px dashed #FFF"; 
// opacity or visibility works well too

When we mouse-over the PubSub node, the eventlistener for the previously hidden dotted lines become visible. Note that other non-essential links become hidden. With just one line of code, you can achieve a funnelling effect on the user’s attention and tell a story without narration.

dottedLine.style.borderRight = "1px dashed #ddd";

It’s almost mandatory to apply a fade-in fade-out transition.

dottedLine.style.borderRight = “300ms ease”;

Tweak #7

Contextualise: How to show the contextual usage of the mouse cursor?
Communicate: Update the mouse cursor icon to signify different usage or behaviour.

Interacting with the minimap. Users drag the rectangular bracket (top left) within the minimap to update the canvas (main view). The cursor change from a default pointer to a four-way arrow.

canvas.style.cursor = “-webkit-grab”;  // hand icon
canvas.style.cursor = “-webkit-grabbing"; // fist icon

Tweak #8

Contextualise: How to add contextual usage to the same mouse click?
Communicate: Differentiate a mousedown from a mouse click.

We want a left-click to do this.

As you can see, a left-click is not the same as a prolonged left-click. The later drags the canvas.

A mouse button can have dual usage and still feel intuitive. When a left-click is on mousedown, and not mouseup yet, it may mean either:

1. click on something, or
2. drag things.

It’s trivial to implement. The trick is knowing what happens after the mousedown event is detected. Is there an immediate mouseup event or a mousemove event? The former suggests a “standard” click and the later a custom drag action.

If a mouseup is not detected within, say 300ms, then let the user drag the canvas.

In the main while loop (from part-one), listen to the mousedown event.

while (item[i]) {
   itemElementName[i].addEventListener("mousedown", clickTimer );
   ...
}

Add a custom function named clickTimer to determine whether it’s a click or a drag.

var mouseClick = true; function clickTimer(event) { ... // measure the time interval between mousedown and mouseup ... }

Since we’re only interested in knowing if the time interval is more than 300ms (not the same as the interval value itself), we can use a simple hack to do the job.

// measurement hack
setTimeout(function(){
    mouseClick = false; }, 300);

On mousedown, set mouseClick to true. However, after 300ms, set it to false.

Tweak #9

Contextualise: How to transit from “in-browser” to full-screen mode.
Communicate: Provide a quick-toggle option.

Toggle-to-interact. Offer an option to go interactive. By default, the “in-browser” mode won’t block users from scrolling pass the canvas (also see scroll from part-two). A toggle will enable navigation from within the canvas.

Use the zoom API to increment or decrement size.

canvas.style.zoom = zoomLevel;
zoomLevel = zoomLevel + 0.01; //increment the zoom level

Tweak #10 (Zoom with easing)

Contextualise: How to make UIs respond in a fluid and human-like manner?Communicate: Incorporate an easing function to create an intuitive experience.

Animation and easing effects work hand in hand to provide useful visual cues for users. One example is the original iPhone end-of-page “rebound” effect.

Let’s try this on our zoom example.

function easeInOutQuad(t, b, c, d) {
    if ((t /= d / 2) < 1) return c / 2 * t * t + b;
    return -c / 2 * ((--t) * (t - 2) - 1) + b;
}

function spreadZoom(direction) {
    var time = 0;
    var diff = 1;
    var minTime = 5;
    var maxTime = 40;

for (var i = 0, len = diff; i <= len; i++) {
        (function(s) {
            setTimeout(function() {
                if (direction == 'zoomin') {
                    ...
                } else
                if (direction == 'zoomout') {
                    ...
                };
            }, time);
    })(i);
    time = easeInOutQuad(i, minTime, maxTime, diff);
    } // for loop
}

The result is a smoother start-stop curve that mimics a more natural response.

• spreadZoom breaks a physical scroll action into a series of smaller virtual zooms “spread over” a easeInOutQuad curve.
• easeInOutQuad creates the analogue effect. The formula is based on the Robert Penner’s easing equation.
• The behaviour can be further configured via time, diff, minTime, and maxTime variables.

Concept aside: Easing

Why is easing a first-class citizen in UI design?

Next Steps

Some of the most complex UIs are built on top of the simplest ideas. Once we apply those ideas to contextualise the problem, we can create solutions that work better.

While we’ve devoted five stories and covered some of the most common Javascript techniques, we are saying only one thing. Anyone can create a compelling design with just simple tools. Anyone can transform a casual visit into a superior user experience.

Links to other parts

Part-one sets the foundation for designing interactive infographics.

Part-two adds navigation features to browse content.

Part-three adds a dynamic mini-map to enhance navigation.

Part-four adds an inline UI to access layered content.

Part-five → You’re are here. Yay!