North Dighton website designers
Hello and welcome to this website designers Web Designer North Dighton video tutorial.
I’m Owen Corso from Google.
And today, we’re going to build a rich media expandable creative with video.
Let’s start by selecting file, New File.
This opens a dialog box where we will set up our ad.
First, let’s make out high of project.
We have four options– The default is Display & Video 360so we will leave that as is.
Color in Design Systems
OWEN CORSO: Hello and welcometo this Google Web Designer video tutorial.
I'm Owen Corso from Google.
And today, we're goingto build a rich media expandable creative with video.
Let's start by selectingFile, New File.
This opens a dialog boxwhere we will set up our ad.
First, let's chooseour environment.
We have four options-- The default is Display & Video 360so we will leave that as is.
Next, we can selectthe type of ad.
We want to make anexpandable, so we select Expandable on the left.
Next, we can set upour ad's dimensions.
We are building a 320 by 50that expands to 480 by 250.
So I will make those changes.
We then assign thecreative a name.
I will leave my Save ToLocation as the default, and leave the animationmode set to Quick.
Once I'm happy with mysettings, I click OK.
Google Web Designer creates theinitial pages of the ad for me with the dimensions I defined.
The collapsed page alreadycontains a Tap Area event to expand the ad and an expandedpage with a close tap area to collapse back down.
It also has added all theinitial code needed for the ad to talk to the ad server andcollect tracking metrics.
Those metrics are builtinto the components, and we can assign uniqueidentifiers to each component as we go.
So now I can start adding thegraphic elements I've already prepared.
I drag a backgroundimage or initial ad state and drop it onto the stage,then align it to the stage, and layer it behind the taparea by sending to back.
Now, let's switch toour expanded page.
Let's add a background imageby dragging my image file to the stage.
I can also add abutton to the stage by dragging theTap Area component.
Let's make a backgroundexit tap area.
I will size, align it, and thenI will give it a unique name.
To add functionalityto the button, I will add an event using theplus button in the event's toolbar.
This brings me tomy Actions panel, where we assignall of the metrics to our ad instead ofcoding them manually.
I'm going to selectthe tap area I just named BackgroundExit from the list.
Choose Tap Area, Touch/Click as the event.
Google Ad, Exit ad.
On the Receiver panel,I select gwd-ad.
Lastly, I give it an exitidentifier and a destination URL.
For more in-depth detailson the event model, check out the Eventsand Metrics video.
Next, let's add avideo component.
You drag it to the stage,then give it a name and size it properly.
Tell it how to behave.
I want it to autoplay and start muted.
And you target thevideo file here.
This component has allof the metrics built in, so you can avoid handcoding them in the ad.
Let's preview our ad.
On page load, we seeour collapsed state.
When we click, the adexpands to our expanded page.
Our video behavesas we told it to, and clicking on the backgroundexits to our landing page.
Once the ad is built andfunctioning as you want, it is ready to publish.
Go to File, Publish.
And you're presentedwith a few options-- Publish Locally,to Google Drive, and, finally, toStudio.
Let's choose Publish Locally.
This is where you cancontrol how the ad is output.
For instance, youcan add polite load to the ad, which delays thead load until after the page content loads.
You can also set itto minify the code and add browserprefixes automatically.
We'll leave all thesesettings as to the default.
Click Publish, and Web Designerwill wrap up all of your files in a nice little zipfor uploading to Studio.
Now, let's testit out in Studio.
Let's make a newcreative of expanding type.
Drag the zip file to uploadour creative to Studio.
Now, let's preview our creative.
As you can see, I can expandthe unit, play the video, and trigger thebackground exit we added.
You can see these eventslogging to the output console.
And that's an overviewof Studio integration features in Google Web Designer.
North Dighton website designers
Next, we can select the type of ad.
We want to make an expandable, so we select Expandable on the left.
Next, we can set again ad’s dimensions.
We are building a 320 by 50that expands to 480 by 250.
So I will make those changes.
We then assign the North Dighton creative a name.
I will leave my Save ToLocation as the default, and leave the talk about set to Quick.
Once I’m happy with my settings, I click OK.
Google Web Designer creates the initial pages of the ad for me with the dimensions I defined.
The collapsed page already contains a Tap Area event to expand the ad and an expanded pageNorth Dighton with a close tap area to collapse back down.
💸 How to budget for your web design project 💸 - Web Design is Broken e05
ADRIENNE PORTERFELT: You've probably tried to buy somethingonline or had to fill out some formfor your kid's school, and it's reallyhard on your phone.
It's really hard.
MUSTAFA: There seemsto be a dark art when it comes to nativeapplications, and they're such small details thatyou're actually working on.
[MUSIC PLAYING] Quite often, developers willjust throw on input fields onto a page and not reallythink about the UX that's attributed to that.
So they'll think ofa flow of a form, but they won't necessarilyfeel that individual input, so how a user struggles.
And we know thatautocomplete really helps speed up theuser experience and makes fillingforms quite nice.
What are your feelingsand experiences on autocomplete andAutofill as a thing? ADRIENNE PORTER FELT:From the user experience, you've probably triedto buy something online or had to fill out someform for your kid's school.
And it's reallyhard on your phone.
It's really hard.
It's even hard on desktop.
You don't want to get upand get your credit card out of your purse,which is downstairs.
And these browserfeatures just really improve the userexperience of using a form.
In fact, we find that peoplefill out or submit the form 30% faster if the formworks with Autofill.
So we very much suggest thatweb developers think about this.
You want people to besubmitting your forms.
Right? So if you really want yourforms to be submitted quickly, easily, work with Autofill.
MUSTAFA: And why do you thinkdevelopers don't do that? Is it very difficult to do? I'm assuming it's just a fewattributes you add to inputs.
Right? ADRIENNE PORTER FELT: Yeah.
It's actually not that hard.
So you basically need to setup autocomplete attributes, and you need to makesure that you're not doing any fancy things thatreplace the normal select and input elements withother types of elements.
I think most of these developersjust don't think about it, don't realize,that you just need to put a littlebit of extra effort in to make sure that yourform works well with Autofill and to test it out.
MUSTAFA: Is that oneof the challenges, I suppose, like people makingthese custom UI things, which are not native but justlike divs or whatever and replacing that? Is that where thingsfall down with Autofill? ADRIENNE PORTER FELT:Honestly, there's a few things that can go wrong,but that's one of the big ones.
Yeah, so someone wants thisreally beautiful custom form where the dropdown isall fancy and custom.
And as a result of that,they're using all divs.
And the browser can'tfigure out, oh, this is supposed to be a form.
And then in that case,Autofill isn't going to work.
MUSTAFA: And Isuppose there's a lot of accessibilityissues connected to that as well, it looks like.
But from your pointof view, you've got designers anddevelopers, they want to do something custom,like unique experience.
But then as someone whoworks on the browser, you want to say, now letthe browser do the work.
Do you think there'sa middle point there? How can developers at leasthave a custom experience that's unique to theirproduct, but at the same time without breaking standards? Because this is one of thebiggest challenges on the web.
ADRIENNE PORTER FELT:So there's a lot of things you can do tochange the look of the form on the page while stillusing the select and input elements that HTML provides.
Right? You can customizethem in many ways.
I have to admit, there is onething you can't customize, and it's the lookof the dropdown, like in a select element.
But everything else, the wayit statically looks on a page, you can customize.
And the browser will stillknow that they're fields.
What you see is thebiggest challenge then, for Autofillor implementation, from your point of view? ADRIENNE PORTER FELT:I think it's honestly that developers don't thinkabout it, that people don't think to themselves that theyreally need to be testing their forms in this way.
When you've made it yourself,you've filled it out 100 times.
You tested it yourself.
And you don't thinkabout the fact that a user is goingto be coming to it in a different state of mind.
They are tryingto fill it out as fast as they can on the phone.
So I think developersjust aren't really thinking about the factthat they need to take these extra small steps.
MUSTAFA: So in terms ofbrowser compatibility, the things you're using willbe Chrome-specific stuff? Or is that open source-- not open source, butit's cross-platform.
ADRIENNE PORTER FELT: Yeah,that's a good question.
So specifically autocompleteattributes for Autofill, that's standardized.
All the browsers respect them.
With that being said, thereis one part, turning Autofill off-- that's the autocompleteoff attribute-- is not respected by all browsers.
But if you say,this form should be a credit card, thatwill be respected by all the major browsers.
MUSTAFA: But eachexperience, is there slight quirks per browser? Because obviously, that's goingto be a browser-specific thing.
ADRIENNE PORTER FELT: Some are-- they have veryslightly different UIs.
For example, maybe they'llbe integrated with a keyboard widget versus a dropdown.
But I think they're prettysimilar across browsers.
MUSTAFA: You work on theactual Chrome UI itself.
ADRIENNE PORTER FELT: Yes.
MUSTAFA: So are you actuallybuilding that design and code yourself, or are youworking with UX designers in that process? ADRIENNE PORTER FELT: Sowe have a design team.
And the design team helpsus figure out what those UI elements should look like.
We actually have a bigredesign coming up this year that I think is going tomake those substantially more beautiful and also help clean upthe code, which I know that it won't affect most people becauseit won't look any different.
But from our perspective-- MUSTAFA: It's much cleaner.
ADRIENNE PORTER FELT: Man,the code's so much cleaner.
MUSTAFA: What's the actualprocess of you actually creating UI? Because for me, I do front-enddevelopment and code.
But it's like there seemsto be a dark art when it comes to native applications.
And they're such smalldetails that you're actually working on, which the user maynot notice because it works.
But if it's broken,they will see it.
What is the actualprocess that you go through with your Chromedesigners to actually making the UI or testing it? I'm asking lots ofquestions all at once.
ADRIENNE PORTERFELT: Yeah, it's OK.
So I'll talk about theprocess a little bit.
So usually at the beginning,Product, Eng, and the designer will get togetherand talk about what they hope for from the feature.
Often, the designwill then come up with some conceptualmocks of what they feel the feature could look like.
They'll get feedbackfrom Product.
They'll get feedback fromthe engineers, like can we actually build this, whatare the corner cases we need? And then we'lliteratively get closer to what we actually can ship.
So I work on across-platform team, which means that whatwe build has to ship on all of Chrome's platforms.
People think of Chromeas one platform.
But actually, it'sWindows and Mac-- which previouslyhad different UIs, but we're coming toone single standard-- Android, iOS.
And so we have to havedifferent mocks that relate to the specific platforms.
So some things may bepossible for some subset.
Anyway, the designers get allthis feedback from engineers, like, we can do thishere and not there.
And then we iterativelycome through to red lines, which isour final set of designs.
And that's what we implement.
MUSTAFA: So in termsof do the designers work with the actual W3C? Because you'redesigning something which has to beconsidered cross-platform at the same [? time.
?] So likewhen the payment request API, like I was working withsome of the team there, there seems to be thingswhere you have to really be seeing whateveryone else is doing so that the experiencethat you're creating is not so widely different.
And that can be quitechallenging for the designer and developer because youinstinctively want to make it, I don't know, "better.
" But you don't want to makeit so vastly different, because then you stick out.
ADRIENNE PORTER FELT: That'san interesting question.
The challenge here isthat with specs, we try not to specify whatthe UI has to look like.
We try to talk about what theuser experience should be so that we can have the appropriatecallbacks, et cetera, to build that experience.
But we don't like tostandardize the UI itself, which is a fine balance becauseyou have to have a UI in mind when you're designing the API.
But we try to make itas general as possible so that we can build differentUI experiences on top of it.
MUSTAFA: Are you workingwith the browsers as well at the sametime to do that, or is it you do things independently? Because there's the thing.
It's like if you do it[INAUDIBLE] the browsers, then you may be leddown a path that's not the best for everyone.
That it's, OK, it'slike a compromise.
But at the same time, you don'twant that complete disparity.
ADRIENNE PORTER FELT: Itdepends a lot on the standard, honestly.
Some of them willbe heavily driven by Chrome or some other browser.
They really want this API.
They'll drive it, and thenget a little bit of feedback along the way fromother vendors.
Whereas others,from the beginning, there's severaldifferent browser vendors working together.
So honestly, it differsfrom standard to standard.
MUSTAFA: And we're coming to the10-year anniversary of Chrome.
What do you thinkthe future of say, Autofill, or just workingwith the other browsers? Because it seems like thingsare getting much better.
I was speaking toDarren, and it was like, the implementationof Flexbox was a nightmare becausethe standard kept changing.
But with CSS grid, it'samazing that there's so much cross-collaborationbetween the browsers, which is great for the users and thedevelopers working across this.
What do you think the futureis for Chrome as a platform and, I suppose, Autofillas well as a specific? ADRIENNE PORTER FELT: Sofor Autofill specifically, it's hard to saybecause I don't think the limitation there reallyis the lack of browser vendors cooperating.
I feel like actually, there'sbeen a lot of discussion, for example, aroundpayment request.
There's a lot of collaborationbetween Safari and Chrome.
I think that thereal problem we have is that Autofill dependson developer adoption.
Right? If it's hard for thebrowser to figure out what form's in thepage, we're not going to be able to Autofill it.
And so I think thething we really care about is whetherwe can get developers interested in andusing the tools that we have provided for them totry to improve the Autofill experience.
Do you ever have toremove a feature when you see there's not wide adoption? Because I can seefrom an engineer, you're working on Chrome.
You spent your heart andsoul working on this feature.
And then you know it'sgreat for user experience.
You know from theresearch that Autofill will help transactions,and it's just nicer.
But if adoption doesn'thappen, how do you [INAUDIBLE]?? It's the biggest-- ADRIENNE PORTER FELT: Yeah,that's a really hard one.
I've been througha few deprecations.
They can be really challenging.
It's very hard.
So there are a few waysyou can look at it.
One is how many usersinteract with websites that are using such a feature.
And obviously, thatnumber is large, you don't want to create apain point for a lot of users.
But even if thenumber is very small, it might be that there are afew websites, a few companies, whose entire businessmodel depends on having access to this API.
And so that can make itvery difficult, where OK, even if it's thisreally a niche thing, it still can behard to deprecate.
So I think there have beenlots of ongoing discussions in general about howto make that trade-off.
Some of the onesI've been involved in relate specificallyto security and TLS, where if something is makingthe web as a whole as safe, we may have to breaksome connections in order to deprecate it.
And it can be areally painful thing when you've got old serverson the internet that aren't being upgraded.
And maybe it's only a smallpercentage of overall page loads, but it'sstill frustrating when a user is trying to getto a website and it's broken.
But ultimately, fromChrome's perspective, it's the user's experiencethat's paramount.
Right? ADRIENNE PORTER FELT: Yes.
MUSTAFA: And theirsafety and security.
So it's like HTTPS, you couldprobably explain it better, but there's a cutoff pointwhere if your site is not loaded on HTTPS, you're goingto get a message saying, this isn't secure.
Right? ADRIENNE PORTER FELT: Fora long time in Chrome, we showed HTTP as neutral, HTTPas just plain text and no TLS.
MUSTAFA: Sorry, what's TLS,just for my non-designer-- ADRIENNE PORTER FELT: Oh, TLSis the underlying protocol that makes HTTPS HTTPS.
It's why it's secure.
So there is HTTP,which doesn't have any of the end-to-endsecurity bits on it.
And HTTP websiteswere just shown as a neutral standard thing.
Right? Most websites on the web wereHTTP, but that's changed.
We went from a few yearsago, we were at 25% HTTPS.
And now, it's the opposite wherewe're at more like 75% HTTPS.
So made changes in theUI to back that up.
So now when you go to awebsite that says HTTP, it's going to also say"not secure" next to it so people reallyunderstand what that means.
MUSTAFA: That decision mustbe quite tough, though.
In some respects, you need toforce the developers to say users' security is paramount.
But at the sametime, does it feel like you're breaking the web? ADRIENNE PORTER FELT:It doesn't really feel like we'rebreaking the web.
First of all, Ithink people have seen this a long time coming.
We've been talking aboutit for a long time.
We've rolled it out in phases.
So first, we started showing"not secure" specifically for pages with passwordsand credit card form fields.
And then it was for allform fields and web pages when viewed in incognito.
And now we're rolling itout for all HTTP websites.
And as you can see, becauseHTTPS adoption has really increased, it's onlyimpacting less than a quarter of page loads at this point.
MUSTAFA: So really,we're just talking about protecting the user.
ADRIENNE PORTERFELT: Yeah, and I think users have a right to knowthat their information isn't secure when they'regoing to this website and help them make adecision about whether or not they want to keep using thatservice or go to another one.
MUSTAFA: And do youthink users are quite savvy now to see those things? Or is this part of theeducation for the user as well to say, look,there are certain things on the web which arenot secure that you have to take into consideration.
ADRIENNE PORTERFELT: I'll be honest.
We have literally billions ofactive users, so it's hard to-- MUSTAFA: Make ageneral [INAUDIBLE] ADRIENNE PORTERFELT: --say generally whether people are goingto understand it or not.
We think enoughpeople understand it that they have a reactionand that they can reach out to sites saying, hey, Ireally like this site, but I wish it were secure.
And we see people doing thatas we've been rolling out these warnings.
SPEAKER 1: The way thatcellular networks are set up is that there's alwaysthese fringe areas, and there's alwaysthese breakdowns.
And higher latencyis always there.
Designing for Mobile Apps: Overall Principles, Common Patterns, and Interface Guidelines
When I joined Google a little more than 2 years ago, I was asked by a few people to tell the story of how I got there and what my experience was.
I promised I would but I never actually did. Maybe I was shy, maybe I didn’t have the time or maybe I simply thought, probably wrongly, that it wasn’t interesting enough.
I decided to finally honor that promise and write about it.
I hope this is not too late and that it will be useful to some people.
I will try my best to sum up my experience and stories and provide a few advices from them.
Oh, one more thing. This is not a guide on how to get a job at Google. Based on my experience, I do not think such a thing exists. It will not describe the interview process in detail (such as the questions asked) nor disclose any confidential information.
The sole purpose of this article is to talk about my pre-Google personal experiences. I hope this will be useful for you, at least a little.
Baguettes and berets
If you don’t know me, I’m a 27 years old Frenchman born in a small city in Paris suburban area called Lagny. I spent the first 6 years of my life there and then moved to the south of France where I lived and studied in various cities such as Toulon, Hyères, Arles and Marseille.
Today, I’m a visual designer for Google Chrome and Chrome OS, living in San Francisco.
I got a High school diploma in what was called “social and economics”, then I studied 2 years in a general technology school and 3 additional years in a multimedia project management school.
What these schools and courses had in common is that they taught you a general approach on various subjects. It didn’t specialize you. Thinking back, I think I was taught how to become an effective swiss army knife.
I started by learning the basics of social science and economics mixed with history and philosophy. Add a bit of math to that and you get my High school diploma.
The following two years were all about introducing you to everything you can do with a computer, a screen and a camera. From code to design to filming and photography. Very broad subjects.
The last three years that led to my masters degree were multimedia management. It was all about managing people, project, public speaking and… wearing a suit.
Looking back at it, the more I was going through these school courses, the less I was learning the skills I use in my current everyday job.I learned at school what I didn’t want to do.
School is not about teaching, not really. It’s about opening your mind. I forgot most of what I learned at school but it helped me visualize and understand the things that I wanted to do and the things that I wanted to avoid.It’s by learning a subject that you realize it’s not for you.
I had to learn math to discover that I hated it, I had to learn to code to discover that my appeal to it wasn’t as strong as my appeal to align pixels.
I had to wear a suit to realize that this is not something that I would want to wear everyday. I learned how to manage projects and people to understand that what I really wanted to do is to spend my entire day in Photoshop, listening to Hans Zimmer and Amon Tobin.
Maybe it’s not the best path to follow to learn things, but it was mine. Don’t get me wrong, I learned a lot of useful things in these schools but somehow, it’s the things I hated to learn that gave me the most beneficial lessons and drove me to my key skills.In any given project, I always volunteered for the design part, it was my refuge. In response to possibilities of acquiring more knowledge, I specialized in one thing.
In the 5 years following my High school diploma, I dismissed a lot of potential knowledge to obsess over details in interfaces.
Is it a good thing ? I do not know. I’m not a fast learner. I found what I was good at and instead of searching to acquire a broader range of skills, I maximized the strong ones.
Let’s summarize who I was after my studies:
An obsessed interface designer focused on web and mobile design. I was comfortable and self-confident enough to present my ideas in front of people.
I had a daily schedule made of an hour and a half of web browsing to discover, save and categorize inspiration across the web followed by 8 hours of visual design in Photoshop and Illustrator. Also, I was fluent in English, and this was key.
My work history is tightly linked to my school history. My 3 years of multimedia management were alternate. I had to spend a month at school and the other in any company nice enough to welcome and form a newbie.
I was lucky enough to work for companies who made me do some actual work besides bringing coffee and I will always be grateful for that. Here is the biggest thing I learned and that I have absolutely no doubt about whatsoever:The best way to learn is to work for real people, in real companies.
The benefit from working and learning at the same time with people who actually make a living out of what you want to do is by orders of magnitude more beneficial than school. Any internship will teach you more about real life work than any class.
Now I’m not saying that you don’t learn anything at school. You need it to give you the basics, the by-the-book approach of design and tech but being able to apply learned principles and confront them to real situations and projects is priceless. Combining school and in-situ internship is for me the best pedagogical approach to learning a subject, at least in our field.
The first Year
During the first year of alternation, I learned print, logo and identity design. From an intern perspective, I did a decent job. From a professional designer standard, I was terrible. My work was messy and full of mistakes. Thankfully, it was ok, because I was with the right people.During your life, if you’re lucky enough, you will meet people who will help you grow. People who will help you reach what you think was too far, by standing on their shoulders.
This was the kind of person my boss was during this first year. We were a two people company, he had a ton of experience and was eager to share it. He was patient and when he detected the smallest amount of talent in me, he helped me expand it.
I wasn’t expecting that, it think it’s rare to meet somebody who needs to make a living and is still available to help you grow professionally and personally. I’m trying to carry on this lesson, but I’m not there yet.
It takes a lot of selflessness.
The second and third year
I spent the second and third year of my alternation in another company. I left my first year one because I needed to make a little bit more money, he couldn’t assume an intern anymore and I was ready to move on.
The company was a small web agency created by one person who was sick of being given orders and wanted to make cool things by and for himself.
Now let’s take a break here for a quick advice to any aspiring designer who wants to land any job/internship:Smile and engage.
As simple as that. At the time I was a shy guy with a bit of confidence issues when it came to selling myself. Saying that my presentation was underwhelming is an understatement. If I wasn’t supported by an employee of this same company, I think I would still be searching an internship right now. Hurray for networking and string pulling.
Ok, back on the subject. You remember what I wrote earlier about my first boss ? Well you can re-apply this here. Two in a row can be considered lucky, and it is. Luck is an important factor in your career but I will get back to that.
These two years improved my visual design skills at an incredibly fast rate.
I was working on a large range of projects from complex web-design to phone applications. It was a balance of internal and client projects. A good way to keep some freedom in your work while making a living. I even did a few email design for mass mailing which I’m not very proud of but teach you the realities of the field. This is also important:
Following the same logic as for school, doing something you do not like builds you and defines you as a designer.
This work was thankfully secondary. A large majority was incredibly interesting projects with a lot of challenges for a young designer. I grew exponentially with every work because I had freedom and responsibility. My boss was a safety net, a knowledgable guide that was there when I needed him. But he trusted me from the start, giving me enough responsibility to feel involved in everything I was doing.Be a safety net for the person you want to see evolve. Make him feel impactful and in control of his decisions and projects.
I finished my studies and was hired full time in this company. I stayed another year before being hired by Google and I loved every second of it.
In addition to school courses and learning with pros, learning by yourself will be a great asset in your career. Some may say that it is all you need, especially in our line of work.If you have the passion about something, self teaching should come naturally. If you have fun learning stuff, you are where you’re supposed to be.
My favorite way of learning was by looking at other people’s work and learn from the .psds they were sharing, that’s why I’m still doing that to this day. A way to return the favor.There will always be more talented people than you.
Look up to them and try to catch up.
Networking and design communities
Something you need to know: I hate networking. Actually I used to. I’m getting a little bit better at it but even today, I’m awkward. I have this weird expression on my face that makes people think I’m obnoxious sometimes. I don’t know, maybe I am a little bit. But I think it’s mostly shyness.
Anyway, I learned very early that networking is important to develop your career, especially in our field. Dennis Covent will probably explain why better than me in his blog post so I will not spend too much time on it.
That’s the beauty of internet, you can network without engaging anybody in the real world. You can build yourself as a designer and build your web presence simply by participating in communities. If you are alone on an island, you have virtually the same chance of being recognized for your work as anybody else.
Of course this is not entirely true, an outgoing person living in San Francisco will probably network easier than a brown bear living in a south France cave with poor internet connection but you know what I mean.
Thankfully, I wasn’t a bear, I had a decent internet connection and a need to share things. So I started a little blog using Tumblr.
It was simply about sharing things about design and writing various notes about it. Some sort of personal Pinterest. Very few readers but that was fine. I enjoyed it. Heres an important note about that:
So I continued writing my little blog and I was eventually contacted by a bigger french site focused on web-design and various source of inspiration for designers. My audience suddenly exploded, of course. This blog had way more visibility. I started shifting from sharing inspiration to creating my own design resources, or “freebies”, after discovering the work of Orman Clark and his work on Premium pixel. I was and still am a huge fan.
It was a great way for me to improve, satisfy my compulsion for pixels and gave me things to share. I also learned a lot from reverse engineering other designers freebies, it was my way to give back. I even started writing tutorials.
And then the owner of the blog asked me this question:
“Do you need an invite to Dribbble?”
This deserves a section of his own simply to make a point. Dribbble played a huge part in my career and I think this is the case for a lot of people.
I joined it the 6th of March 2011 and published this shot:
My first shot made me rapidly get followers. At the time I was publishing a freebie per week. It took a lot of time, I was pretty much doing nothing else during the week besides working and creating photoshop goodies to share and updating my blog. Doing this created a lot more opportunities than I ever thought it would. Suddenly, people contacted me for work, outside of France.
Oh and also, it’s where Google found me.
A little bit of freelance
Remember that at the time, I was working in the web agency. That’s during my full time year that I started receiving work inquiries from companies outside of France via Dribbble. The first one I received was from a print company based in Sweden. That was a big deal for me. I was speaking enough English to understand them, but we were talking about business here. I was fresh out of school and not that confident about handling my own projects.
So I proposed to my boss to make this request a company project. He would teach me the business part of it and I would handle the rest.
This is how I started my first “sort of freelance project”.
It went smoothly, they were satisfied by the result, I delivered in time and we built a pretty good relationship. This project added to my portfolio, I was more confident because I went out of my comfort zone and did it.Going out of your comfort zone will greatly improve your confidence.
I was continuing my constant flow of freebies on Dribbble and spending half of my day in photoshop, designing mock-ups after mock-ups for sites, mail, iPhone apps and iPad apps. I was designing everything I could from video players to upload panels (why?! I’m not sure). I was getting more followers and more work inquiries.
I accepted projects from France, Denmark, and the United states. Each one opening new design horizons. From social platform to DJ-ing software.
As the inquiries got more numerous, I learned to choose the projects I wanted to work on, taking them both for the companies and starting a few projects on my own. Usually, everything went well for a simple reason: I got all my inquiries via Dribbble from clients who knew what they wanted and knew what to expect from me based on my previous work. Being able to choose your client is a luxury. I was able to do that because I had a full time job.If you have the time and if your situation allows it, taking side projects as a freelancer while you have a full time job is a good way to try it out and see if it’s something for you. Be careful though because you will not see the sunlight a lot.
Getting all these clients also helped me to do one important thing, build up a portfolio. Which brings me to this.
Working for free
Before anything else I suggest you read this article by Dann Petty.
I know this is a delicate subject. Every work deserves payment. There are a lot of people that will take this opportunity to exploit young designers and I received my share of “I need a design for a youtube-like site, $200 should be enough.” or “there is 5 other designers working on this, I will pay the one I pick”.Working for free is all about building your portfolio.
Now, you will only be able to do that if you actually manage to pay for your internet bill first of course. One benefit to it is that you will choose the project you want. You will work on what makes you happy and what you will be happy to show as a work reference. If you work with the right persons, it will open doors for you.
That’s why I accepted a lot of requests with no money involved, any student party that needed a poster, every little website design with very low budget because I knew the guy, this kind of thing.
Do it when you are a student, when you’re eager to do over hours and work on various stuff. Yes they will get something for really cheap or even nothing, but as a young designer you will get invaluable experience, you just need to be careful.
As for being able to pick your clients, working for free is a luxury, it is not for everybody. I was able to do it because I had a supporting boss, family and a full time job. If you can to, consider it but do it for the right people.
“Want to chat ?”
The year went by and I received my first recruitment email from a company in Spain. That was weird. For the first time somebody wanted me to work for him, in a big structure, out of my country. He wanted to know if I would consider “a chat”, and they would bring me to their headquarters for it.
I actually told my boss about it what he told me was: “go for it!”. Remember what I wrote earlier about the kind of people that will help you grow?
So I went for it and accepted to go there just to chat. Why not after all? I wasn’t that in love with the city I was living in, I loved my job for sure but I saw an opportunity to grow.If you see an opportunity, if you have the slightest doubt or “what if” in your mind, just go for it.
They paid for the plane ticket and the hotel just to talk to me. I know, now it sounds completely normal to some people but that was crazy for me in a world where I heard clients not willing to pay more than a few hundred bucks for a website design… when they were actually willing to pay anything.
So I did the interviews and got to know them a little better. Things were clicking and I was starting to consider the fact that I could move from France to Spain. It wasn’t that far after all and these people were pretty awesome. But a week after being back home I received another email.
I think this is spam
This email was from Google as you probably guessed. I really thought it was spam. It was completely out of the blue.
I answered… you know… just in case.
At the time it was during a US holiday so it took five days to receive an answer, reinforcing my spam theory in the meantime.
Turned out it was real and I couldn’t wait to know more.
After checking a few things like my willingness to move to the US in case this ever works, the recruiter told me that I was going to enter the process, starting with a call from a Googler.
At this moment I thanked the thousand of hours spent listening to various American TV series while working at home. Otherwise I would have struggled to understand anything during our conversation. It was still hard though, it is way different to passively learn a language than it is to have an actual human interaction, and my brief 2 weeks school trip in the US when I was fourteen didn’t really help.
I thought I did terribly on the phone but apparently not as they were willing to continue the process. The next step was a design exercise.
This part was very stimulating for me. I had the opportunity to demonstrate how I think and deliver polished visuals. It really wasn’t that different from what I experienced several times with clients, maybe the result was a bit more life changing…
So I sent the finalized exercise crossing my fingers hoping to get a positive answer and avoiding imagining them laughing at my work.
Around two weeks later, they told me they wanted to see me in person, in Mountain View.
What am I doing here ?
At the time I had a two weeks trip in New York with a friend planned 4 month earlier. Some sort of “we’re done with school” trip because we wanted to discover New York and the US.
The confirmation email came during this time. I was stopping twice a day at a Starbuck to get some Wifi and check emails. I mentioned I was in New York and that it would be a good idea to meet during these two weeks, you know, to avoid crossing the atlantic and come back again.
They agreed, set up my flight, two days later I was flying somewhere I’ve never been before, California.
I landed in San Francisco and before realizing what was happening I was driving a rental car on a highway that was going to become the one of my daily commute. The “What am I doing here” moment was when I realized I was driving for the first time on a Californian road, passing signs with cities like San Francisco, Palo Alto and Cupertino written on them. Big deal for me.
The next day were the on-site interviews. It went really fast and was over before I could realize it. One thing I do remember is that, between two interviews, I was asked when I considered joining Google. I answered that I never considered it and that I never imagined being here, it was just not a realistic possibility for me.
Retrospectively, this was a probably a weird if not bad answer but it was the simple truth. I was too tired and disoriented to start thinking about what could be a good answer.
Thinking about it, maybe it was what to do. It sounds cheesy but I think this applies to a lot of situations and to any job applications. You may talk your way into landing a job by finding the right answer at the right moment but you would be at risk of not finding the right thing in the end, something that is neither for you or your employer.
This time I didn’t forget to smile though.
And that was the end of it, I just had to wait for the final decision. I jumped in the plane back to New York, looking to San Francisco by the window, a city I would never enter until I discovered it for the first time, searching for a place to live.
If you want more information about the Google hiring process,
head this way. You will find some useful details on that.
I received the call on a Friday. I was asked if I was interested in joining Chrome. This couldn’t have been better. I didn’t hesitate a second and gave a positive answer. The web made me and now I was going to help make it better.My Dribbble announcement post.
One thing you may say if entering Google is one of your objectives is that I got really lucky. I was lucky to have the studies that helped me figure out what I wanted to do, lucky that I got two great bosses in a row, lucky that I got a Dribbble invite at the right time with a Googler looking at my work at the right moment, lucky that I was already in the US when they wanted to see me, lucky that there was still some visas available when I applied, and you would be completely right.
Luck played a huge part in this and I wouldn’t be writing this if it wasn’t for it. One addendum though:Be prepared for luck, if it ever happens, make sure you can take your chances.
Reading this article myself, it sounds like I described some sort of magical story made of rainbows and ponies and that I am a huge fanboy writing an advertisement. You may also not agree with what Google is doing, although reading this to the end would seem like a huge waste of your time. This is only my view of it.
I tried to stay true to what I felt at the time and how things worked out.
I feel grateful to be where I am surrounded by people way more clever than me. Is it awesome every day ? No. It can be frustrating and you may not agree with everything. You are part of a gigantic machine that makes things at an unimaginable scale. That’s also part of the thrill.
Will I be there forever ? I do not know, I had my ups and downs but I do love Chrome, Chrome OS, my team and Google.
For now, I’m not going anywhere.
I think it’s an extraordinary experience simply to be here, not just at Google but in the bay area. I’m trying to remind myself that when I tend to act like a spoiled kid. Deep-down, I’m still waiting for them to realize that I’m a fraud and put me on the first plane back to France.
Get in touch
I didn’t cover everything, it was a long story.
If you have any questions or just want to chat or connect, here is some shameless social network self-advertisement:
LYNN MERCIER: Thetruth is, like, if we want to evolve thematerial design system, we need to be able tobuild on top of the code, and each layer ofthat code matters.
MUSTAFA KURTULDU:The conveyor belt is-- designer works onsomething, developer takes it, and developer screams becausethere was no conversation.
I think that's one ofthe biggest challenges.
[MUSIC PLAYING] One of the challenges inthe beginning with material on the web was there's so manydifferent implementations.
Again, the singlesource of of truth, so you had Angular material,you had Polymer, you had MDL.
How have you found solvingthat single source of truth? LYNN MERCIER: Yeah.
Originally we had a unique teamof developers in both Android-- I'm sorry-- Angular,and Polymer, and all these otherweb frameworks sort of building their ownimplementations in material design.
But we found that we couldn'tkeep that going at scale.
Like, we were iterating onthe material design system so quickly, and we couldn'tkeep a single source of truth with these othercomponent libraries.
It's not a perfect solution.
We're still working onmaking it faster and better, but we've foundthat that creates these sort of componentsthat look like they belong in the framework.
So any framework developerwho's working there, they look seamlesslylike they're a part of the environment.
MUSTAFA KURTULDU: The onething that we struggled with with MaterialDesign Lite was there was a lot of blackmagic going on in the DOM.
So you check DeveloperTools, and there'll be, like, these random elements.
And that was, like, anopinionated decision so, you know, how do you go aboutdeveloping a new framework where you have to have anopinion-- there has to be, like, this is the baselineof what we're doing-- without impeding on, like, whatthe developer just wants to do? They just want this componentto work, or this widget, or whatever.
LYNN MERCIER: Yeah.
I try as much as possibleto avoid black magic.
And, like, whenever I'mreviewing any code that any of the designers on myteam are writing, we, like, try and avoid anything that's-- maybe it's a little hack,and it makes it slightly more performant-- butthe truth is, like, if we want to evolve thematerial design system, we need to be able tobuild on top of the code, and each layer ofthat code matters.
So we try and, like, steeraway from any black magic and just have thisone source of truth that works with all thecomponent libraries as much as possible.
MUSTAFA KURTULDU:In terms of, like, working withexisting frameworks, what's the relationship there? Because, like, React isa thing-- you have to-- it's the real world, right? LYNN MERCIER: Mm-hmm.
MUSTAFA KURTULDU: Or likeWordPress is a thing.
Like, you have towork in that world.
LYNN MERCIER: Mm-hmm.
MUSTAFA KURTULDU: So theremay be certain things that you can or can'tdo as a result of that.
LYNN MERCIER: Yeah.
MUSTAFA KURTULDU: Like, formaintaining a framework where-- it's not Android.
It's not, like, a single-- LYNN MERCIER: Yeah.
MUSTAFA KURTULDU:--you have-- it's, like, the web is allabout relationships between different code bits.
I mean, how do you manage that? LYNN MERCIER: It gets reallytricky and really funny.
So we tend to prioritizethem in terms of what developers are already using.
So React is a great example.
There are a ton of codebases already in React-- it's super-popular.
So we want to prioritizethat one first, which is why we're making anMDC React library for React in particular.
But then there'sother libraries, like Angular andlike Polymer that we want to start using as well.
But we tend toprioritize them, again, based off whether or notdevelopers are already using them.
In terms of, like, keepingall that functioning-- and sometimes you endup, like, one framework wants it to do it oneway and another framework wants it to do another way.
It's just constantlycompromising.
Like, we work with thesedevelopers on the Polymer team, or we, like, talk tothe React community and try and figure out what'sthe right way to figure it out.
And we just sort of settleon the right compromise and stay there.
We do it as well with browsers.
So for example, we tendto develop first on Chrome because it's kind of thebest, and it works nice, but we have to support Safari,and Firefox, and Edge as well.
So we tend to testIE at the very end.
And we want it towork, but there's sort of, like, gracefuldegradation sort of things that happen.
As long as that happens, like,carefully and gracefully, then it tends to be OK.
And I think we do the samesort of thing with platforms.
You know, maybe itdoesn't perfectly work in everyplatform but as long as we can kind ofgracefully degrade that component in thatsituation, it'll work out.
MUSTAFA KURTULDU: Yeah, Iknow the BBC have, like, a term that's calledcutting the mustard.
So basically, they willhave, like, a baseline where things have to work.
LYNN MERCIER: Yeah.
MUSTAFA KURTULDU: Like, withthis, and if it doesn't work, or it doesn't supportthis technology, they're gonna say--you know what, you're not going to getthese experiences that we're designing.
I mean it-- how would youfeel about that as a concept? LYNN MERCIER: Yeah, we'vehad to use that already.
So there's newthings coming out-- material designed around shape.
And on the web platform,no matter what technology you're in-- like, what webplatform or what browser you're in-- rounded corners are really easy.
Like, cut-off corners? Impossible.
Just straight up impossiblewith the existing technology.
And so we kind of had to goback to our material design team and say, like-- look, we can update theCSS spec today in 2018, and then three years fromnow, our children's children will, like, have thisfeature, but we're not going to be able toimplement it right now.
So there are some featureswhere you just kind of have to draw the line and say,we can't do this feature without it beinga confusing story, without it being some sortof hack that no one would be able to use.
MUSTAFA KURTULDU:So how about SVG? I mean, I suppose whenit comes to animation, the challenge of SVG isthe performance 'cause-- LYNN MERCIER: SVGs, and thenthe shadows on top of them, and the scroll performanceunderneath those SVGs-- by the time you, like, transportall the browsers and all the situations wherethat component would be, it gets reallyconfusing quickly.
MUSTAFA KURTULDU:And very complicated.
LYNN MERCIER: Yeah,very complicated.
MUSTAFA KURTULDU: That'squite interesting, because the conveyor belt isdesigner works on something, developer takes it, anddeveloper screams because there was no conversation.
I think that's one of thebiggest challenges developers face because, ifyou just talk to me, then I'll be able to explain,especially for designers who have no coding experience.
And I know we've spokenbefore, and you've mentioned stress testingthe design, which is a new concept for me.
LYNN MERCIER: It's my concept.
MUSTAFA KURTULDU: How doesthat work, where you're stress testing the design? LYNN MERCIER: Imean, I think there's a limitation inDesigner Tools that make them want to forceeverything to sort of this pixel-perfect mock.
And it's gorgeous-- itcreates some gorgeous assets, but it doesn't always workin a real-world application.
And a developer'sjob is to create something that works in areal-world application, right? Ours is the stuff-- thecode that's running live.
And so many problems come froma design being pixel-perfect for one language, one screenwidth, one set of content.
And when you goto build that, you can build sort of adummy site quickly, but once you start populatingit with real content, all these problems come up.
And I think most designers,if you go and talk to them and say, like-- hey,I have this problem.
They'll help you.
They'll, like, show youhow to change the design and tweak it in this situation.
Like, they're very receptiveto that feedback-- they want to make their designs better.
But if you don't knowwho your designer is when you have thisproblem, then you just have this bug that says-- doesn't work in German.
Like, what do you do? You have no idea how to fix it.
So yeah, I think this conveyorbelt problem of designers who sort of, like,design something but then leave the projectand don't collaborate with the developers asthey're building it, it makes it reallydifficult for the developers to make the productbetter over time.
MUSTAFA KURTULDU: So how do youthink designers can actually improve their process to makethat relationship better? Or more, is it reallydown to the most obvious? You just need to pairprogram, or pair together.
You have to talk to the person.
That's really the bestway to do it, so like-- LYNN MERCIER: Thatis the best way.
I mean, I think that can bereally difficult in certain-- if you don't have enoughtime and resources, sort of dedicate, like, one person,one designer, and one developer to every single feature.
I think there's waysin the middle to do it.
So for one, make sure thatyou know each other's names.
Like, if you'reremote, make sure you know how to deployyour code somewhere to staging so yourdesigner can work with it, and make sure your designerhas a way to send you, like, iterations on mocks.
Another sort of quick andobvious thing, I think, for designers is tointernationalize.
The moment you take allthe text from your mock, put it in Google Translate,put it back in the mock, and see what looks horrible-- MUSTAFA KURTULDU: German.
LYNN MERCIER: --like, yeah! German! Or even, like, CJK languages.
Just pick a language.
It doesn't matter ifyou translate it right.
Just, like, do thatfirst step because you're going to run into all thewidth and height problems that a developerwill run into live.
And I think it's goodfor designers, right? It helps you makeyour product better to get feedback aboutwhat sort of languages do I need to support.
MUSTAFA KURTULDU:And it's especially important inuser-generated apps where the content could be 10 pages,or it could be two lines.
LYNN MERCIER: Yeah! MUSTAFA KURTULDU:It's not like-- you always get the mock wherethere's, like, the name-- LYNN MERCIER: Yeah! MUSTAFA KURTULDU: --theavatar name's perfect.
LYNN MERCIER: Fits perfectly.
MUSTAFA KURTULDU: Yeah, butwhat if the name's like, you know, four words long? LYNN MERCIER: Yeah.
MUSTAFA KURTULDU: Isthere anything else that they can do like the stresstest that wasn't just really-- LYNN MERCIER:Internationalization is a big one.
I think different screen widths,at least in your own web, is helpful as well,like making sure that the obviousbreakpoints work but also sort of smallerones or bigger ones.
But, yeah, it justcomes back to, like, be there when your developerruns into a real problem and help them fix that problem.
I think most developerswant to fix problems.
They want to code that out.
They just want to geton their headphones-- like, get the code outthat will fix the problem, but they don't know how toredesign the site, right? We're not going to-- ifyou make a developer guess how to design a site, we'regoing to guess really poorly.
So you need to helpus as designers.
SPEAKER: If you spentloads of time polishing your, like, amazingprototype, then you suddenly becomevery, like, you know, reticent to throw it away.
Kind of like it'syour baby, you're going to polish this too much.
And so that's dangerous,because then you're not using prototyping forprototyping's real purpose, which is to learn.