web designers Melrose Massachusetts

Melrose web design

web design adobe

Hello and welcome to this web design Web Designer Melrose video tutorial.

I’m Owen Corso from Google.

web design yearly salary web design naics

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.

web design unit 1 lesson 7

Data Driven Templates for Display & Video 360 Ad Canvas - Google Web Designer

Backstory

I am a product designer at Google, and I joined the company through Sparrow, a French startup that got acquired on July 20, 2012. Since then, I worked with the Gmail team to build from scratch a flagship product that became Inbox by Gmail. It shipped on October 22, 2014.

I designed productive applications for a few years, and I felt like I reached a tipping point. I wanted to expand my skill set, learn new things every day and get better at something I’ve never touched. I needed new challenges to reboot myself by leaving my comfort zone.

I got interested in virtual reality around the Oculus Kickstarter period because of the immersiveness and endless possibilities that came with it. There is nothing more exciting than building for a new medium and exploring an uncharted territory.

I joined the Google Cardboard and Virtual Reality team on April 17, 2015. Thanks to Clay Bavor and Jon Wiley for this great opportunity.

Another dimension

My first weeks in the team were as scary as it can get. People used words I had no idea of and asked me questions I didn’t know how to answer.

I am not going to lie, ramping up on the jargon was not easy but I was expecting that. Virtual reality is a deep field (pun intended) grouping together a variety of job titles each requiring a very specialized skill set. The first weeks were intense and day after day I had a better vision of the big picture. Slowly, the pieces came together. I found out which roles would be the best fit, what I wanted to do and what was required to get there. Regardless of the mission, I knew I would have to learn a lot, but I was prepared for this challenge. My feelings varied from one day to another. From super excited to create and learn something new, to super scared because of the colossal knowledge I still had to learn. Working with smart and knowledgeable people around me reinforced these mixed feelings.

Everything is going to be alright

I told myself and firmly believed that the dots would connect eventually. I am a passionate person, and I knew that I didn’t mind spending hours learning and experimenting.

During my product designer career, I got better at understanding, identifying and resolving user problems. Making things easy to use and delight users is not that different, no matter the medium.

The core of the mission is the same, but to get you from point A to B there are some interesting things to know.

  • Sketching, is, again, at the core of everything. During any brain dump or design phase, sketching is as fast as it can get. I’ve sketched more in the time I’ve joined this team than I have in my entire career.
  • Any design skills as diverse as they are will be a huge benefit.
  • Photography knowledge will help you because you will interact with concepts such as field of view, depth of field, caustics, exposure and so on. Being able to use light to your advantage has been much valuable to me already.
  • The more you know 3D and tools, the less you will have to learn. It’s pretty obvious but be aware that at some point, you might do architecture, character, props modeling, rigging, UV mapping, texturing, dynamics, particles and so on.
  • Motion design is important. As designers, we know how to work with devices with physical boundaries. VR has none, so it’s a different way of thinking. “How does this element appear and disappear?” will be a redundant question.
  • Python, C#, C++ or any previous coding skills will help you ramp up faster. Prototyping has a big place because of the fundamental need of iterating. This area is so new that you might be one of the first to design a unique kind of interaction. Any recent game engine such as Unity or Unreal engine largely integrates code. There is a large active community in game and VR development with a huge amount of training and resources already.
  • Be prepared to be scared and get ready to embrace the unknown. It’s a new world that evolves every day. Even the biggest industry-leading companies are still trying to figure things out. That’s how it is.

Roles

Design teams will evolve because this new medium opens a lot of possibilities for creation. Think about the video game or the film industry for instance.

I think there will be two big design buckets.

The first one will be about the core user experience, interface, and interaction design. This is very close to how product design team are structured today (Visual, UI, UX, motion designers, researchers, and prototypers).

Each role will have to adapt to the rules of this new medium and keep a tight relationship with engineers. The goal will always remain the same; create a fast iteration cycle to explore a wide range of interactive designs.

On the other hand, content teams will replicate indie and game design studio structure to create everything from unique experiences to AAA games. The entertainment industry as we know it in other mediums will likely be very similar in VR.

Ultimately, both will have a close relationship to create a premium end to end experience. Both industries have a great opportunity to learn from each other.

To wrap up on my personal experience, I think being a product designer in VR is not that different but requires a lot of dedication to understand and learn a vast field of knowledge.

First step and fundamentals of VR design

First step

In this second part of the article, I will try to cover the basics you need to know regarding this medium. It’s meant to be designer oriented and simplified as much as possible.

Let’s get (a little bit) technical

The new dimension and immersiveness is a game changer. There is a set of intrinsic rules you need to know to be able to respect physiologically and treat your users carefully. We regrouped some of these principles in an app so you can learn through this great immersive experience.

Download Cardboard Design Lab

You can watch Alex’s presentation at I/O this year which goes more in-depth. The following is a small summary.

If you have to remember just two rules:

  • Do not drop frames.
  • Maintain head tracking.

People instinctively react to external events you might not be aware of, and you should be designing accordingly.

Physiological comfort. It regroups notions like motion sickness. Be careful when using acceleration and deceleration. Maintain a stable horizon line to avoid the “sea sickness” effect.

Environment comfort. People can experience various discomforts in certain situation like heights, small spaces (claustrophobia), big spaces (agoraphobia) and so on. Be careful with the scale and colliding objects. For example, if someone throws an object at you, you will instinctively try to grab it, dodge or protect yourself. Use it to your advantage and not to user’s disadvantage.

You can also use user senses to help you create more immersive products and cues. You can find inspiration in the game industry. They use all sorts of tricks to guide users during their journey. Here’s a couple:

  • Audio for spatial positioning.
  • Light to show a path and help the player.

Do not hurt or over-fatigue your users. It’s a classic mistake when you start to design for this medium. As cool as it looks, Hollywood sci-fi movies fed us with interactions that goes against simple ergonomic rules and can create major discomfort over time. Minority Report gestures are not suitable for a long period of activity.

I made a very simplified illustration of XY head movement safe zones. Green is good, yellow is ok and avoid red. There are a some user studies made public (links at the bottom of the page) that will give you more in-depth information about that topic.

A simplified illustration of XY head movement safe zones.

Bad design can lead to more serious conditions.

As an example, have you heard about Text Neck? A study, published in Neuro and Spine Surgery measured varying pressures in our neck as our head moves to different positions. Moving from a neutral head position looking straight ahead to looking down increase the pressure by 440%. The muscles and ligaments get tired and sore; the nerves are stretched, and discs get compressed. All of this misbehavior can lead to serious long-term issues such as permanent nerves damages.

TLDR; Avoid extended look down interactions.

Degrees of freedom

The body has six different ways of moving in space. It can rotate and translate in XYZ.

3 Degrees of freedom (Orientation tracking)

Phone based head mounted device such as Cardboard, Gear VR are tracking the orientation via an embedded gyroscope (3DOF). Rotations on all three axes are tracked.

6 Degrees of freedom (Orientation + Position tracking)

To achieve six degrees of freedom, the sensor(s) will track positions in space (+X, -X, +Y, -Y, +Z, -Z). High-end devices like HTC Vive or Oculus Rift are 6DOF.

Tracking
Making 6DOF possible frequently involves optical tracking of infrared emitters by one or more sensors. In Oculus’s case, the tracking sensor is on a stationary camera, while in Vive’s case the tracking sensors are on the actual HMD.

Oculus and Vive lighthouses position tracking

Inputs

Depending on the system you are designing for, the input method will vary and affect your decisions. For example Google Cardboard has a single button, that’s why the interaction model is a simple gaze and tap. HTC Vive uses two, six degrees of freedom controllers and Oculus will ship with an Xbox One controller but will eventually use a 6DOF dual controller “Oculus Touch”. All of them allow you to use more advanced and immersive interaction patterns.

The good old Xbox OneOculus Touch

There are also other kinds of inputs such as hand tracking. The most famous being Leap Motion. You can mount it to your Head Mounted Display (HMD).

Leap Motion on top of a DK2

This area constantly evolves as technology catches up but as of today, hand tracking is not reliable enough to be used as the main input. The principal issues are related to hands and fingers, collisions, and subtle movements tracking.

Even though it’s very familiar, using a game controller is a disappointing experience. It physically removes some of the freedom VR is creating. In FPS, strafing and moving might usually cause some discomfort because of the accelerations.

On the other hand, the HTC Vive controllers reinforce the VR experience thanks to the 6 degrees of freedom, and Tilt Brush is a really good example. As I am writing theses lines, I haven't tried the Oculus touch but every demo I have seen looks very promising. Check out Oculus Toybox demo.

While designing user interfaces and interactions, inputs are the keystone that will drive some decisions differently depending on which method you are using. You should be familiar with all of them and aware of their limitations.

Tools

This is a big piece and might require a more in-depth article. I will focus on the most popular tools used in this industry.

Pen and paper

You just can’t beat them. It’s the first tool we use because it’s always around and does not require too many skills. It’s a proven way to express your ideas and iterate at a fast and cheap pace. Theses factors are important because, in VR, the cost of moving from wireframes to hi-fi is higher than 2D.

Sketch

I still use it every day. Because of its ease of use, it’s the perfect tool that allows me to create a lot of explorations before moving to a VR prototype. It’s also handy for its export tools and plugins that are a huge time saver. If you are not familiar with that program, I wrote articles here and there.

Cinema 4D

I don’t see C4D as a competitor of Maya. Both are great tools, and each excels in its own way. When you don’t have a 3D background, the learning curve can be very steep. I like C4D because the interface, the parametric and non-destructive approach make sense for me. It helps me create more iterations quickly. I love the MoGraph modules, and a lot of great plugins are available. The community is very active, and you can find a lot of high-quality learning materials.

Cinema 4D motion explorations

Maya

Maya is colossal in a good and a bad way. It does anything and everything a 3D artist needs. Most of the games and movies are designed with it. It’s a robust piece of software which can handle massive simulations and very heavy scenes with ease. From rendering, modeling, animation, rigging, it’s simply the best tool out there. Maya is highly customizable, and that is one reason why it’s the industry standard. Studios need to create their own set of tools, and Maya is the perfect candidate to integrate any pipeline.

On the other hand, learning all the tools will require your full and unconditional dedication for quite some time. I mean weeks of explorations, months of learning and years of practice on a daily basis.

Unity

It’s most certainly THE prototyping tool where everything will happen. You can easily create and move things around with a direct VR preview of your project. It’s a powerful game engine with a great community and a ton of resources available in their store (the asset author determines the pricing). In the assets library, you can find simple 3D models, complete projects, audio, analytics tools, shaders, scripts, materials, textures and so on.

Their documentation and learning platform are stellar. They have a wide range of high-quality tutorials.

Unity3d uses mainly C# or JavaScript and comes with Microsoft Visual Studio but doesn't come with a built-in visual editor even though, you can find good ones in the assets store.

It support all major HMD and is the best to build for cross-platform: Windows PC, Mac OS X, Linux, Web Player, WebGL, VR(including Hololens), SteamOS, iOS, Android, Windows Phone 8, Tizen, Android TV and Samsung SMART TV, as well as Xbox One & 360, PS4, Playstation Vita, and Wii U

It supports all major 3D formats and has the best in 2D game creation. The in-app 3D editor is weak, but people have built great plugins to correct that. The software is licensed based, but you can also use the free version to a certain extent. You can check the details on their pricing page. It’s the most popular game engine out there with ~47% of market share.

Unreal Engine

The direct competitor of Unity3D. Unreal also has great documentation and videos tutorials. Their store is smaller because it’s much newer.

One of the big advantages over the competition are the graphic capabilities; Unreal is one step ahead in nearly every area: terrain, particles, post processing effects, shadows & lighting, and shaders. Everything looks amazing.

Unreal Engine 4 uses C++ and comes with Blueprint, a visual script editor.

I haven’t worked with it too much yet, so I can’t elaborate more.

Less cross-platform compatibility: Windows PC, Mac OS X, iOS, Android, VR, Linux, SteamOS, HTML5, Xbox One, and PS4.

Closing notes

Virtual reality is a very young medium. As pioneers, we still have a lot to learn and discover. That’s why I am very excited about it and why I joined this team. We have the opportunity to explore and we should, as much as we can. Understand, identify, build and iterate. Over and over.
And over again…

Resources

Community

  • Immersive design Facebook group

Videos

  • Google I/O 2015 — Designing for Virtual Reality
  • Oculus Connect keynotes
  • VR Design: Transitioning from a 2D to 3D Design Paradigm
  • VR Interface Design Pre-Visualisation Methods
  • 2014 Oculus Connect — Introduction to Audio in VR

Tutorials

  • Cinema 4D tutorials
  • Unity 3D tutorials
  • Maya and 3D tools tutorials

Articles

  • LeapMotion — VR Best Practices Guidelines
  • The fundamentals of user experience in virtual reality
  • Ready for UX in 3D?

Thanks everyone who helped me with the rereading and improvements 💖

Melrose web design

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 Melrose 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.

 

web design Melrose

The collapsed page already contains a Tap Area event to expand the ad and an expanded pageMelrose with a close tap area to collapse back down.

web design adobe

How to Be Comfortable in the Dentist's Chair

web design jobs entry level

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.

MUSTAFA: Yeah.

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're tired.

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.

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.

MUSTAFA: Yeah.

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.

MUSTAFA: Yeah.

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.

That's true.

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.

From product design to virtual reality

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.

OK.

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.

web design inspiration 2018

There's a lot involved when it comes to building a good website.

You've got to start thinkingabout SEO from the ground up.

It can't be an afterthought.

The website needs to be safe and secure.

It needs to be fast.

It needs to look good.

It needs to be responsive so it looks good on a cellphone or a laptop or a tablet.

It's your bread andbutter of your business.

So you want to haveyour best foot forward.

You've got to have a great website.