The document outlines six UI tips to enhance developer satisfaction, emphasizing the use of base 8 for padding, consistent color naming conventions, and establishing a single source of truth (SSOT) for brand assets. It advises saving high-resolution images and including fonts in design handovers while discouraging the use of WeTransfer for file sharing. A concise TL;DR summarizes the key points to focus on for effective collaboration.

1. 6 UI tips to make your
developers happy
There's a TLDR; at the end if you can't be arsed to read

2. Work in base 8
We know it's basic, but developers love a bit of
base 8. Especially with Apple & Google adopting
base 8, make everyone's life a little easier.
If you don't know what base 8 is, it basically means - make padding
divisible by 8, so a card could be 8px/pt away from the edge of the
screen

3. Settle on a naming
convention
Labelling your colors: primary, secondary, accent
is a big step instead of #8224E3, #FF0068,
#170728
It's always worth communicating with your developers to ensure
you're adhering to the same naming conventions, instead of finding
out later from a massive Zeplin file

4. Make a SSOT
SSOT stands for "Single source of truth" and it
basically means a big file where a marketer,
developer or non-designer can find all brand
assets
It cuts down on messing around finding a company logo, company
colors and assets, and it stops Kevin from using 14 slightly di erent
o -brand variations of your company colors... God-damnit Kevin

5. Save a hi-res version of
images
Save countless hours, by including the images
you've used within your artboards as a separate
hi-res file.
Us developers usually have 100 ways we can optimise an image,
so getting the original source is a blessing. So don't be shy in
sending a 4k pic because you can always downscale, but never up.

6. Include the fonts
If you're using fontbase, or another font handling
tool. Make sure you include the original font for
your devs
We only really need 1 version (usually .otf) so we can generate an
optimised pack to be able to use them on the site

7. Don't use WeTransfer
There's a special place in hell for people that
handle data transfer via WeTransfer, just send a
Google Drive link or better yet, a cloud link
We love WeTransfer and definitely think it's a cool tool, but don't
send countless files via WeTransfer as it's guaranteed to get lost
after 10 or so minutes

8. TLDR;
Work in base 8
Label colors with naming convention
Learn what SSOT is, then build one
Backup UI stock images in separate file
Include fonts in handover or where to get
Don't use WeTransfer