WhatsApp is a chat app that's popular on Android and iPhone devices. WhatsApp sharing may be requested by clients but our testing proves that it is not the most practical feature to include as not every phone has the app.


To set up, the button directs to a URL schema for WhatsApp: whatsapp://send?text=http://image-address-or-url-or-text-goes-here


The Good

It is tested across Android and iPhone devices with similar results across all smart-phones. If the app is installed, it's a smooth user journey that populates the chat component with your pre-defined text or URL once a user is selected.


As you can see, I am spamming Mel with Pre-Defined text.

The Bad

You may have noticed that the image is being sent as a URL. This is because images can not be directly messaged via WhatsApp. An OpenGraph Metatag was implemented in the header of the site in attempt to display a thumbnail next to the URL but this did not prove to be successful.

Furthermore, if the app is not installed - which can definitely be the case, the user will be prompted with an obtrusive alert:

''User: "What does this even mean? Why is a brand I trust sending me to an invalid URL? Why can't I have a Lamborghini?!"'


iPhone and Android both support this one, but as of yet there is no valid fallback for if the user does not have WhatsApp installed. We must warn the client of how his brand will be perceived if the user does not have WhatsApp installed if they are insisting on using it. Of course, if it's a share button alongside other share buttons like Facebook and twitter, they might not mind as the User has other options to share.