Top Banner
Design and Code. Work should be fun. by Andrii Vandakurov, frontend developer eleks.com
16

Design and Code. Work should be fun.

Apr 12, 2017

Download

Internet

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Design and Code. Work should be fun.

Design and Code. Work should be fun.by Andrii Vandakurov, frontend developer

eleks.com

Page 2: Design and Code. Work should be fun.

Designers think outside of the box and see crazy animations, ideas, pixels, and buttons, while developers see the technology, speed bumps, and limits.

Page 3: Design and Code. Work should be fun.

What we can learn from real world ?

Create a site/product is almost the same as build a house. But in our case it could be much cheaper ;)

We need: ➔ communication ➔ prototypes ➔ blueprints

Page 4: Design and Code. Work should be fun.

Prototyping

Its about finding the fastest, cheapest way to validate ideas.

Image from Tom Chi presentation “Rapid prototyping Google Glass” https://goo.gl/jFer6j

Notes:

Page 5: Design and Code. Work should be fun.

Blueprints

Introduced in the 19th century, the process allowed rapid and accurate reproduction of documents used in construction and industry

Blueprints were created by sending light around an ink drawing on transparent film. The light would shine through everywhere except the ink and hit a paper coated with a light-sensitive material, turning that paper blue.

Page 6: Design and Code. Work should be fun.

Specctr

Page 7: Design and Code. Work should be fun.

Communication with the team

Effective collaboration requires effective communication

Tools (Free):

● Marqueed ● Framebench ● Notism

Page 8: Design and Code. Work should be fun.

Features

● Design comments ● Notifications ( via Slack ) ● Export assets/colours ● Styleguide ● Web interface

For now Zeplin works only with Sketch (

Notes:

ZEPLIN

Page 9: Design and Code. Work should be fun.

Frameworks follow the "Hollywood principle", i.e. "don't call us, we'll call you.” A software framework is a re-usable design for a software system.

A library is essentially a set of functions that you can call

Examples: Angular, Bootstrap, Foundation , Backbone, Ember

Examples: React, Jquery, Dojo

Framework vs Library

Page 10: Design and Code. Work should be fun.

A preprocessor is a program that takes one type of data and converts it to another type of data.

● Sass ● Less ● Stylus ● PostCss

Why we need preprocessors ? - Variables, Mixins, Nesting, Partials, Extend/Inheritance and even more …

Notes:

Preprocessors

Page 11: Design and Code. Work should be fun.

Icons

Icon sets (free) :

● Font awesome ● Material icons

Customization tools:

● IcoMoon ● Fonticons ● Fontello ● Fontastic

Page 12: Design and Code. Work should be fun.

We can write it ourselves. But should we? There are lot of free and ready to use animations

● Animate.css ● Bounce.js ● Magic Animations ● CSShake

Here you can find comparison of this libraries http://goo.gl/QZPEh8 ( Top 9 Animation Libraries to Use in 2016 )

Notes:

Animations

Page 13: Design and Code. Work should be fun.

Developing enterprise applications should be fun too.

Page 14: Design and Code. Work should be fun.

● Kendo UI ● DevExpress ● Wijmo ● Essential JS

Link with comparison of these ui sets https://goo.gl/LdFCb2

Notes:

Faster development. Easier integrations with backend.

UI sets

Page 15: Design and Code. Work should be fun.

Cool stuff

● Push notifications ● Track online/offline status ● Splash screen ● Battery api ● Page visibility api ● Audio api

Page 16: Design and Code. Work should be fun.

QA ?Helpfull links: ● specctr ● A Front-End Developer’s Ode To

Specifications ● Zeplin ● Prototyping by Tom Chi from

google ● Best practices for designer/

developer collaboration