Articles

Guide pratique de sécurité des conteneurs

Vous cherchez à mieux comprendre la sécurité des conteneurs ? Découvrez ce guide pratique qui vous aidera à protéger vos applications et vos données !

Lire le rapport : Rapport sur les tendances des conteneurs DZone 2023

Avec l’essor de l’architecture conteneurisée, les entreprises réalisent l’importance croissante de la sécurité des conteneurs. Bien que les conteneurs offrent indéniablement de profonds avantages, tels que la portabilité, la flexibilité et l’évolutivité, ils introduisent également des défis de sécurité sans précédent. Dans ce rapport, nous aborderons les principes fondamentaux et les stratégies de sécurité des conteneurs et nous nous pencherons sur deux méthodes spécifiques : la gestion des secrets et le patching. De plus, nous examinerons les outils et les techniques pour sécuriser les clés, les jetons et les mots de passe.

La gestion des secrets est une pratique essentielle pour assurer la sécurité des conteneurs. Les bases de données cryptographiques sont un moyen efficace de stocker et de gérer les secrets. Les bases de données cryptographiques peuvent être utilisées pour stocker des informations sensibles telles que les clés d’accès, les jetons d’authentification et les mots de passe. Les bases de données cryptographiques peuvent également être utilisées pour générer des clés et des jetons dynamiques, ce qui permet aux applications d’accéder aux données sensibles sans avoir à stocker les informations dans le conteneur.

Le patching est une autre pratique essentielle pour assurer la sécurité des conteneurs. Les outils de patching peuvent être utilisés pour mettre à jour le système d’exploitation et les applications logicielles installées dans le conteneur. Les outils de patching peuvent également être utilisés pour vérifier la présence de vulnérabilités et appliquer les correctifs appropriés. Les outils de patching peuvent également être utilisés pour surveiller l’activité du conteneur et détecter toute activité suspecte.

En conclusion, la sécurité des conteneurs est une préoccupation croissante pour les entreprises. La gestion des secrets et le patching sont des pratiques essentielles pour assurer la sécurité des conteneurs. Les bases de données cryptographiques peuvent être utilisées pour stocker et gérer les secrets, tandis que les outils de patching peuvent être utilisés pour mettre à jour le système d’exploitation et les applications logicielles installées dans le conteneur. De plus, les outils de patching peuvent également être utilisés pour surveiller l’activité du conteneur et détecter toute activité suspecte.

Source de l’article sur DZONE

Ne Pas Brouiller la Définition du Terminé

Résumé : La Définition de Fait – Agilité d’Affaires et Excellence Technique

L’importance d’une définition d’achèvement actionnable – Agilité commerciale et excellence technique

La plupart du temps, les parties prenantes ne sont pas intéressées par la façon dont nous résolvons leurs problèmes, à condition que nous jouions éthiquement selon les règles. Au lieu de cela, ils sont intéressés par la livraison régulière d’incréments précieux, car cela ouvre la voie à l’agilité commerciale. Cependant, il n’y a pas d’agilité commerciale sans excellence technique, ce qui nous amène au sujet d’aujourd’hui: l’importance d’une définition d’achèvement actionnable.

En tant qu’équipe Scrum, une définition d’achèvement actionnable est essentielle pour aider votre organisation à devenir agile. Cela signifie que chaque membre de l’équipe doit être clair sur ce qui doit être fait pour que le produit soit considéré comme terminé. Une définition d’achèvement actionnable est une liste de critères qui doivent être satisfaits pour que le produit soit considéré comme terminé. Ces critères peuvent inclure des tests unitaires, des tests d’intégration, des tests de performance, des tests de sécurité et des tests de conformité.

Une définition d’achèvement actionnable est essentielle pour garantir que les produits livrés sont de qualité et répondent aux attentes des clients. Elle est également essentielle pour s’assurer que les produits sont testés et prêts à être livrés. Les tests sont une partie importante de la définition d’achèvement actionnable car ils permettent de vérifier si le produit répond aux exigences et aux normes de qualité. Les tests peuvent également aider à identifier les problèmes avant qu’ils ne se produisent et à s’assurer que le produit est prêt à être livré.

Une définition d’achèvement actionnable est un outil puissant pour aider les équipes à atteindre l’agilité commerciale et l’excellence technique. Elle permet aux équipes de garantir que les produits livrés sont de qualité et répondent aux attentes des clients. Elle permet également aux équipes de s’assurer que les produits sont testés et prêts à être livrés. Enfin, elle permet aux équipes de mieux comprendre ce qui doit être fait pour que le produit soit considéré comme terminé. En résumé, une définition d’achèvement actionnable est essentielle pour aider les équipes à atteindre l’agilité commerciale et l’excellence technique.

Aujourd’hui, les entreprises sont confrontées à des environnements en constante évolution et à des clients exigeants. Pour rester compétitives, les entreprises doivent être en mesure de livrer rapidement des produits de qualité. Cela signifie qu’elles doivent pouvoir réagir rapidement aux changements et s’assurer que leurs produits répondent aux attentes des clients. Une définition d’achèvement actionnable peut aider les entreprises à atteindre cet objectif en fournissant une liste claire des critères qui doivent être satisfaits pour que le produit soit considéré comme terminé.

Source de l’article sur DZONE

It’s no secret this has been a difficult year for many companies in tech. The truth is, it’s easy to be a leader when times are good. It’s less easy in the midst of a storm.

That’s why we assembled a panel of some of the smartest engineering leaders we know at Interact to talk about the leadership principles that help guide an engineering organization no matter what is happening in the world.

Source de l’article sur DZONE


This is an article from DZone’s 2022 Enterprise Application Security Trend Report.

For more:

Read the Report

According to a 2020 Gartner report, it is estimated that by 2023, 75 percent of cybersecurity incidents will result from inadequate management of identities and excessive privileges. To a large extent, this is attributable to the increased number of identities used by modern cloud infrastructures. Applications run as microservices in fully virtualized environments that consist of dynamically orchestrated clusters of multiple containers in the cloud. 

Source de l’article sur DZONE

Many firms’ design and development decisions are increasingly oriented toward human-centered innovation. Instead of rushing goods to market, these firms are using a user-centered design approach.

Design and development teams build high-performing digital products or websites that uniquely meet customers’ demands by concentrating on the user experience. After all, a good web design is helpful in boosting the business reputation or user experience.

This post will define user-centered design, discuss its fundamental principles, and describe the user-centered design process.

What Is User-Centered Design?

To create an enjoyable solution to a problem, user-centered design is a collection of iterative design processes concentrating on the user’s needs at each step. In UCD, the expectations, objectives, and preferences of the user significantly impact design decisions.

Additionally, users are actively involved in the entire process from start to finish. User-centered design principles encourage designers to create products with users rather than just for them. This strategy typically includes user research, interviews, usability testing, and a massive amount of feedback gathering.

UCD Requires Four Fundamental Components:

  • Visibility: Can people see what your website is about and how to utilize it the moment they land on your page?
  • Availability: Is your website user-friendly? Can they swiftly locate information? They should be able to find call-to-action buttons, menus, filters, and search choices with ease.
  • Legibility: Is the text simple to read for users?
  • Language: Is the language simple to grasp for users? Do you avoid using industry jargon in your UX authoring, which might lead to confusion and hesitation?

What Is The Significance Of UCD?

User experience is important in product design, especially in digital products such as app design, web and interface design, and marketing. Customers want their lives to be simplified. A website, app, or product exists to fulfill a consumer. Hence its success is determined by their interaction with it.

The following are some of the advantages of a user-centered design strategy for a business:

  • Customers keep coming back for more
  • There would be an increase in sales
  • Creating polished, efficient, and widely available goods
  • Understanding challenges thoroughly to provide suitable solutions
  • Customers and teams working together
  • Avoiding typical blunders
  • Enhancing Competitiveness
  • Assisting them in comprehending their market

It offers consumers the following advantages:

  • Making their life easier
  • Fulfilling their desires
  • Companies making them feel heard and understood
  • Making them feel important in the creation of things they use
  • Providing answers to challenges they were unaware they had or could not imagine solutions to

Let’s dig in to learn more about the advantages of UCD.

Businesses can benefit from using the user-centered design approach in various ways. As you incorporate this into your web development, you can enjoy the following four main advantages.

1. Prevent Project Failure

Your company might find it simpler to incorporate improvements and ensure your product is in line with actual user needs if you have a continuous feedback process assessing how customers react to your product, like a website.

Customers feel like their needs are better represented in the finished product, which can increase engagement and strengthen the bond with the company.

2. Improve ROI

This method produces products that more accurately reflect user expectations. The procedure also lessens mistakes made by website users, for instance. When combined, these factors motivate users to convert from leads to paying clients, boosting return on investment.

3. Increase Development Efficiency

In user-centered design, the objectives of the various team members are aligned. This can help clarify the best course of action for all parties involved. A more targeted, goal-oriented development process may be encouraged by the regular evaluation process.

Additionally, businesses can engage stakeholders and explain how their efforts and methodologies will improve customer interactions by using an iterative life cycle during product development.

4. Up The Level Of Competition

Customers will more fully appreciate what you offer, improve their engagement with your product or website, and be more likely to purchase from you if your product is created with their needs and expectations in mind.

As a result, this may increase your ability to compete in your sector.

5. KPIs Are Included

Given your user needs and business objectives, how do you move from the first to the second? You can measure key performance indicators with this in mind once you know what user needs are essential for the overall goals.

For instance, productivity may be the focus of office software, shopper activity may be the focus of sales tools, and retention rates may be the focus of other apps. All of these are necessary steps toward achieving business values like profit and revenue.

Human-Centered Design Versus User-Centered Design

There is a significant difference between humans and users. Simply put, all users are humans; however, not all humans will use your product. Therefore, you must thoroughly understand your target market to produce a successful user-centered design.

Detailed research should be done on the problems and goals of your users. Then, talk to them and give them several chances to offer feedback. By doing this, you’ll create a user persona that is complete and that you can use to determine the priorities for your design.

It’s critical to understand that different user groups may have additional requirements, levels of technical expertise, and expectations for using products like the one you’ve made.

What crucial guidelines or principles should designers consider when adopting a user-centric design?

The Process Of User-Centered Design

Certain fundamental principles underpin user-centered design. While the development process is always iterative, no explicit methods for implementation are specified. The approach can be implemented in either a waterfall or an agile environment.

1. Contextualization

The first step is to analyze the environment in which users will use the product. What are the intended applications of the product for future users? Teams working on projects can get answers by watching and talking to potential users.

2. Outlining The Prerequisites

Specifying the requirements for the new product is the second step. In this step, user requirements are described while considering corporate needs.

3. Design

Once the requirements are established, the actual design process can begin. Designers typically start by producing a straightforward prototype, like one made of paper, then move on to digital wireframes and a finished prototype.

4. Analysis

The project team solicits feedback from potential users after creating a prototype. This is typically done for digital applications through in-depth user testing and qualitative research.

Do surveys and tests evaluate user satisfaction, effectiveness, and efficiency? With the new information, the project team goes back to step 2 or step 3 of the design process to improve the product. Once the user feedback is satisfied, these iterations continue while taking into account corporate frameworks (time and costs).

Top 10 User-Centered Design Principles

Principles of user-centered design attempt to guarantee that usability is the primary priority throughout the development process. These principles, if successfully followed, will ensure that user experience is fulfilled not just during the initial introduction of a product but also during its use.

Furthermore, each of the following principles may be tailored to match the specific requirements and interaction demands of any product.

1. Use Simple Language

Professional Web Designer strives to provide the most readable discourse for the user while creating a product. This involves clarifying vocabulary, eliminating jargon, and simply providing information pertinent to the work.

Presenting users with irrelevant information throughout their use of the product taints its usefulness. Furthermore, basic language helps the user finish the work without being overwhelmed or confused.

2. Feedback

Users expect a reaction to all of their actions. This might involve modifying the look of the screen after completing an activity. If the job is finished after some time, it should display a loading page to notify the user that the task is in process.

Keeping the user informed throughout the process reassures them and keeps them on track with their job.

3. Maintaining Consistency

Keeping the product consistent is essential in ensuring an ideal user experience. Consistency affects how customers approach a product, and the time it takes to learn how to use it.

From the start of the project until its completion, the consistent philosophy underpinning the UCD process should be maintained. If the interface design needs to be updated, it is critical to maintaining consistency across new features to stay beneficial to the user.

4. Give The Complete User Control

Consumers are already aware of their requirements. They should be able to use a product with minimal effort and depend on the product’s help to accomplish the rest.

By removing the effort from the job, the user can do it quickly while keeping control of their activities.

5. Describe The Situation

Before developing a product, the designer must first investigate the ideal user and their wants. The designers can gain a comprehensive sense of some of the issues these people experience by studying their lifestyles.

Many of these observations are conducted through interviews. These interviews provide the designer with information on the exact goals that users want to attain and how they want to achieve them.

6. Examine the Design

Designers undertake usability testing with actual users of their product at this stage in the UCD process. This stage provides designers with insight into how consumers will interact with the product and how to modify it to suit them better.

It is advised that this stage be completed as quickly as feasible. The sooner customers provide input, the faster designers can comprehend their product from the user’s perspective.

7. Create Designs That Are Specific To The Needs Of The User

The design team must examine the distinctive features of their intended demographic as well as frequent real-world activities while beginning the design process. Furthermore, the product should be appropriate for the environment in which it will be utilized the most.

Making a product that needs a lot of work from the user reduces its usability and usefulness, ultimately defeating the objective of UCD.

8. The Design Process Is Iterative

Because user-centered design is based on putting the user first, the product team should constantly be working to improve the user experience. By introducing changes gradually, you will gain a better understanding of your target audience.

9. Adequate Navigational Tools

An essential component of the user experience is the capability to navigate between pages of your website and return to the previous one. Make sure users know where they are on your website and how to leave any pages they don’t want to see.

Customers can better understand how to navigate your page by giving them features like a navigation map, for instance. Make it simple for customers to change their order without leaving the current page if they buy clothing and discover they need a different size once they reach the checkout page.

10. Unflawed System

Customers should find it easy to navigate between your website’s pages and accomplish their goals. If they make a mistake, be there to help them fix it so they can achieve their goal.

The form may ask for specific, essential fields, such as the square footage, and may also include a gentle reminder or an alert that appears if the user accidentally leaves a required field blank.

Customers may feel more comfortable responding to your prompts and participating in a conversation if you ask questions one at a time and offer automated responses for each response.

Wrapping Up

User-centered design is more than just making a good product. It goes further than that. You demonstrate your motivations and intentions by putting your users in the spotlight. You’re demonstrating that it’s not all about meeting deadlines or turning a profit. Instead, you’re telling your users that you understand what they want and prioritize their needs.

It should come as no surprise that the most effective teams are user-centric. Knowing your customer is essential for success in any industry, including design. Create products that put the user first, and you will create products that people will love.

You can build a more robust, user-friendly website that is better equipped to respond to user needs and expectations by incorporating the User Centered Design process into your product design. However, it’s crucial to collaborate with a specialist who can apply these techniques and produce the result you’ve envisioned.

 

Featured image by pch.vector on Freepik

Source

The post 10 Key Principles of User-Centered Design first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

Need help with your NoSQL migration? Look no further than our « NoSQL Migration Essentials » Refcard. We walk through the primary steps for moving out of a relational database, plus important design principles to understand and consider in your migration process.

Readers will review key concepts that range from denormalizing and modeling data to defining access patterns, designing primary keys and indexes, and creating an entity relationship diagram — all demonstrated with a simple site application example. As a bonus, readers can use the included JSON structure at the end to interact with a NoSQL playground.
Source de l’article sur DZONE

Apple has released an OS update. Packaged in with it is the latest version of Safari, 16.

Expected to be released ahead of next month’s macOS 13, Safari 16 is packed with updates, making it one of the most capable browsers available.

For web designers, the significance is the forward momentum in web technologies that enable freer design work and fewer hacks to achieve complex layouts. Little by little, CSS recommendations are being implemented to the point that using JavaScript for layout is rapidly becoming as unnecessary as it is disliked.

Some of this was announced in June in the Safari 16 beta. But a lot has been added in the last couple of months. So here’s what’s new in Safari 16 today.

CSS Container Queries

The most exciting addition to Safari 16 is CSS Container Queries.

It is hard to understate how in-demand this feature has been; if you imagine an edit button on Twitter that gifted you crypto every time you corrected a typo, you’d be getting close to how popular this feature is.

Until now, media queries have detected the whole viewport. And so, if you have an element like a card, for example, that needs to change at smaller viewports, you need to calculate the available space and adapt the element’s design accordingly. Unfortunately, this frequently gets out of sync with edge cases causing more than a few headaches for front-end developers.

Media queries are severely restrictive to modern layout methods like Grid that wrap elements automatically because there is no way to detect how the elements are laid out.

Container Queries solve this by allowing you to define styles based on the size of the actual containing element; if a div is 300px wide, the contents can have one design, and if it’s 400px wide, they can have a different design—all without caring what size the whole viewport is.

This is dangerously close to OOP (Object Orientated Programming) principles and almost elevates CSS to an actual programming language. (All we need is conditional logic, and we’re there.)

The latest versions of Chrome, Edge, and now Safari (including mobile) support CSS Grid. Even discounting the rapid decline of Twitter, this is way more exciting than any edit button.

CSS Subgrid

Speaking of Grid, if you’ve built a site with it (and if you haven’t, where have you been?), you’ll know that matching elements in complex HTML structures often results in nesting grids. Matching those grids requires careful management, CSS variables, or both. With CSS Subgrid, grids can inherit grid definitions from a grid defined higher up the hierarchy.

CSS Subgrid has been supported by Firefox for a while but is not yet part of Chrome or Edge. Until there’s wider support, it’s not a practical solution, and using a fallback negates any benefit of using Subgrid. However, its introduction in Safari will surely herald rapid adoption by Google and Microsoft and moves the web forward considerably.

CSS Subgrid is likely to be a practical solution within 18 months.

AVIF Support

AVIF is an exceptionally compact image format that beats even WebP in many instances. It even allows for sequences, creating what is essentially an animated GIF but smaller, and for bitmaps.

AVIF is already supported by Chrome, with partial support in Firefox. Safari now joins them.

AVIF support is one of the more valuable additions to Safari 16 because you’re probably already serving different images inside a picture element. If so, your Safari 16 users will begin receiving a smaller payload automatically, speeding up your site and boosting UX and SEO.

Enhanced Animation

Safari 16 introduces some significant improvements in animation, but the one that catches the eye is that you can now animate CSS Grid.

Yes, let that sink in. Combine Container Queries and animation. The possibilities for hover states on elements are tantalizing.

Safari 16 also supports CSS Offset Path — known initially as CSS Motion Path — which allows you to animate elements along any defined path. This enables the kind of animated effect that previously needed JavaScript (or Flash!) to accomplish.

Chrome, Edge, and Firefox all support CSS Offset Path; the addition of Safari means it’s now a practical solution that can be deployed in the wild.

Web Inspector Extensions

Announced as part of the beta release, Web Inspector Extensions allow web developers to create extensions for Safari, just as they would for Chrome.

Web Inspector Extensions — or Safari Extensions as they’re destined to be known — can be built in HTML, CSS, and JS, so the learning curve is shallow. It’s a good route into app development for web designers.

Because the underlying technology is the same as other browser extensions, anyone who has made a Chrome, Edge, or Firefox extension will be able to port it to Safari 16+ relatively easily. As a result, there should be a rapid expansion of the available extensions.

Improved Accessibility

Accessibility is key to an effective and inclusive web. Be like Bosch: everybody counts, or nobody counts.

When testing a design for accessibility, emulators don’t cut it. In my experience, Safari has some of the most reliable accessibility settings, especially when it comes to Media Queries like prefers-reduced-movement.

Further gains in this field mean that Safari continues to be an essential tool for QA tests.

Reduced Resets

Finally, I want to throw up my hands to celebrate the reduced number of non-standard CSS appearance settings.

For years we’ve been prefacing our style sheets with elaborate resets like Normalize, designed to undo all the assumptions browser developers make about design and the UI preferences of their engineers.

Safari 16 has reportedly “Removed most non-standard CSS appearance values.” How effective this is and how much we can rely on it given the other browsers on the market remains to be seen. However, like many of Safari 16’s changes, it’s a step towards a browser that’s on the developers’ side instead of an obstacle to overcome.

Source

The post Exciting New Features in Safari 16 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

We had a great talk with Bjarne Stroustrup, the designer and original implementer of C++. He is also the author of The C++ Programming Language (Fourth Edition), A Tour of C++ (Second Edition), Programming: Principles and Practice Using C++ (Second Edition), and many popular academic publications.

Enjoy the full interview below!

Source de l’article sur DZONE

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