Articles

Perfect CTA Placement: Above-The-Fold Vs. Below-The-Fold

,

As a website designer, your professional life revolves around crucial questions that might help you to deliver better results for your clients.

Which widgets are essential to driving conversions? What kind of checkout page elements do you need to include? Should there be a video or slideshow on that product page?

One of the biggest queries that we face when building landing pages to encourage sales is whether a CTA (call to action) button needs to be above or below the fold. 

Answering the question: “Where should the CTA go?” correctly could make or break your client’s chances of a sale. Unfortunately, this particular concern has been the source of a raging debate for many years now. Everyone has their own opinion about CTAs and where they belong.

Today, we’re going to cover the benefits and issues with placing a CTA above the fold.

Should You Place a CTA Above the Fold? 

Starting with a quick refresher, the term “above the fold” refers to any area of a website seen on a screen when a user arrives on a webpage. The content that appears above and below the fold may differ depending on the device you’re visiting a website with. 

Experts in the design and digital marketing world have frequently claimed that if you want to get the best results with a CTA, you need to place it above the fold. 

This strategy makes a lot of sense. If your CTA is above the fold, then your chances of it being seen are significantly higher. Some customers might not want to scroll to the bottom of a page to find out what they need to do next in their buyer journey. 

Additionally, according to the NN group, the 100 pixels that appeared above the fold were seen 102% more often than the pixels underneath the fold. Eye-tracking technology learned that more often than not, you’ll get more engagement above the fold. 

Just look at this landing page from Lyft, for instance, you immediately see what you need to do next:

It’s not just a single study that has touted the benefits of an above-the-fold CTA, either. 

Another report into the “importance of being seen” found that above-the-fold ads and CTAs had a 73% rate of visibility compared to only 44% for those below the fold. 

So, with stats like that to think about, why would you ever consider using a below-the-fold CTA? 

When to Place a CTA Below the Fold

As with most things in web design, there is an exception to the rule. 

Yes, above the fold, CTAs will be better for you most of the time. However, there are times when you might need to think outside of the box. 

Most people think that placing a CTA below the fold practically guarantees that it won’t be seen. However, if you’re creating a website page or landing page that includes a lot of vital information, your audience will need to scroll. 

For instance, if you’re creating a page where someone can download an app to engage with a business they already know about, it makes sense to speed the journey along with an above-the-fold CTA. However, if you’re trying to convince someone to sign up for your webinar, you might need to tell them what that webinar is all about first. That’s where a below-the-fold CTA comes in handy. 

Customers might not have a lot of time in their busy schedules for scrolling these days. However, they still need the right information before they can make a decision about what to do next with your brand. According to Marketing Experiments, below the fold, CTA buttons can result in a 20% increase in conversions. However, this conversion boost only happens when you’re providing valuable, engaging, and persuasive content.

Check out this example from the Boston Globe, for instance:

The Fold Isn’t Everything in Web Design

The fold is often an essential consideration in web design. 

However, it’s not all you need to think about when you’re deciding where to place sign-up forms and valuable CTA buttons. 

According to the Nielsen Norman group, the content that appears at the top of the page will always influence user experience. However, that doesn’t mean that you need to place your CTA there. What you do need to do is ensure that whatever you have above the fold is promising enough to engage your visitor and make them scroll. 

Put simply, what’s above and below the fold does matter, but your focus should be on taking advantage of customer motivation, rather than worrying exclusively about an imaginary line. 

When deciding where a CTA belongs, you need to think about motivation. 

How motivated is your prospect to click on a button? How desirable is your offering at that time, and how much does your visitor already know about the thing they’re being offered?

If you’re going to need to provide more information before your customer wants to convert, then a below-the-fold CTA makes more sense. 

If you’ve already provided all the information that your customer needs and a prospect is visiting from an advertisement or another page on the website, then above the fold should be exceptional. 

The Truth About Designing for The Fold

The reality for web designers today is that achieving higher conversion rates doesn’t really have that much to do with whether a CTA is above or below the fold.

What’s important is whether your buttons come under the right amount of copy that answers the correct questions for an audience. 

Remember, when visitors come to a website, they’re looking for different things. There are visitors that:

  • Already know your brand and value your offering: These people are often clicking into your landing pages from other marketing campaigns where they’ve learned about the brand or offer. You can give these prospects a CTA immediately so they can continue down the buyer’s funnel as fast as possible. 
  • Are uncertain about your offering and need to know a bit more: These people need some extra information. They might have a concern that needs to be addressed before they’re willing to spend their money. You might not need much copy here, which means that a CTA may still appear above the fold. 
  • Are brand new to your website: These prospects need a reasonable amount of copy. They don’t know what you’re offering or why it’s valuable to them. Because of this, you may need to wait to push them into action until you’ve delivered the right copy. 

In some cases, you may even place multiple CTAs on the same page. Some people will have a general understanding of the technology and what it does. This means that they’ll be happy to click on the button at the top of the fold. 

On the other hand, there could also be visitors arriving on the same page that don’t understand what the benefits of real-time personalization are. This means that you need to elaborate a little on what you have to offer. A simple one-line explanation isn’t enough here.  

Figuring Out Where to Place a CTA

Deciding where to place different elements of a website is a common challenge for web designers. Despite tons of blogs out there, that claim “above the fold” is always the best option for any conversion rate optimization, the truth is a little more complicated. 

The critical thing to remember as a web designer is that a CTA button asks a customer for commitment. Even if the CTA allows someone to download a free demo or sign-up for a newsletter without spending any money, it requires a customer to start a relationship with a brand. 

In a world where customers are less trusting of companies than ever, it doesn’t make sense to push them into a relationship too quickly. Asking for a commitment from a target audience before they’ve had the chance to see what’s “in it for them” is not a good idea. 

Jump in too quickly, and you’re likely to rub people the wrong way. 

Go Out and Master the Fold

The issue for today’s designers isn’t figuring out whether a button needs to be visible from the moment someone arrives on a page. Instead, you need to think about whether visitors are finding the CTA at a time when they’re ready to take action. 

You can only answer the question “where should the CTA go?” after you’ve carefully analyzed the project that you’re working on. 

Remember, above the fold isn’t always the answer. 

 

Featured image via Pexels.

Source

The post Perfect CTA Placement: Above-The-Fold Vs. Below-The-Fold first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

OpenTelemetry in Action: Optimizing Database Operations

,

Many software developers can attest that some of the most significant issues in their applications arise from database performance. Though many developers prefer to use a relational database for enterprise applications, typical logging and monitoring solutions provide limited signals to detect database performance issues. Rooting out common bad practices such as chatty interactions between the application code and the database is non-trivial.

As developers, we need to understand how our database is performing from the context of user transactions. Ideally, we would have a common tool that can monitor the performance of both the application and the database concerning user transactions. OpenTelemetry has emerged as a popular tool for application monitoring, but it can also be extended for monitoring databases.

Source de l’article sur DZONE

/par

3 Essential Design Trends, June 2022

,

Are you bored with some of your current design projects? This month’s collection of website design trends can help break you out of that rut with some fun and funky alternatives.

And all of these options are anything but boring. From visual display to technique, these trends present a different set of challenges.

Here’s what’s trending in design this month.

1. Layers on Layers

These website designs have so many layers of information that you almost don’t know where to look or where the design elements start and stop.

This can be a complex technique to make work because of the number of elements competing for the same attention in the design.

What you are likely to see with this design tend includes an image or video background with some motion but not anything that truly demands attention. Then add on a few still images in smaller frames throughout the design. Layer on text as well for a three-deep effect.

If you interact with these designs, you’ll find that they are not flat either. They all include animated elements, hover states, and interactions that help direct you through the layers of what can be a somewhat complex design.

Western National Parks Association uses a background image, middle images with animations, and multiple text layers (some on the pictures and some on the background). There’s also scroll animation to help build the design. A lot is going on, but it does not feel too busy.

WIP Architects is another design with layers that interact with each other and include motion. With a lot of scroll animation and layers that go in front of and behind other elements, engagement helps this site work.

The Shipwreck Survey uses the same basic layer outline with a little more overlap between elements and less overall animation. The primary animated effect on the homepage is the scroll bar.

 

 

2. Directed Click Actions

This interesting website design trend can be incredibly useful or a wasted element – directed click actions. These are buttons, icons, and animations that tell you to click somewhere in the design to move to the next stage of interaction.

The direct approach ensures that users see and have the best possible chance of doing what the design is intended for. On the other hand, if you need this much instruction, is the design too complicated? Or is there a middle ground where this trend looks great and is usable?

In each of the examples below, these directed click actions are a bit different.

HUG Co has a big circle to click in the bottom third of the screen. It’s almost designed like a bullseye, and you can’t miss it. The thing that is interesting here is that most of the video falls below the scroll. The click action also has two emojis to denote action – a smiling face or pointer when you are ready to click. (The click extends the video to full screen.)

ThinkOvery also uses a similar circular click icon. It also takes you to the next screen in a single movement so that you can continue to explore the design.

Living with OCD has a different approach with scroll and back-to-top icons paired in the bottom right corner. The scroll option includes words to help create direction and instruction. It consists of a small animation and an interactive hover state when you get close to the interactive element. The interesting thing here is that it is not actually a button, and you use a traditional scroll to interact.

 

 

3. Word Breaks

If you are a stickler for readability, this design trend might make you cringe.

In each of these designs, words are broken across lines – some with and some without hyphens. For the most part, there’s not much confusion about what the words are, but it does make you pause and think during the page experience.

Why would this be a design trend?

It’s a combination of using large typography, long words, and figuring out a solution to create a common experience between large and small screens. Many of these words would not fit on mobile screens, for example, with the same weight, scale, and impact as the desktop counterparts.

Hence, the word break solution. It creates a consistent user experience across devices.

This technique should be used only if you think your audience is savvy enough to understand what you are trying to communicate with the word break. It can be a tricky proposition!

Plantarium breaks at “plant” with a word that’s made up. But with the imagery and supporting terms, you still know immediately what the design is about.

Michelle Beatty takes a common word and breaks it. Because “photog” and “rapher” are the only letters on the screen, it’s pretty easy to figure out. What’s interesting is that the word break is not on the syllable, but the letters do stack nicely with this break visually.

Wreel Collective breaks a word with a hyphen in giant letters – something we rarely see in website design. Hyphens are not often used in this medium. Because of this, it gets your attention and makes you think about the words and the design.

 

 

Conclusion

There are a lot of rule-breaking trends in this month’s collection. They are interesting, fun, and require a certain level of risk to execute.

Could you see yourself (or your clients) opting for a design that features one of these trends? Time will tell if these visual compositions grow in popularity or begin to fade fast.

Source

The post 3 Essential Design Trends, June 2022 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

WordPress 6.0 Lives Up To The Hype

,

WordPress 6.0 has been released, and another niche jazz musician will be enjoying extra Spotify royalties next month.

WordPress 6, named for latin-jazz musician Arturo O’Farrill, is the realization of a change of direction the WordPress Foundation adopted several years ago.

All versions of WordPress now power around 42% of the web. That’s approximately 810,000,000 sites. If you looked at each site for a single second, without pausing to blink, it would take you over 25 years to see the home page of each one — of course, if you factor in how long a typical WordPress site takes to load it would take well over a century.

Some people (i.e., me) have been predicting the decline of WordPress for so long that sooner or later, we were bound to be correct. And, despite its astonishing reach, there are some signs that its market share may now be in decline. Even the W3C abandoned it in favor of Craft.

Of the 1,930,000,000 sites that currently make up the web, only around 400,000,000 are active. WordPress’s long-term dominance, coupled with a stalling market share, means that a disproportionate number of abandoned sites are WordPress. With site builders like Wix, Squarespace, and Shopify taking huge chunks of WordPress’ share of new sites, WordPress is facing something of a cliff edge.

What the ill-informed naysayers (i.e., me) hadn’t counted on was that WordPress had already seen the writing on the wall and formulated a plan…

WordPress’s problem has always been its legacy code; supporting out-of-date ideas and a spaghetti-like codebase has meant a great deal of work to do anything new. As a result, the last few releases have seen great ideas stifled by labored implementation. Even the most loyal WordPress user has to admit that Gutenberg, while filled with potential, doesn’t work the way it should. However, with WordPress 6, all the work may be starting to pay off.

With version 6, the block editor in WordPress is starting to feel like a design tool that, if not perfect, is at least usable. Editing content no longer feels like you’re fighting against the UI. Most importantly, the bar for creating a site is much, much lower. WordPress 6 also offers improved performance and accessibility, both areas that have traditionally been lacking. Security is still something of an issue, but that is mainly due to the ROI for hackers that massive market shares generate.

WordPress, it seems, has arrived at two conclusions: its main competition isn’t other CMS but other site builders. To maintain its market dominance, it needs to cater not to professionals but to amateurs.

Don’t get me wrong; the WordPress ecosystem will benefit from WordPress 6, at least reputationally. New sites run by amateurs eventually become established sites run by, if not professionals, then at least knowledgeable amateurs.

OK, so WordPress probably isn’t a good choice for enterprise sites. And there are certainly better options for ecommerce. And as for SEO, well, probably best not mentioned.

But in WordPress 6, we have a free, open-source site builder that lowers the bar for making a new site. It’s a credit to the community that has persevered to produce it.

Source

The post WordPress 6.0 Lives Up To The Hype first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Jump Into the DevOps Pool. The Water is Fine.

,

In scanning the IT landscape, the call for DevOps engineers remains toward the top of many companies’ priorities. A nationwide search through various job posting sites returns literally thousands of DevOps opportunities. However, reviewing these job postings shows that the skillsets required are widely varied. In comparison, software development job descriptions and requirements tend to have a narrower focus – broadly speaking, a language and a particular framework. DevOps job descriptions and requirements range from implementing continuous integration and continuous delivery (CI/CD) processes, to building infrastructure, to configuration management, to cloud operations, to writing code in any number of languages, and so on. It’s an impressive and intimidating list. Have you considered joining the DevOps wave but have been challenged in getting a clear picture of what DevOps is or means? If so, you’re not alone.

What is DevOps?

While many organizations have DevOps teams, even within a single organization, there are likely to be multiple roles within a DevOps team. Why is that? The reason is that DevOps is a process, and various roles within a DevOps team each contribute to the process. The DevOps process is a product of the evolution of Agile development processes. With Agile, production-quality software is iteratively delivered, which drives the need to deploy software more often. The process of getting software into production needed to be streamlined, thus the DevOps movement and process was born.

Source de l’article sur DZONE

/par

A Brief History of Responsive Web Design

,

Websites haven’t always been as adaptable as they are today. For modern designers, “responsivity” is one of the most significant defining factors of a good design. After all, we’re now catering to a host of users who frequently jump between mobile and desktop devices with varying screen sizes. 

However, the shift to responsive design didn’t happen overnight. For years, we’ve been tweaking the concept of “responsive web design” to eventually reach the stage we’re at today. 

Today, we’re going to take a closer look at the history of responsive web design.

Where Did Web Design Begin?

When the first websites were initially created, no one was worried about responsivity across a range of screens. All sites were designed to fit the same templates, and developers didn’t spend a lot of time on concepts like design, layout, and typography.  

Even when the wider adoption of CSS technology began, most developers didn’t have to worry much about adapting content to different screen sizes. However, they still found a few ways to work with different monitor and browser sizes.

Liquid Layouts

The main two layout options available to developers in the early days were fixed-width, or liquid layout. 

With fixed-width layouts, the design was more likely to break if your monitor wasn’t the exact same resolution as the one the site was designed on. You can see an example here. 

Alternatively, liquid layouts, coined by Glenn Davis, were considered one of the first revolutionary examples of responsive web design. 

Liquid layouts could adapt to different monitor resolutions and browser sizes. However, content could also overflow, and text would frequently break on smaller screens. 

Resolution-Dependent Layouts

In 2004, a blog post by Cameron Adams introduced a new method of using JavaScript to swap out stylesheets based on a browser window size. This technique became known as “resolution-dependent layouts”. Even though they required more work from developers, resolution-dependent layouts allowed for more fine-grained control over the site’s design. 

The resolution-dependent layout basically functioned as an early version of CSS breakpoints, before they were a thing. The downside was developers had to create different stylesheets for each target resolution and ensure JavaScript worked across all browsers.

With so many browsers to consider at the time, jQuery became increasingly popular as a way to abstract the differences between browser options away.

The Rise of Mobile Subdomains

The introduction of concepts like resolution-dependent designs was happening at about the same time when many mobile devices were becoming more internet-enabled. Companies were creating browsers for their smartphones, and developers suddenly needed to account for these too.

Though mobile subdomains aimed to offer users the exact same functions they’d get from a desktop site on a smartphone, they were entirely separate applications. 

Having a mobile subdomain, though complex, did have some benefits, such as allowing developers to specifically target SEO to mobile devices, and drive more traffic to mobile site variations. However, at the same time, developers then needed to manage two variations of the same website.

Back at the time when Apple had only just introduced its first iPad, countless web designers were still reliant on this old-fashioned and clunky strategy for enabling access to a website on every device. In the late 2000s, developers were often reliant on a number of tricks to make mobile sites more accessible. For instance, even simple layouts used the max-width: 100% trick for flexible images.

Fortunately, everything began to change when Ethan Marcotte coined the term “Responsive Web Design” on A List Apart. This article drew attention to John Allsopp’s exploration of web design architectural principles, and paved the way for all-in-one websites, capable of performing just as well on any device. 

A New Age of Responsive Web Design

Marcotte’s article introduced three crucial components developers would need to consider when creating a responsive website: fluid grids, media queries, and flexible images. 

Fluid Grids

The concept of fluid grids introduced the idea that websites should be able to adopt a variety of flexible columns that grow or shrink depending on the current size of the screen. 

On mobile devices, this meant introducing one or two flexible content columns, while desktop devices could usually show more columns (due to greater space). 

Flexible Images

Flexible images introduced the idea that, like content, images should be able to grow or shrink alongside the fluid grid they’re located in. As mentioned above, previously, developers used something called the “max-width” trick to enable this. 

If you were holding an image in a container, then it could easily overflow, particularly if the container was responsive. However, if you set the “max-width” to 100%, the image just resizes with its parent container. 

Media Queries

The idea of “media queries” referred to the CSS media queries, introduced in 2010 but not widely adopted until officially released as a W3 recommendation 2 years later. Media queries are essentially CSS rules triggered based on options like media type (print, screen, etc), and media features (height, width, etc). 

Though they were simpler at the time, these queries allowed developers to essentially implement a simple kind of breakpoint – the kind of tools used in responsive design today.  Breakpoints refer to when websites change their layout or style based on the browser window or device width.

Viewport Meta tags need to be used in most cases to ensure media queries work in the way today’s developers expect. 

The Rise of Mobile-First Design

Since Marcotte’s introduction of Responsive Web Design, developers have been working on new ways to implement the idea as effectively as possible. Most developers now split into two categories, based on whether they consider the needs of the desktop device user first, or the needs of the mobile device user. The trend is increasingly accelerating towards the latter. 

When designing a website from scratch in an age of mobile-first browsing, most developers believe that mobile-first is the best option. Mobile designs are often much simpler, and more minimalist, which matches a lot of the trends of current web design.

Taking the mobile first route means assessing the needs of the website from a mobile perspective first. You’d write your styles normally, using breakpoints once you start creating desktop and tablet layouts. Alternatively, if you took the desktop-first approach, you would need to constantly adapt it to smaller devices with your breakpoint choices.

Exploring the Future of Responsive Web Design

Responsive web design still isn’t perfect. There are countless sites out there that still fail to deliver the same incredible experience across all devices. What’s more, new challenges continue to emerge all the time, like figuring out how to design for new devices like AR headsets and smartwatches. 

However, it’s fair to say we’ve come a long way since the early days of web design. 

 

Featured image via Pexels.

Source

The post A Brief History of Responsive Web Design first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

How to Streamline the Customer Experience with Monads in Kotlin

,

 At my company, we see a lot of SDKs and Swagger-generated clients that could throw exceptions at any time. This could be a fault in our logic, or it could be a fault with some 3rd party SDKs that have no rhyme or reason to how their exception handling works. But either way, when our customers want to fetch a Git commit history for a service, they do not want to be greeted with an error message.

We’ve seen GitHub go down during a customer demo and 3rd party integrations throwing other unexpected exceptions. Overall, it was a very discouraging experience for our customers that we had no control over.

Source de l’article sur DZONE

/par

Introduction to Serverless With AWS Lambda and Bitrise API: Part 1

,

In the early days of software development, anyone seeking to develop a web, mobile, or backend application had to own the hardware required to run a server, which is an expensive process.

Then, when cloud computing came, it became possible to lease server space or a number of servers remotely. The developers and companies who rent these fixed units of server space generally overbuy to ensure that a spike in traffic or activity won’t exceed their monthly limits and break their applications. Because of this, a lot of the server space that gets paid for can be wasted.

Source de l’article sur DZONE

/par

The 3 Conversations That Improve Developers’ Lives w/ Reprise’s Jennie MacDougall

,

We want to make the Dev Interrupted podcast a vital, enjoyable part of your week. Please take 2 minutes and answer our new Listener Survey. It lets us know a bit about you, what you want from Dev Interrupted and what you want from podcasts in general! 

If you’re doing your job right, most of your time and your team’s time should be spent actually building things. That means conversations should be reserved to the very important ones.

Source de l’article sur DZONE

/par