Post pobrano z: masked fingerprint / Une copie de plus démasquée?
 |
 |
| THE ORIGINAL? National Geographic – 2007 “Discover who’s really hidden behind the September 11h” Agency : H Paris, Havas (France) |
LESS ORIGINAL Vancouver Police Department – 2020 “Don’t let thieves hijack your identity Source : Adsoftheworld Agency : Taxi Vancouver (Canada) |
Post pobrano z: masked fingerprint / Une copie de plus démasquée?
|
|
| THE ORIGINAL? National Geographic – 2007 “Discover who’s really hidden behind the September 11h” Agency : H Paris, Havas (France) |
LESS ORIGINAL Vancouver Police Department – 2020 “Don’t let thieves hijack your identity Source : Adsoftheworld Agency : Taxi Vancouver (Canada) |
Post pobrano z: BusConnects: Working it out Together
Outdoor, Online
BusConnects
BusConnects, a division of the National Transport Authority, launched their second round of public consultation for the Core Bus Corridor Project with an expansive through the line campaign created by TBWA\Dublin. The campaign visuals, by Watermark Studios, feature an intricate representation of Dublin city as a Rubik’s cube being solved thanks to the collaborative efforts of the public and BusConnects.
Advertising Agency:TBWA, Dublin, Ireland
Ceo:Deirdre Waldron
Head Of Account Management:Paula Kelly
Executive Creative Director:Des Creedon
Business Director:Yvonne Caplice
Creative Director:Clayton Homer, Dillon Elliott
Art Director:Mikey Ryan
Copywriter:Blaise Hoban
Account Director:Eibhin McLoughlin
Account Executive:Alana Ryan
Producer:Sarah Collins
Senior Strategist:Shane Kelly
Digital Artist:Watermark Creative
Post pobrano z: World Health Organization Health: COVID-19 Tales
Print, Online
World Health Organization
He is trapped in a dystopia against the world coronavirus. We, as humans, are closed to our homes in order to survive this epidemic that will happen every few centuries. At least many of us … Despite all the warnings of the authorities, there are millions of people who did not stay at home and caused the virus to spread. These warnings have a fabulous and unrealistic effect on themselves. In this direction, we; On behalf of the World Health Organization, we prepared a campaign called #Covid19Tales, which contains dark tales that end up with people.
Advertising Agency:Creasoup, Istanbul, Turkey
Copywriter & Creative Director:Erhan Cirak
Illustration + Animation:Ethem Onur Bilgiç
Voiceover:Aslı İnandık
Sound Designer:Ömer Arısoy
Post pobrano z: How to Design Sales Funnels That Convert
According to Pardot, 79% of marketing campaigns never lead to purchases. Only 4% of website visitors make up their mind to make a purchase.
So you ask yourself, where does the other 96% go? Well, they never buy, but there is something you can do.
What they need is encouragement and nurturing. Whilst this is what sales funnels essentially try to do, it’s not as easy as you may think.
It is one thing to build a sales funnel but entirely another thing to design a funnel pathway that converts as many visitors to buyers as possible.
Here are some tips to show you what I mean.
The call-to-action is a vital feature that shifts visitors from one end of the funnel to the other. It is what moves your subscribers to buyers. How you approach the CTA will determine your conversion rate in a great deal.
For too long, content marketers have been making a mistake of using just one CTA at the end of the funnel. As readers’ attention spans are continuously changing, this is not enough. Most of them only reach to the middle of the process before something else piques their attention.
It’s advisable to also place the CTA at the top and bottom of the funnel. The one placed on the top of the funnel does the primary task of calling a subscriber to join a mailing list. The one at the bottom encourages the visitors to sign up for a service or buy a product.
In addition, the CTA should make it easy for the visitors to perform the action you want them to. Create an easy-to-use form and distribute it over the page.
Landing pages are excellent ways to promote every stage of your funnel. Since sales funnels are divided into three parts, you should have a landing page for each level.
This gives you room to increase the number of people you can capture. One landing page that works for the whole website will not yield the same results.
In all the steps, the sales funnel should follow this procedure;
The result you get here will help you analyze your business and the areas you need to improve.
Many visitors use their phones to access websites. According to Smashing magazine, it’s because of this reason that website content should be kept minimum.
But because we are talking about designing a converting sales funnel, you must include all the details that will make or break their purchasing decision.
You might have a perfectly curated sales funnel, but if it has a lot of distractions, you automatically interfere with the design flow.
People make decisions quickly on whether they should stay on a website longer or not. If your page has a lot of distracting features like sidebars, top navigations, or too many images, visitors are likely to bounce off your site.
Every section within the funnel should answer whether it is the final stop or leads to another page. If there is anything else that will distract your visitors or direct them to click away, delete them.
You will agree that coming up with an effective sales funnel is an uphill battle. However, they still remain an essential weapon in content marketing strategies. If you need some inspiration have a look at these sales funnel templates from Performance Funnels. To convert the most visitors, it advisable that you take into account even the smallest things. It’s such alterations that will help you maximise sales at the end of the day.
Post pobrano z: 5 Important Tips When Building Your First Mobile App
Building a mobile application is a complex process, and mistake can be costly in time and money. To make sure that your mobile app projects are a success, here are a few tips that will be helpful.
When building anything complex, you should never start without a plan. Building a mobile app is no exception. To plan ahead for an app, you’ll have to do extensive thinking to make sure you are not forgetting any important functionalities. Some of the steps you should follow include:
As counter-intuitive as it may sound on a design blog, a design-free environment will allow you to create better designed apps. In fact, working on a wireframe will force you to focus on the functional parts of your app design, and prevent you from “prettifying” things to hide your apps flaws.
To make your wireframes more efficient, start by sketching it on paper to get your ideas flowing and work quicker. Try to go for as many ideas as possible.
Use a grid in your wireframes already, grids will make your layout work easier and more stable. Also, try to insert the real content early-on in the process. Dummy content actually doesn’t add any value to the app creation process.
If possible, I would also suggest to try to go colorless. It may be harder, but this type of constrain forces you to be even more sure of the way you lay out the functionalities. When working with a team, you should also annotate your wireframes to better communicate with others.
Once your mobile app’s preliminary work has been done thoroughly, you should try to go for a quick MVP for your mobile app.
There are several reasons for trying to release quickly and often. First, it can give you a competitive edge on other mobile apps similar to yours. It also gives you the opportunity to quickly understand what your users like or not by observing their behavior and collecting their feedback. At last but not least, it will help you avoid heavy development costs on features that you would have abandoned anyway.
Obviously, this advice doesn’t mean that you should release unfinished work. Releasing with less features should never equate with buggy software.
It is important to understand that there is a major difference between what you think that your users are going to do, and how they effectively behave.
For that reason, testing is a crucial part of app development. Organize user testing sessions where you ask them to perform some tasks and observe their behavior. All data and feedbacks should be collected for analysis and later use.
Of course, testing is not useful if it’s not followed by revisions on the app. You need to take your user testing into account and make changes accordingly.
On the longer term, it is important to keep your mobile app updated and regularly fix bugs and add new features. Through the download platforms, you will get regular feeback and comments from your users, you should show them that you care and use their experience to make your software better.
Post pobrano z: CSS Foldable Display Polyfill
Foldable phones are starting to be a thing. Early days, for sure, but some are already shipping, and they definitely have web browsers on them. Stands to reason that, as web designers, we are going to want to know where that fold is so we can design screens that fit onto the top half and bottom half… or left half and right half¹.
Looks like that’s going to make its way to us in the form of env() constants, just like all that notch stuff.
The code block in the polyfill repo is:
@media (spanning: single-fold-vertical) {
body {
flex-direction: row;
}
.map {
flex: 1 1 env(fold-left)
}
.locations-list {
flex: 1;
}
}I would also think it could be…
@media (spanning: single-fold-vertical) {
.page-wrap {
display: grid;
grid-template-columns: env(fold-left) 1fr;
}
}Interesting how there is no fold-right, isn’t it? And aren’t we trying to stay away from directional terms like that and use logical properties? Why not fold-inline-start?
The post CSS Foldable Display Polyfill appeared first on CSS-Tricks.
Post pobrano z: Create Diagonal Layouts Like it’s 2020
Nils Binder covers the ways:
1. Use an SVG in the form of a triangle. This technique is nicely described by Erik Kennedy on CSS-Tricks.
2. Hide part of your section using
clip-path. Read Diagonal Containers in CSS by Sebastiano Guerriero or Sloped edges with consistent angle in CSS by Kilian Valkhof.3. Using CSS Transforms
I would normally be a #2 kinda guy — slice off the top and bottom a bit, make sure there is ample padding, and call it a day. But Nils almost has me convinced this fancy math is better.
Here’s a kinda dumb clip-path way:
And Nils incredibly fancy playground:
Direct Link to Article — Permalink
The post Create Diagonal Layouts Like it’s 2020 appeared first on CSS-Tricks.
Post pobrano z: Thinking in Behaviors, Not Screen Sizes
Chase McCoy wrote a nifty post about the “gap problem” when making a grid of items. His argument might be summarized like this: how should we space elements with margins in CSS? He notes that the gap property isn’t quite ready for prime time when it comes to using it with flexbox, like this:
.grid {
display: flex;
gap: 10px;
}
Right now, using gap with flexbox is only supported in Firefox and I’ve already caught myself forgetting about that in a few projects. So watch out for that.
Anyway, the part about Chase’s blog post that I love is where he mentions Andy Bell’s technique for creating a responsive layout with no media queries, like this:
.grid {
display: grid;
grid-gap: 10px;
grid-template-columns: repeat(auto-fill, minmax(150px, 1fr));
}This CSS is doing the following:
The nifty thing about all this is that our grid is now effectively responsive because of minmax — if you resize the browser, then the grid will snap down into fewer columns, just like this:
No media queries at all! Although sure, there’s a few other ways that you could get this to work but I think this is neat not just because we’re avoiding media queries — instead, it’s because it teaches us to think in a new way when designing and building components.
Chase continues:
With this technique, instead of using breakpoints to specify the screen size where your items should stack, you specify the minimum size an element should be before it stacks. I like this because it encourages developers to think about responsive design in terms of behaviors instead of screen sizes.
“Behaviors instead of screen sizes” is such a great way to think about component design! A lot of the problems I’ve encountered when making components for a design system is when I’ve been thinking about screen sizes — mobile, tablet, desktop, etc. — and trying to make those components fit within those constraints.
Thinking in behaviors is always more effective because there are so many things that can impact a component beyond what screen or device width we’re working with. Perhaps we want that component to fit inside another component. Or we want to align some helper text to the side of it for comparison.
Either way, thinking about behaviors instead of screen sizes isn’t really going to be fully impossible until we have container queries, as Chris writes:
Container queries are always on the top of the list of requested improvements to CSS. The general sentiment is that if we had container queries, we wouldn’t write as many global media queries based on page size. That’s because we’re actually trying to control a more scoped container, and the only reason we use media queries for that now is because it’s the best tool we have in CSS. I absolutely believe that.
The post Thinking in Behaviors, Not Screen Sizes appeared first on CSS-Tricks.
Post pobrano z: Thinking in Behaviors, Not Screen Sizes
Chase McCoy wrote a nifty post about the “gap problem” when making a grid of items. His argument might be summarized like this: how should we space elements with margins in CSS? He notes that the gap property isn’t quite ready for prime time when it comes to using it with flexbox, like this:
.grid {
display: flex;
gap: 10px;
}
Right now, using gap with flexbox is only supported in Firefox and I’ve already caught myself forgetting about that in a few projects. So watch out for that.
Anyway, the part about Chase’s blog post that I love is where he mentions Andy Bell’s technique for creating a responsive layout with no media queries, like this:
.grid {
display: grid;
grid-gap: 10px;
grid-template-columns: repeat(auto-fill, minmax(150px, 1fr));
}This CSS is doing the following:
The nifty thing about all this is that our grid is now effectively responsive because of minmax — if you resize the browser, then the grid will snap down into fewer columns, just like this:
No media queries at all! Although sure, there’s a few other ways that you could get this to work but I think this is neat not just because we’re avoiding media queries — instead, it’s because it teaches us to think in a new way when designing and building components.
Chase continues:
With this technique, instead of using breakpoints to specify the screen size where your items should stack, you specify the minimum size an element should be before it stacks. I like this because it encourages developers to think about responsive design in terms of behaviors instead of screen sizes.
“Behaviors instead of screen sizes” is such a great way to think about component design! A lot of the problems I’ve encountered when making components for a design system is when I’ve been thinking about screen sizes — mobile, tablet, desktop, etc. — and trying to make those components fit within those constraints.
Thinking in behaviors is always more effective because there are so many things that can impact a component beyond what screen or device width we’re working with. Perhaps we want that component to fit inside another component. Or we want to align some helper text to the side of it for comparison.
Either way, thinking about behaviors instead of screen sizes isn’t really going to be fully impossible until we have container queries, as Chris writes:
Container queries are always on the top of the list of requested improvements to CSS. The general sentiment is that if we had container queries, we wouldn’t write as many global media queries based on page size. That’s because we’re actually trying to control a more scoped container, and the only reason we use media queries for that now is because it’s the best tool we have in CSS. I absolutely believe that.
The post Thinking in Behaviors, Not Screen Sizes appeared first on CSS-Tricks.