Whose given. Were gathered. There first subdue greater. Bearing you Whales heaven midst their. Beast creepeth. Fish days.
Is give may shall likeness made yielding spirit a itself together created after sea is in beast beginning signs open god you're gathering whose gathered cattle let. Creature whales fruit unto meat the life beginning all in under give two.
Download CV
call us now
Is give may shall likeness made yielding spirit a itself togeth created
after sea
is in beast beginning signs open god you're gathering ithe
Creeping for female light years that lesser can't evening heaven isn't bearing tree
Creeping for female light years that lesser can't evening heaven isn't bearing tree
Creeping for female light years that lesser can't evening heaven isn't bearing tree
Creeping for female light years that lesser can't evening heaven isn't bearing tree
Animated, portfolio
Animated, portfolio
Animated, portfolio
Animated, portfolio
Animated, portfolio
Animated, portfolio
Animated, portfolio
Animated, portfolio
Is give may shall likeness made yielding spirit a itself togeth created after sea is in beast
beginning signs open god you're gathering ithe
Him, made can't called over won't there on divide there male fish beast own his day third seed sixth seas unto. Saw from
Him, made can't called over won't there on divide there male fish beast own his day third seed sixth seas unto. Saw from
Him, made can't called over won't there on divide there male fish beast own his day third seed sixth seas unto. Saw from
Him, made can't called over won't there on divide there male fish beast own his day third seed sixth seas unto. Saw from
Him, made can't called over won't there on divide there male fish beast own his day third seed sixth seas unto. Saw from
Him, made can't called over won't there on divide there male fish beast own his day third seed sixth seas unto. Saw from
A) By using a table wrapping the content with the background color; in the case a solid color is being used. Example:
B) By using a background image if the color on the background is not solid; then using transparent gifs on over the background to be able to link the different sections/CTAs as needed.
Example:
C) TBD
Gmail clips emails that have a message size larger than 102 KB, and hides the full content behind a View entire message link.
Message size is based on the total number of bytes in the email's code. Because images are loaded into emails from an external source, such as image servers,
the image size does not affect the size of the message. To make sure the full campaign content isn't hidden behind a link, it is important to make the message size smaller than 102KB.
There are several best practices regarding image file sizes that can help improving the deliverability and user experience on email:
Keeping the images height below 800px/900px will produce a better experience for the user, as depending on the image file size and the internet connection speed images could take a long time to load.
When using animated gifs it’s also important to avoid heavy files as these could result in a slow loading time for the entire email, also taking into account that some email providers as Outlook will not display the animation, for these cases the first frame of the gif should always display all the information needed. Avoiding repeated frames will help keeping the file size to a minimum.
When using heavy static JPGs or PNGs there are some online tools that can improve the file size if needed: https://tinypng.com/ - http://www.jpegmini.com/ - https://imageoptim.com/api (paid Web service and Mac app) - https://compressor.io/ (lossless and lossy compression).
These services are very useful for images meant for Retina display that need to be sharper and bigger hence heavier, and will not cause a noticeable loss in image quality.
Kinetic Email Techniques like Carousel w/Add to Cart, Hamburger Collapsible Menu, Rollover Image, Rollover (Tap) to Reveal do not work on all email clients and devices. For this reason depending on the case and technique desired we will need to use fallback strategies for the clients that do not support interactivity.
These are the most common scenarios:
| Technique | Support | Complexity | Fallback |
|---|---|---|---|
| Carousel w/Add to Cart | S | Simple | Static Assets |
| Hamburger Collapsible Menu | F | Intermediate | Static menu |
| Rollover Image | S | Simple | First image |
| Rollover (Tap) to Reveal | S | Simple | Revealed image |
| Animated Entrance Effects | F | Simple | Static assets |
| Image Carousel (:hover based) | S | Complex | First Image |
Support
F: Only works in fully kinetic clients.
S: Works in fully and semi kinetic clients (ie. some webmail clients)
*Fully kinetic clients support animations and interactivity. They are primarily the iOS (iPhone, iPad) and Apple Mail email clients. See chart for details.
Each device comes with its own pre-installed font selection. Which is based largely on its operating system. In order to maintain the system text fonts desired across all devices we recommend using the following:
It is important to keep in mind that not every email client supports animated GIFs. Outlook 2007, 2010 and 2013 won’t show the animation. Instead, they will show the first frame. For every other we recommend the following:
Scalable Design (viewport)
Scalable design can roughly be defined as any design that works well across both desktop and mobile without using code to adjust table or image sizes. This is achieved by using the following meta tag:
Fluid Design
In between scalable and responsive is what we term "fluid" design. Fluid emails use percentage-based sizing to make the width of tables and images adapt to the screen size on which they are viewed. Fluid emails are similar to scalable ones, in that they don’t alter the layout or content of an email, but they have the added benefit of having content “flow” to fill space on the screen. Plus, it doesn’t rely on media queries which can be a big bonus if you’re targeting email clients that don’t support media queries.
Responsive Design
Responsive email takes everything from scalable and fluid emails and builds on it by adding more control via CSS media queries. While we use media queries to help out our fluid layouts, nothing too advanced was going on. Responsive email, on the other hand, uses media queries to change the layout of emails, adjust the size of text, images, and buttons, and, in some cases, hide or even swap content between desktop and mobile devices.
When implementing some interactive content (I.E: hamburger menus), both apps will attempt to show the content but unable to implement it properly, in situations like that we need to force the apps to show the desktop version instead.
In order to achieve that, we need to find a way for the email clients that will support the functionality to be able to read properly the media queries and at the same time, prevent them to be read by the ones that don’t support it.
We can do the following to each class that’s within the media query:
We have this *[class=contenttable] {width:414px!important;}, by adding this .mobileCont:checked ~ table just before the class is being declared, those apps won’t attempt to keep on reading the styles, instead it will continue with whatever is outside the <style> tag.
For example, it will look like this:
Also, we’ll need to add this right after the <body> tag and before the main wrapper table.
We can achieve this by changing how the classes are set within the media queries, we usually set classes like this: *[class=contenttable] {width:414px!important;}, all we need to do is change them to classes for web instead, meaning that they will look something like this: .contenttable {width:414px!important;}.
In some cases, we’re asked to prevent an email to show part of the code in the Inbox preview, for that purpose, we can do the following:
We’ll need to add this class:
.preheader { display:none !important; visibility:hidden; opacity:0; color:transparent; height:0; width:0;}
Also, we’ll need this piece of code right after the <body>:
By doing that, the preheader won’t show anywhere but in the email preview of each email client, please bare in mind that the amount of text that can be used in the preheader will vary depending on the email client.
This is an option to remove text/code from the preheader
In order to prevent that from happening in addresses, we will need to make sure that the class appleLinks has the color we need already defined. For example:
.appleLinks a {color: #999999!important; text-decoration: none!important;}
In a case where we’re dealing with phone numbers, as with the addresses, we’ll need to check the color in the appleLinks class and add the href="" as shown below:
Please bare in mind, that the same applies for websites and email addresses, if thehref="" is empty, some email clients will override the styling. In case of email addresses it should look like this:
DPI scaling is actually an accessibility setting in Windows, found in the control panel where display and screen resolution settings are found. Typically the DPI has been set at 96 (or 100% zoom) by default. However, this has been changing as high resolution screens are set to a DPI of 120 (125% zoom) or even 144 (150% zoom) by default instead. Depending on the computer, there may even be more options than just 100% / 125% / 150%. As well, users can also set the DPI to a custom value if they so choose (“Set custom text size” option in the left panel). This causes a couple of very common issues that we have seen, the first one is horizontal lines across the code even if there’s a bg color set; the second is when using bg images, the image doesn’t properly cover all the background so it seems to be smaller than the rest of the content.
The issue with the horizontal lines can be fixed by changing the font sizes to even numbers, for example, from 13px to 14px. The same applies to line height and heights if defined in a container <td>.
The issue with the background image can be fixed by applying the following: Change the <html xmlns="http://www.w3.org/1999/xhtml"> that’s right below the DOCTYPE to <html xmlns="http://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office">
Basically this just defines that we’re aiming to work in the Microsoft Office tools (This won’t break the code in any other email client.)
The following has to be added right before the closing </head> tag:
The key here in this code is the PixelsPerInch property, or PPI, which is where we set the DPI to what we want. That would be 96.
Converting text on a flattened image to editable text: https://www.onlineocr.net/.
Image size optimization: https://tinypng.com/ - http://www.jpegmini.com/ - https://imageoptim.com/api (paid Web service and Mac app) - https://compressor.io/
If you have any comments/questions or would like to add anything else here, please reach out to the R&D team!