How to we successfully design and implement movement into our websites and digital products?
Today I’ve been fortunate enough to have a design problem on my to do list. I need to work out how to visualise that something triggered by the user is ongoing.
In the race for new products and features, sometimes we lose sight of why something exists in the first place.
This week our electric kettle died. As a tea drinker, this is a code red situation. A replacement needs to be sorted quick. My other options for boiling water were, well, slow in comparison.
Buffer say that they lost nearly half of their social referral traffic in the last year. I’m going to do one of those annoying things and not answer the question I pose in the title. I don’t have access to Buffer’s data so I can’t give you any real insights.
What I will do is give you some ideas about how to dig deeper into these kinds of “oh my!” moments that you find in your analytics data. Sometimes it’s too easy to take figures at face value, panic and draw the wrong conclusions.
Various drafts of this post have been with me for years.
The title has evolved over time as my “answers” to the problem have swung back and forth. The problem itself has undergone several incarnations as I’ve learnt new things and my experiences challenged its definition.
From version 8 of the Safari web browser the navigation timing API is supported. This marks the last of the major browsers to include support. It will also see navigation timing supported in iOS.