Newton Upper Falls web agency
Hello and welcome to this web agency Web Designer Newton Upper Falls 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.
Material Design Components for web - Designer vs. Developer #22
As part of Intuit’s core initiatives to further cultivate mobile first thinking and accelerate growth into global markets, the Intuit Small Business Group’s Design Org has shifted from a model of designing and shipping prioritized features to a model where every designer is responsible for end-to-end, cross-device experiences, which includes designing for our products and services on desktop web, mobile web, desktop client apps, and native mobile apps.
As a design lead for our ecosystem of native mobile products over the past few years, I started getting a lot of questions around guidance and principles for mobile design. I noticed many of the designers, product managers, and engineers who are new to mobile app design or don’t live and breathe mobile app development on an everyday basis didn’t fully understand the nature of designing for native platforms and device capabilities. To reinforce the notion that “cross-device” and “mobile first” isn’t just about designing for smaller screens and scaling across multiple device sizes, I collaborated with the Design Systems Team to establish a set of mobile patterns and guidelines so that designers can hit the ground running, or run even faster, with mobile design. We recently published some guidelines, tools, and resources on our internal design toolkit that I thought would be great to share some key points and takeaways with a wider audience as the documentation addresses many frequently asked questions around mobile patterns.
Firstly, I want to start off by saying that what I write here is simply for guidance. Our mantra for any kind of pattern guidelines documentation we provide is, “Give me guidance, but let me drive.” We don’t want to be prescriptive, and we don’t want to tell you how to design, but this is a good starting point to get you going on native mobile designs. Why are we calling out native mobile? As we continue to design device-agnostic, end-to-end experiences and features for products and services, we must remember not to neglect the different platforms (i.e. our mobile products are currently offered on both iOS and Android).
1. Respect the platform
We documented patterns and components based on native operating systems that we have apps on: iOS and Android. When designing for native platforms, you should consistently refer to the native OS design guidelines first for maximum quality. Keep in mind that native platform guidelines constantly evolve, so it’s always good practice to stay on top of these guidelines and refresh your memory and knowledge often.
Apple’s Human Interface Guidelines: https://developer.apple.com/ios/human-interface-guidelines/
Google’s Material Design Guidelines: https://material.io/guidelines/
2. Focus on the customer benefit
Always design for the customer benefit first. No use case is the same, and many use cases have exceptions. Do not design something simply because you can reuse a pattern or component for another feature. Design patterns help ground us as a system and unify an experience across an ecosystem of products, but they should by no means be the first or last stop in the design process. Always question yourself: How will this benefit the customer?
3. Think device first
Push your thinking beyond “mobile first.” Start thinking about leveraging device capabilities first. The native mobile device has a lot to offer: touch, voice, pressure, location tracking, accelerometer, notifications, etc. You are designing around the device, the platform, the user experience. How can these device features be utilized in our products? How can the mobile device benefit users beyond the screen interface in front of them?
4. Keep scalability in mind
Growing from the previous principle, do remember that a mobile device isn’t just a phone. Scalability across devices, more specifically between a phone and tablet, is a common challenge among designers. When we think of mobile devices, we know there are tablets, phones, phablets (not small enough to be a phone, not big enough to be a tablet). Some of the recurring questions I get asked are: Should there be parity between web and tablet designs? Can we translate the phone patterns to be the same on tablets? How do we design for phablets (not small enough to be a phone, not big enough to be a tablet)? To answer these questions, we researched with users, took an in-depth look at device interfaces and screen sizes, and set some standards. While the phone and tablet share many similarities, users use them very differently.
Mobile interfaces LESS THAN 7 inches width should be treated as a phone. Syntax and layout should be aligned across these devices as much as possible, but we also want to leverage native platform guidelines and capabilities first and foremost.
A fundamental design principle for mobile phones is to include only necessary information. Do not overload the user with more than they need to know or take action on. The phone is a convenient way to consume information on the go. Small business owners use a phone to complete quick actions while they are not in the office, capture data, view content, then perhaps close it out and come back to take a look later.
Mobile interfaces GREATER THAN 7 inches width should be treated as a tablet. Syntax and layout should be aligned across these devices as much as possible, and by no means should they need to align exactly the same as the less than 7-inch interfaces.
Tablet designs should look and feel like desktop web, but they should function like the phone (with tap/swipe/hold gestures, transitions, etc.). Many users view the tablet as a hybrid device. We’ve encountered many small business owners that don’t own a computer, but they own a tablet, and those users treat the tablet as a reliable device they can do work on.
To scale for the future or additional digital interfaces, you should also think about non-mobile touchscreens like TV displays, interactive table displays, automobile displays, laptop displays that you can touch, etc. You want to make sure you can scale for multiple screen sizes, large and small, and not limit yourself to thinking only about the devices your products are being supported by.
Patterns and Guidelines
This list is a small subset of patterns and guidelines that I’ve found designers have been commonly asking around best practices for our mobile products.
One of the major aspects that make navigating content on native mobile platforms so delightful is the transitions between screens. Two questions I get asked a lot are: When should a push (screen pushed in leftward from the right) be used? When should a modal (screen pushed upward from the bottom) be used? We’ve established the following best practices:
A push is essentially the fundamental screen transition to view a new screen that is stacked on top of the previous screen. There is typically a Back button so user can view the last viewed screen. For screens that are primarily for viewing, such as transaction detail screens or lists, we use a push.
A modal is typically used when we are requiring the user to select, edit content, or input data. All of our transaction forms use full screen modals as it requires more user thought due to several form fields on one screen. The titles bars for these screens typically have Cancel and Save or Cancel and Done actions. Then, when you tap Save, you get a push screen because you are viewing (not editing) the saved content.
Call to Actions
This section highlights a question I often get: “Should this call to action be a button or a text link?” In both iOS’ and Android’s design guidelines, text as buttons is the norm and recommendation. However, I feel when we use text, especially with a system font against a dark or light background, we lose out on a major opportunity to incorporate brand elements, such as our ecosystem green color or line iconography. So, we’ve deliberately moved away from using text as call to actions, and instead use buttons with high contrast, which also makes it very clear that it is a call to action and not just part of the screen content.
Our empty state screens provides a first impression to users who are new to our products. It usually consists of an illustration, a brief description, and a clear call to action. A common and current design trend is the usage of gray text on a light background. If you decide to follow that trend, make sure the text is readable and accessible by analyzing the foreground and background colors to meet the WCAG 2.0 color contrast ratio requirements.
Firstly, yes, it’s spelled caret, not carat or carrot. 🙂 Carets are used to promote discoverability. Historically, we try to use carets for every instance we want to indicate that the user should tap into the row to view more. However, in our forms, we are working toward to moving away from using carets and instead utilize the extra real estate by creating visual cues and conversational content design to indicate tap targets to view more. After some user testing with different design treatments, we’ve found that discoverability isn’t as much of an issue as we thought. Users will naturally tap on rows, whether there’s more information provided to them or not. We only want to use carets when absolutely necessary.
General rule of thumb for native mobile design: Use action sheets whenever there are multiple actions associated with a single call to action (that is not a system blocker). Apple iOS guidelines calls these action sheets. Google Android calls these bottom sheets. Use action sheets/bottom sheets whenever there are multiple actions associated with a single call to action.
Cards or Tiles
A card (or tile as other teams may call it) is a component acting as a rectangular container for a certain amount of information: visual elements, instructional text, diagrams, and action triggers. There are two types of cards based on appearance and usage: action card and info card.
We use native system dialogs for critical alerts, permissions related alerts, system blocker alerts, etc. The key word is “alert.” Note that for actions that aren’t related to these things, we try to use action sheets.
The general rule for native mobile design is to use system fonts as much as possible. However, we needed to incorporate our brand and voice and tone to create what we call “QuickBooks Ownable Moments.” For large headlines and sub-headlines, we use our brand fonts. For body text, we use system fonts. For fonts within buttons, we use system fonts.
Toggle switches are used to trigger a binary operation (i.e. turning something on and off). It is used often to replace a web checkbox metaphor. We have a lot of checkboxes in our web products so when we design for native mobile, we want to make sure we are only looking to replace binary checkboxes that allows for things like enabling or disabling content, show/hide content or fields, turn on/off tax, track returns for customers, instead of checkboxes used for selecting multiple items.
Again, these are just a few guidelines to get you started or to accelerate your mobile first design process, especially for native mobile. You are the driver and designer with creative license to define the end-to-end user experience for your products and services. Trust your gut, follow your instincts, but always remember to respect the platforms, focus on the customer benefit, think device first, and keep scalability in mind!
Yvonne So is a Principal UX Designer @Intuit currently crafting meaningful experiences for small businesses around the world. With a passion and mission for making technology more inclusive of everyone, she regularly speaks and writes about mobile UX, accessibility, innovation, and empathic design.
Newton Upper Falls web agency
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 Newton Upper Falls 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 pageNewton Upper Falls with a close tap area to collapse back down.
Latest Dental Implants To Be Used
This reading list is for anyone who wants to learn or deepen their knowledge in the disciplines of User Research, Usability, Information Architecture, User-Interface Design, Interaction Design, Content Strategy or Experience Strategy.
The list is broad and includes books that exemplify design thinking, processes, methods, principles and best practices. Some of the books on this list are over 20 years old, yet still relevant more than ever.
There’s not a day where I don’t find myself applying the ideas from these books. Each has helped shaped the designer I am today, helped me advance my craft. I hope that you too, can extract the same value.
Last updated 09/10/2017
My Top Ten
- The Design of Everyday Things, Donald Norman
- About Face: The Essentials of Interaction Design, Alan Cooper
- The Elements of User Experience: User-Centered Design for the Web and Beyond, Jesse James Garrett
- The User Experience Team of One: A Research and Design Survival Guide, Leah Buley
- Manage Your Day-to-Day: Build Your Routine, Find Your Focus, and Sharpen Your Creative Mind, Jocelyn K. Glei, 99u
- A Practical Guide to Information Architecture, Donna Spencer
- Designing Together: The collaboration and conflict management handbook for creative professionals, Dan M. Brown
- Seductive Interaction Design: Creating Playful, Fun, and Effective User Experiences, Stephen Anderson
- 100 Things Every Designer Needs to Know About People, Susan Weinschenk
- Lean UX: Applying Lean Principles to Improve User Experience, Jeff Gothelf and Josh Seiden
More Must-Reads On Thinking, Methods, Principles and Best Practices
I find it helpful to choose what to read based on what’s relevant at the time. Applying what you’re reading, as you’re thinking and making is a great way to solidify concepts, reflect and learn.
Some old, some new. All important reading, in no particular order.
Last updated 09/10/2017
- The Shape of Design, Frank Chimero
- Mental Models: Aligning Design Strategy with Human Behavior, Indi Young
- Practical Empathy: For Collaboration and Creativity in Your Work, Indi Young
- Interviewing Users: How to Uncover Compelling Insights, Steve Portigal
- Designing Web Interfaces: Principles and Patterns for Rich Interactions, Bill Scott, Theresa Neil
- The Laws of Simplicity (Simplicity: Design, Technology, Business, Life), John Maeda
- Information Architecture for the World Wide Web: Designing for the Web and Beyond, Peter Morville, Louis Rosenfeld, Jorge Arango
- Sketching User Experiences: The Workbook, Saul Greenberg, Sheelagh Carpendale , Nicolai Marquardt, Bill Buxton
- Well Designed: How to Use Empathy to Create Products People Love, Jon Kolko
- Thoughts on Interaction Design, Jon Kolko
- Linchpin: Are You Indispensable?, Seth Godin
- Don’t Make Me Think AND Rocket Surgery Made Easy, Steve Krug
- Designing Interfaces, Jennifer Tidwell
- Handbook of Usability Testing: How to Plan, Design, and Conduct Effective Tests, Jeffrey Rubin, Dana Chisnell
- Designing Interactions, Bill Moggridge
- The Visual Display of Quantitative Information AND Envisioning Information, Edward R. Tufte
- A Project Guide to UX Design: For user experience designers in the field or in the making, Russ Unger & Carolyn Chandler
- Gamestorming: A Playbook for Innovators, Rulebreakers, and Changemakers, Dave Gray, Sunni Brown, James Macanufo
- The Mobile Frontier: A Guide for Designing Mobile Experiences, Rachel Hinman
- Design Is the Problem: The Future of Design Must be Sustainable, Nathan Shedroff
- Prototyping: A Practitioner’s Guide, Todd Zaki Warfel
- Making Meaning: How Successful Businesses Deliver Meaningful Customer Experiences, Steve Diller, Nathan Shedroff, Darrel Rhea
- Content Strategy for the Web, by Kristina Halvorson, Melissa Rach
- Just Enough Research, Erika Hall
- Design Is A Job, Mike Monteiro
- Designing for Emotion, Aaron Walter
- Creative Workshop: 80 Challenges to Sharpen Your Design Skills, David Sherwin
- Letting Go of The Words: Writing Web Content that Works, Janice (Ginny) Redish
- Designing the Obvious: A Common Sense Approach to Web Application Design, Robert Hoekman Jr
- Designing the Moment: Web Interface Design Concepts in Action, Robert Hoekman Jr
- Designing for the Social Web, Joshua Porter
- Undercover User Experience Design, Cennydd Bowles, James Box
- Product Design for the Web: Principles of Designing and Releasing Web Products, Randy Hunt
- Designing the User Interface: Strategies for Effective Human-Computer Interaction, by Ben Shneiderman, Catherine Plaisant, Maxine Cohen, Steven Jacobs
- This is Service Design Thinking: Basics, Tools, Cases, Marc Stickdorn, Jakob Schneider
- Resonate: Present Visual Stories That Transform Audiences, Nancy Duarte
- Metaskills: 5 Talents for the Robotic Age, Marty Neumeier
- The Brand Gap: How to Bridge the Distance Between Business Strategy and Design, Marty Neumeier
- Getting Real AND Rework, 37 Signals, Jason Fried, David Heinemeier Hansson
- The Humane Interface: New Directions for Designing Interactive Systems, Jef Raskin
- Simple and Usable Web, Mobile, and Interaction Design, Giles Colborne
- Search Patterns: Design for Discovery, Peter Morville, Jeffery Callender
- Emotional Design: Why We Love (or Hate) Everyday Things, Don Norman
- Neuro Web Design: What Makes Them Click? Susan Weinschenk
- Designing for the Digital Age: How to Create Human-Centered Products and Services, Kim Goodwin
- A Web For Everyone, Sarah Horton, Whitney Quesenbery
- How to Make Sense of Any Mess, Abby Covert
- Radical Focus: Achieving Your Most Important Goals with Objectives and Key Results, Christina Wodtke
- Org Design for Design Orgs: Building and Managing In-House Design Teams, Peter Merholz, Kristin Skinner
- Communicating Design: Developing Web Site Documentation for Design and Planning, Dan M. Brown
- Subject To Change: Creating Great Products & Services for an Uncertain World, Peter Merholz, Todd Wilkens, Brandon Schauer, David Verba
- Hooked: How to Build Habit-Forming Products, Nir Eyal
- The 46 Rules of Genius: An Innovator’s Guide to Creativity, Marty Neumeier
- Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, Braden Kowitz, Jake Knapp, and John Zeratsky
- Designing with Data: Improving the User Experience with A/B Testing, Rochelle King, Elizabeth F Churchill, Caitlin Tan
- Banish Your Inner Critic: Silence the Voice of Self-Doubt to Unleash Your Creativity and Do Your Best Work, Denise Jacobs
- Design for Real Life, Eric Meyer & Sara Wachter-Boettcher
- Designing Interface Animation: Meaningful Motion for User Experience, Val Head
- Practical Design Discovery, Dan Brown
- On Web Typography, By Jason Santa Maria
- Designing Voice User Interfaces: Principles of Conversational Experiences, Cathy Pearl
- Thinking in Systems: A Primer, Donella H. Meadows
- Creative Confidence: Unleashing the Creative Potential Within Us All, Tom Kelley, David Kelley
More Useful Reading
Reading books is only a partial source of my inspiration and learning. I also frequently read blogs and articles. I highly recommend staying connected to these sources of great thought leadership:
- Eleganthack, Christina Wodtke
- Peter Merholz
- The Year of the Looking Glass, Julie Zhuo
- Bokardo, Joshua Porter
- Information Architects, Oliver Reichenstein
- Felt Presence, Ryan Singer
- Whitney Hess
- Disambiguity, Leisa Reichelt
- Form and Function, Luke Wroblewski
- Frank Chimero
- Aral Balkan
- David Cole
- Seth Godin
- Scott Berkun
- Google Ventures Design Library
- Adaptive Path
- Boxes and Arrows
- UIE Brainsparks
- UX Magazine
- UX Booth
- A List Apart
- Smashing Magazine
- Signal vs. Noise, Basecamp
- 52 Weeks of UX
If you’ve found this article helpful, I would love to hear about it. Comment, tweet me or reach out to share your story: email@example.com
Get My Newsletter
Subscribe to my mailing list and I’ll keep you updated with my latest writing. I’m trying to publish something every 2 months on design thinking and other enriching ideas to help you live a more productive and enjoyable work life.
Color in Design Systems
WEB DESIGN IS BROKEN.
It's just crumbled tosand in your hands and it's just disappointing.
Today we are going to talkabout budget that the big one: budget budget BUDGET! It is such a huge topicbut I'm finally gonna lay down the final word on budget, specifically how much youshould spend when you're buying a website.
I've got the answer for you.
Youready you ready for it? 500,000 pounds a week! There we go! Did it!(that was easy) I'm out.
See you later.
(web design isfixed) No.
If you do have five hundred thousand a week to spend on a websiteyou should get in touch with me.
I think we could work with that.
Budget it's sucha huge topic no one's really kind of tackling the answers of a few there's afew articles on the internet that are like "well if you want this type ofwebsite you should spend around this much and if you want that type ofwebsite you should spend around that" Much it really comes down to a fewfactors namely your attitude towards risk, whether you're whether you'recoming from a gain or a pain perspective and how much you actually stand to makeout of it.
What you're really doing is investing in a website: you're lookingfor it to create a return you want it to be putting money back into your pocket.
If you don't want it to do that then it's only gonna be acting detrimental,it's only gonna be taking money or reputation or whatever out of yourpocket and you really need to rethink the reasons why you're doing this in thefirst place.
Go back to one of my previous videos wherewhat where I ask you the question why are you doing this in the first place.
Sothe first thing that we've got to understand when we're asking thequestion how much does a website cost, how much do I spend on a website, we'vereally got to appreciate that all you're doing is you'retrying to give yourself what they call an 'anchor' This is literally just apsychological stake in the ground so that your brain can go "okay well I'vegot a point to start from" It really doesn't matter what that number is butit becomes your anchor: the first price you hear becomes your anchor and aroundthat point you will base all value judgments.
So be careful when you'reasking this question because you might end up with another massivelyoverinflated number that completely puts you off of even going down that routewhen actually you could have got something that worked for you at areasonable price, and if you get a number that's too lowyou're gonna look around and think "hey well this is all way too expensive" andnot actually start engaging in the conversations to help you understand thevalue that it could bring there is.
Another thing that you need to be reallyaware of when you're trying to create a budget for our website and that is thatyou like me like everyone else on the planetwe are naturally risk-averse: yeah we have loss aversion.
Most people agree withthe statement that "it is better to not lose five pounds than it is to find fivepounds" It's the same five pounds! It's weirdwe're hardwired to avoid losses.
We try and keep what we have and thereforewe're less likely to risk that in search of future gains so this means thatyou're naturally going to be skeptical about the gains that you can create witha website you're naturally gonna want to spend as little as possible andthat means that you're at a risk of actually under investing when you'rebuying a website Yourisk of under-investing because you're averse to loss.
I'm exactly the same: theamount of times that I've bought things that I need on say Amazon and gone forthe cheapest possible one because I wasn't entirely sure if, you know, if itwould bring me the thing that I was looking for - the reality is that I endup spending double because, you know, buy cheap buy twice.
But you can actuallyunder invest and if you do especially in something like a website it's like underinvesting in in your team member: if you if you hire a new salesman andyou under invest in him well then he's not gonna do as good a job as hepossibly could do if you're picking if you're picking your teammembers based on the salary that they're willing to accept then you're probablyunder investing and you're not actually realizing that if you spend a little bitmore you can get like disproportionately larger returns.
The third thing that youreally need to be aware of but before you start thinking about your budget iswhether you're coming from a pain perspective or a gain perspective.
Areyou looking to this website to help you reach new markets to help you, I don'tknow, dominate the competition; to help you boost sales/Is it a gain thing? Are you launching a new business a new product? Or are youlooking at it from a pain perspective? Are you looking at it and thinking wellhow can I use this website to help me automate things, cut costs, reduceoverhead - things like that.
Maybe you've got a whole bunch of bad reviews on yourexisting website and so you're almost being forced by your customers forced byyour marketplace to up your game what you're really trying to do there ismanage losses.
You approach these.
you can buy the same thing in two different waysand your experience and therefore what you're willing to spend completelychanges depending on whether you're coming from a pain or a gain perspective.
The final line on it is using an analogy that we use sometimesit's based around cars basically.
Are you are you just trying toget to and from work or are you trying to win Formula One the Formula One GrandPrix you need very different types of cars to be able to do each of thosethings.
There's no point in buying a Formula One car because when you pull upin the Sainsbury's car park you're gonna have nowhere to put your shopping.
Likewise there's no point in buying a Fiat Panda and taking it to the track.
Sothe better you can understand what type of race is that your business is tryingto win, or what type of things your business are trying to do with a websiteand what that's worth to you is the better you're gonna be able to startcreating a realistic budget and get a return that's more in line with yourexpectations.
My name is Aaron Taylor I'm helping youto make better decisions and have better conversations when you're buying awebsite.
till next time.
[singing] I fixed webdesign, said I fixed web design.
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: