Steve Litchfield

You'll be familiar with 'Whack-a-mole', a fairground game where you have to bash moles that 'pop up' with a mallet. As the game progresses, more and more moles appear, adding difficulty. All of which is brought to mind by app notifications on the modern smartphone. It's a real issue. Especially when starting out with a new phone (as opposed to cloning your old one, Apple-style, which often restores your settings, helpfully), every single application you install has its own ideas of what it wants to 'push' at you multiple times of day. Install 50 apps (a common average) and you are almost literally drowning in notifications, banners, toasts, and so on. The average phone user tends to roll with all this and simply accept the deluge of notifications as a fact of life, watching "Scar213 has liked your reply" or "eBay thinks you'll like this new plastic widget, 5% off" or "Bargain Promotions has emailed you with an ultra-exclusive...

Back in the day, a photo used to be a negative or print, a video would be an 8mm film or perhaps VHS tape - and then the digital age was upon us, with the advent, especially, of phones with cameras. Starting with, arguably the Nokia N93, in 2006, we had useable, focussed, 3MP photos, and useable 'DVD quality' video files - captured from a phone. A photo was, typically, a .JPG file and a video was, typically, a .MP4 file (I won't get into codecs here, to keep things simple). Each - literally - just a file. And then manufacturers started adding on information. Some of which could be contained within the original files, but mostly... not. Starting with Nokia's experiments with 'live' photos on their Lumia phones around 2012, where a small section of video (from before the shutter was pressed and after) was captured and stored with the JPG photo. Then, with the core of Nokia's imaging team being made redundant and moving to Apple, we had live photos making a wel...