- Attempting to scroll, but accidentally lifting the finger for a split second before dragging.
- Any other accidental click - people and phones present an entirely different set of challenges when compared to a mouse & keyboard, which, for the most part stays stationary and free of many of the "accidental click" hazards that using a phone introduces. Things like:
- water splashing
- animals, children, & external "forces" touching the phone unintentionally
- dropping the phone
- shifting hands & accidentally interacting with the phone in other ways that cause clicks on the edge of the screen/email, e.g. with the tip of a finger
- broken and poorly designed screens/sensors cause unintended interactions that developers should work to prevent
Thanks for sharing your thoughts Mark!
I'm very pleased to hear I'm not alone in this, and that one of Email Marketing's biggest voices (you) is in agreement on these specific issues.
RE: "good design" - The recent email designs that led to my discovery of these issues definitely lived up to the standards you mentioned above. They used large, responsive CTAs combined with concise body copy, ideal text-ratios, & proper use of white space and structural design. The issue arose from the lackadaisical approach taken after the design phase was complete. I first ran into these problems during "code reviews" at a large, successful e-commerce company, which, eventually led to enough frustration that I felt compelled to write about it and make a funny minesweeper meme :) It's no fun when developer feedback falls on deaf ears and you don't get recognition for your work.
For me, email development is fun and exciting. I hope more people will grow and share our passion for great email UX, statistical performance, and adoption of best practices/industry standards for the sake of consumers and businesses.
A couple of things I'd add to the list of behaviors that Email Teams should categorize as accidental clicks :
All the above are potential hazards developers and UX designers should and can very easily account for during the build process, which if ignored, will inevitably lead to more frustration and abandonment by recipients.
I'm writing an article detailing these pitfalls, how to avoid them, and how QA and non developers can recognize and prevent these issues from making it into users inboxes.
Thank you for your input Niven!
Linking contextual images and text is okay with me, I'm not sure I would make paragraph text a link myself.
For the sake of the Email Industry and consumers worldwide - Can you think of any other examples of things that might be good to NOT wrap with an anchor tag?
It's funny - I can't reply to your reply (below/above) so I'm responding here instead! If you would like to continue this conversation somewhere more conducive to conversation - please feel free to dm me on twitter: @JoshuelPatterso
I realize this has been a long time, but I was surprised to see no one helped you with your issue.
It appears to me as though you did not consider the overall size and performance of the email itself.
There are very good reasons HTML Email developers get paid for creating Emails, even if the layman or non-technical marketer thinks "it's just email" - they are mistaken. Drag & Drop editors (ESP's that allow building marketing emails with a WSYWG) for instance, will perform significantly worse than having an experienced, passionate UI Dev build your marketing Emails for you.
Take a look at the size difference alone between the two (bottom left of each image shows the overall size). You can also see render and download times for every resource in each email:
While you might not think this matters much, it does. Especially on mobile connections, and you are selling a mobile game.
There is of course much more to go into than just size alone. Many different types of performance issues can arise during the design & development of your emails.
If you ever need any help in the future please do not hesitate to reach out. I'm happy to help.