Articles

Few things are more important to a web designer or developer’s chances of success than having the proper workflow. The term “workflow” applies to the set of standardized steps you or your company uses to create, test, and deploy designs or products.

Over the years, as development processes have evolved, so too have the workflows experts use to bring their ideas to life. The MVP workflow, or “Minimum Viable Product” strategy, is one of the most popular options in 2022.

Here’s what you need to know about the MVP workflow and how it differs from some of the other standard workflows developers may be used to.

What is the Designer/Developer Workflow?

As mentioned above, the designer/developer workflow is a series of steps used by experts in the web design world to achieve a creative goal. The process includes the steps taken to start a project, evolve it, and finish it. Since software is never developed without tools, the technology you’ll access throughout the development process is also considered in most workflows.

An example of a standard development workflow might look like this:

  • Scaffolding: This is the stage wherein you start your new web project, creating a git repo, downloading libraries, preparing file structures, and completing other tasks to make sure your product is ready to roll out into the world.
  • Develop: This is where you’ll spend most of your time writing code for your application or website. The development process may include various specific tools and support from other staff members.
  • Test: In this stage, you examine the functionality of your code to determine if everything works as it should. If there are errors or issues, you can go back and develop fixes to the potential problems. Your code may go through the development/test process several times before you can move to the next stage.
  • Integrate: This is when you merge the code for your part of the development process with the rest of the team. You can also integrate your code into websites and existing apps at this point. If you’re working solo, you can skip this process.
  • Optimize: You prepare all your assets for use on a production server during the optimization stage. Files are generally optimized to ensure your visitors can view your site easily or access your applications with ease.
  • Deploy: In the deployment stage, developers push code and assets up into the server and allow for changes to be viewed by the public.

What is MVP? (Minimum Viable Product)

Now you know what a developer workflow looks like, you can begin to assess the concept of the “MVP” workflow. The term “MVP” stands for Minimum Viable Product.

The idea of “Minimum Viable Product” applies to a range of industries, from education to healthcare and government entities. This term comes from lean start-up practices and focuses heavily on the value of learning and changing during the development process.

When you adapt your workflow to focus on an MVP, you’re essentially adjusting your focus to a point where you can create a stripped-back version of something new – like an app or a website. The MVP is built just with the core features (the minimum), so you can bring the idea to market and test it as quickly as possible.

For instance, if your goal were to create an attractive new website for a client, an MVP would focus on implementing the crucial initial tools, and nothing else. While you may create checkout pages, product pages, and other aspects of the site, you wouldn’t populate it with content or start experimenting with bonus widgets and apps.

So, how does this offer a better alternative to the standard workflow?

Simply put, an MVP workflow is quick, agile, and easy. The idea is you can validate key concepts with speed, fail quickly, and learn just as fast. Rather than having to build an entire app and almost start over from scratch every time you find an error, you can race through the iteration and development process.

MVP workflows are also highly appealing to start-ups and entrepreneurs hoping to validate ideas without a massive amount of upfront investment.

Examples of MVP Workflows

Still confused? The easiest way to understand how an MVP workflow works is to look at an example.

Let’s start with a conceptual example. Say you were building a voice transcription service for businesses. The desired features of this product might include the ability to download transcription, translate them into different languages, and integrate them into AI analytics tools.

However, using the MVP approach, you wouldn’t try to accomplish all of your goals with your software at once. Instead, you’d focus on something simple first – like the ability to download the transcripts. Once you confirm you can do that, you can start a new workflow for the next most important feature for the app.

One excellent example of a company with an MVP approach is Airbnb. The entrepreneurs behind this unicorn company, Joe Gebbia and Brian Chesky, didn’t have a lot of cash to build a business with at first. They had to use their own apartment to validate the idea of creating a website where people could share their available “space” in a home or apartment with the public.

To begin, Airbnb only created a very basic website, published photos of their property, and waited to see the results. After discovering people were genuinely interested in renting another person’s home, the company was able to begin experimenting with new ideas to make a site where people could list their properties for travelers.

The Pros and Cons of an MVP Workflow

There are a lot of benefits to the MVP workflow – particularly when it comes to gaining agility and developing new products quickly. However, there are downsides too.

Pros

  • With an MVP approach, you can maximize your learning opportunities and create a more innovative, successful product at speed. You get to test every step of the way.
  • You release iterations or versions of your product quickly, which means you discover problems faster, allowing you to quickly solve these issues.
  • You build on the benefits of customer fans, “evangelists” in the marketplace who are keen to help your product or service grow.
  • An MVP gives you more freedom to try out unique ideas and “risks” you might otherwise avoid with a traditional workflow.
  • Because you’re focusing on creating only the “minimum viable product,” you don’t have to spend a fortune on initially setting up your workflows.

Cons

  • Agile work with an MVP flow requires a lot of effort in collecting constant feedback from customers and releasing iterations.
  • You’ll need to dedicate yourself to releasing many small and frequent product releases on a tight schedule.
  • You might have to revise the functionality of your product or app a number of times.

Creating Your MVP Workflow

If you believe an MVP workflow might be effective for you, the first step is defining your “Minimum Viable Product.” The app, website, or product you design needs to align with your team’s strategic goals, so think about what your company is trying to achieve at this moment – before you get started. If you have limited resources, or specific purposes, like improving your reputation as a reliable company, now might not be the right time to develop a new MVP.

Ask what purpose your minimum viable product will serve and what kind of market you’re going to be targeting. You’ll need to know your target customer to help you test the quality and performance of each iteration of your MVP. Once you know what your ideal “product” is, ask yourself what the most important features will be.

You can base these decisions on things like:

  • User research
  • Competitive analysis
  • Feedback from your audience

For example, if you’re producing an AI chatbot that helps companies to sort through customer inquiries, the most important “initial feature” may be the ability to integrate that bot into existing websites and apps owned by the company.

MVP Approach Guidelines

Once you have your hierarchy of most valuable features for your minimum viable product, you can translate this into an action plan for development. Remember, although you’re focusing on the “minimum” in development, your product still needs to be “viable.” In other words, it still needs to allow your customer to achieve a specific goal.

  • Review your features: Reviewing your prioritized product requirements and the minimum level of functionality you can deliver with each of these “features.” You need to ensure you’re still providing value to your customer with anything you produce.
  • Build your solution: Build your minimum set of features for the product or service. Remember to build only what is required. You can use methodologies like the agile or waterfall method to help guide your team during this process.
  • Validate your solution: Release your offering into the market, and ensure you have tools in place to gather feedback from early adopters. Use beta programs, focus groups, and market interviews to understand how your solution works for your customers and where you can improve on your current offer.
  • Release new iterations: Based on what you learn from your target audience, release improvements to your product quickly. Use your validation strategies to collect information from your audience with each release.
  • Review again: Go back to your product requirements and desired features and start the process over again, this time focusing on the next most valuable functionality. Over time, the value of your minimum viable product will increase.

Using the MVP Workflow Approach

While the MVP workflow approach might not be the right solution for every development or design team, it can work very effectively in the right circumstances. The MVP approach doesn’t minimize the importance of understanding market problems and delivering value. Instead, the focus is on delivering quick value that gradually increases and evolves over time.

As many developers and designers know, the most useful form of product validation in most cases is real-world validation. When your customers have had an opportunity to use a product on a day-to-day basis, they can provide much more effective feedback.

Just keep in mind that committing to the MVP approach also means changing your workflow and committing to iterations – otherwise, other features may never be completed. You’ll need to be willing to work quickly and in small bursts without getting too heavily caught up in one feature or functionality.

 

Featured image via Pexels.

Source

The post How to Get Started with the MVP Workflow first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

Visual Studio Code is a great code editor that comes with JavaScript and TypeScript features like basic refactoring out of the box. However, its true strength is an outstanding extension marketplace. There are extensions for almost anything you might want to do in an IDE (Integrated Development Environment), and they can make VS Code many times better.

Unfortunately, it can be time-consuming to find the right extensions and configure VS Code. Many developers prefer the out-of-the-box experience that IDEs such as Webstorm provide. This blog post shows how Visual Studio Code extensions can help you enhance the IDE experience for JavaScript. It covers:

Source de l’article sur DZONE

Réduire l’empreinte carbone d’un produit nécessite une vision de bout en bout de son cycle de vie. Pour cela, il est nécessaire de casser la barrière IT existant entre la conception et la supply chain. SAP et Siemens proposent des intégrations avancées entre PLM et ERP. Avec Atos, ils s’allient pour aider les industriels à relever le défi climatique.

Les industriels sont confrontés à un triple défi : proposer des produits toujours plus complexes, dans des délais toujours plus serrés, tout en réduisant leur empreinte carbone. Le bilan de la COP26 de Glasgow est sans appel : constater la réalité du changement climatique ne suffit plus, il faut agir. Histoire de compliquer la situation, la raréfaction des matières premières s’ajoute aujourd’hui à l’urgence climatique.

Le sujet de l’empreinte carbone est crucial pour trois raisons principales :

  • Les clients sont toujours plus nombreux à demander comment sont fabriqués les produits qu’ils achètent et quelle est leur empreinte carbone. Une empreinte que l’entreprise doit être capable de mesurer.
  • La législation devient de plus en plus contraignante, poussant ainsi les entreprises à être plus vertueuses en matière d’environnement. Mais également à mettre en place des outils montrant la réalité de leurs actions dans ce domaine.
  • La RSE met en exergue le sens des responsabilités des entreprises. La green line (empreinte écologique) devient progressivement aussi importante que la top line (revenus) et la bottom line (marges).

Une problématique à traiter de bout en bout

« L’Union Européenne veut réduire ses émissions de gaz à effet de serre de 55% en 2030 et vise la neutralité carbone en 2050. 2030, d’un point de vue industriel, c’est presque aujourd’hui, constate Denis Goudstikker, Teamcenter Business development Executive chez Siemens Digital Industry Software. À ce jour, un tiers des entreprises se sont fixé un objectif zéro émission, mais seulement 9% de ces entreprises ont réellement lancé des actions en vue de les réduire. »

Pour qu’un produit ait un impact environnemental minimal, il faut l’optimiser de bout en bout, de la conception à la production en passant par son utilisation et son recyclage. « La plupart des entreprises se concentrent uniquement sur les émissions liées à leur activité, explique Olivier Everaert, Head of Green PLM chez Atos. Elles ne prennent pas en compte l’ensemble du cycle de vie du produit et de sa chaîne de valeur, ce qui mène à des résultats sous-optimaux. Il faut penser en termes de réseau, où tous tendent vers un but commun, du fournisseur de matière première à l’industriel… et jusqu’au consommateur. »

« La réduction des impacts environnementaux commence dès la conception du produit, enchaîne Bruno Hemery, Head of Siemens partnership, SAP France. Elle se poursuit avec les approvisionnements (matières premières, emballage, etc.). Puis lors de la fabrication : produire mieux permettra d’avoir moins de rebuts en bout de chaîne et de consommer moins d’énergie. La logistique peut aussi être optimisée, en regroupant par exemple les approvisionnements de plusieurs fournisseurs (parfois concurrents) devant livrer un même client. Il faut également être capable de mieux connaître l’usage des produits, ce qui permettra de les améliorer au fil des versions. Enfin, d’autres éléments sont à prendre en compte, comme le recyclage et l’économie circulaire. »

Les actions en faveur de l’environnement ne sont pas forcément des investissements coûteux. Réduire la quantité de déchets générée lors de la production se traduit ainsi par une diminution des besoins en matière première et donc un abaissement des coûts de revient.

SAP et Siemens, artisans de la continuité numérique

Pouvoir prendre en charge l’ensemble du cycle de vie d’un produit nécessite de casser une barrière dans le système d’information de l’entreprise, celle séparant la conception, pré carré du PLM, et les fonctions finance, achat, production, vente, prises en charge par l’ERP. « Il faut décloisonner ces deux mondes, afin de mettre en place une continuité numérique, confirme Bruno Hemery. L’information pourra ainsi circuler dans les deux sens, la conception influant sur la supply chain et – partie innovante – la supply chain et l’usage du produit pouvant influer plus directement sur la conception. La continuité numérique permet également de s’assurer que l’information est identique des deux côtés. »

Le partenariat annoncé le 14 juillet 2020 entre SAP et Siemens vise à donner corps à ce concept de continuité numérique. Il s’est traduit par la livraison de nouvelles intégrations entre les offres de Siemens et de SAP. « Cette intégration fine entre nos deux plateformes donne une compréhension de l’ensemble du cycle de vie d’un produit permettant de s’assurer dès sa conception que l’on va dans la bonne direction, tout en restant compétitifs. La clé de la réussite est d’être capable d’amener des processus vertueux et compétitifs, » résume Denis Goudstikker.

Par ailleurs, la réduction de l’empreinte carbone passe souvent par de l’innovation. C’est le cas par exemple lorsqu’un constructeur automobile adopte des motorisations électriques ou à hydrogène. « La continuité numérique permet de créer des conditions favorables à l’adoption d’innovations, tout en maîtrisant le risque et en préservant la compétitivité de l’organisation, poursuit Denis Goudstikker. C’est un environnement qui permet de se préparer à n’importe quel scénario. »

Des ateliers pédagogiques animés par Atos

Atos sait diagnostiquer la chaîne de valeur des entreprises, afin de les aider à mettre en place une supply chain durable. Chaîne de valeur dont la visibilité et la transparence seront assurées par la mise en place d’une continuité numérique. La grande majorité des entreprises restent toutefois au début de cette transformation. Atos propose des ateliers pédagogiques gratuits leur permettant de mieux comprendre les applications pratiques de cette approche.

« Nous présentons une vingtaine de cas d’usages qui couvrent l’ensemble du cycle de vie d’un produit et nous montrons quelle est leur contribution sur l’empreinte carbone, détaille Olivier Everaert. Lors du premier atelier, les participants sont invités à nous faire remonter leur avis sur ces cas d’usage. Sont-ils applicables à leurs métiers ? Semblent-ils valables ? Peuvent-ils être améliorés ? Le second atelier permet de faire une plongée sur quelques cas d’usage sélectionnés, puis de discuter avec les participants de leur feuille de route de transformation. »

Ces ateliers d’idéation mettent l’accent sur le codéveloppement des cas d’usages et la cocréation des trajectoires de transformation des entreprises. Un premier brainstorming avant le passage à l’action…

The post SAP, Siemens et Atos : la continuité numérique comme réponse au défi climatique appeared first on SAP France News.

Source de l’article sur sap.com


A Short Background

I characterize myself as a slothful engineer due to the specificity of my behavior: rather than duplicating, mentioning different issues in my project, and setting up new appliances to be more efficient, I would be grateful for the opportunity and get back on my way.

My first job as a professional started in the entertainment industry where I had to do my projects really quickly before the deadline was over; moreover, it was not possible to use high-end tools or spend a lot of time researching and integrating peculiar properties. That is the reason why I decided to spend some overtime hours researching and showing my teammates how a few specific tools could improve the process, and show how to have a greater impact in solving technical problems.

Source de l’article sur DZONE

Every year, at this time, blogs like this one like to try and predict what’s going to happen in the year ahead. It’s a way of drawing a line under the archive and starting afresh. A rejuvenation that, as humans, we find life-affirming.

Ten years ago, I would have had high confidence in these predictions — after all I was eventually right about SVG adoption, even if it took a decade. But the last few years have shown that web design is tightly interwoven with the muggle world, and that world is anything but predictable.

So as we look at what might occur in the next year (or five), think of it less as a set of predictions and more as a wishlist.

Last Year’s Predictions

When I write this post every January, I like to keep myself honest by glancing back at the previous year’s predictions to gauge how accurate (or not) my predictions have been.

Last year I predicted the long-term trend for minimalism would end, WordPress would decline, cryptocurrency would go mainstream, and then hedged my bets by saying we’d make both more and fewer video calls.

Gradients, maximalism, and the nineties revival pulled us away from minimalism. It’s still popular, just not as dominant.

WordPress is still the biggest CMS in the world and will continue to be for some time. But the relentless grind of no-code site builders at the low end, and being outperformed by better CMS at the high end, mean that WordPress has passed its peak.

Over-inflated predictions for BitCoin reaching $100k by December 2021 turned out to be a damp squib. In the end, Bitcoin only tripled in value in 2021. However, with micro-tipping and major tech companies moving into the arena, it’s clear digital currency arrived in the public consciousness in 2021.

And how could I be wrong about more but also fewer video calls? So I’m calling that my first clean sweep ever. With that heady boast, let’s take a look at the next twelve months.

What Not to Expect in 2022

Do not expect the Metaverse to be significant in anything but marketing speak. Yes, the hardware is slowly becoming more available, but the Metaverse in 2022 is like playing an MMORPG on PS5: theoretically, great fun, until you discover that absolutely none of your friends can get their hands on a console.

Ignore the blog posts predicting a noughties-era retro trend. All those writers have done is looked at the nineties-era trend and added a decade. Fashions aren’t mathematical; they’re poetic. Retro happens when people find a period that rhymes with present-day hopes and fears. After the last couple of years, if we revisit a decade, it’s likely to be the late-forties.

Finally, don’t expect seismic change. Material design, parallax scrolling, and jQuery are still with us and are still valid choices under the right circumstances. Trends aren’t neat; they don’t start in January and conclude in December.

5 Web Design Predictions for 2022

Predictions tend to be self-fulfilling. So we’ve limited ourselves to five trends that we believe are either positive or, at worst harmless. Of course, there are no guarantees, but if these come to pass, we’ll be in good shape for 2023.

1. The Blockchain is Coming

Underpinning the cryptocurrency industry are blockchains. In simple terms, they’re a set of data that can be appended to but can’t be edited or deleted. Think of it as version control for data.

As with most technology, the first wave has been a way to make a fast buck. However, the exciting development is blockchain technology itself and the transformative nature of the approach. For example, Médecins Sans Frontières reportedly stores refugees’ medical records on the blockchain.

Imagine the Internet as a set of data, editable for a micro-fee, and freely accessed by anyone anywhere. Instead of millions of sites, a single, secure, autonomous source of truth. Someone somewhere’s working on it.

2. Positivity & Playfulness & A11y

Even before world events descended into an endless tirade of grim news, time was running out for dull, corporate, geometric sans-serif design.

We added gradients, we added personality, we embraced humor. And contrary to the established business logic, we still make money. Over the past few years, there have been extraordinary efforts by designers and developers to examine, test, and champion accessibility, and thanks to them, inclusive design is no longer reliant on the lowest common denominator.

In 2022 you can get experimental without obstructing 10%+ of your users.

3. Everything Green

Green is a fascinating color, the primary that isn’t (except in RGB, when it is).

Green has the same visual weight as blue, is substantially more flexible, and yet to date, has been radically underutilized in digital design.

Green has a prominent cultural association with the environment. At a time when tech companies are desperate to emphasize their ethical credentials, marketing companies will inevitably begin promoting a brand color shift to green as a quick fix for all those dumped chemicals, strip mines, and plastic-filled seas.

We’ve already seen earthy hues acquire popular appeal. At the other end of the vibrancy scale, neons are popular. Green spans both approaches with everything from calm sages to acidic neons.

In 2022, if you’re looking for a color to capture the moment, look to green.

4. Hero Text

A picture is supposed to be worth 1000 words, although I’m not sure anyone has actually tried to measure it. The problem is that sites increasingly rely on stock images, so the 1000 words that we’re getting may or may not accurately reflect 100% of our message.

In 2022, a handful of well-chosen words will be worth more than an image, with hero images taking a back seat to large hero text. This is aided by a number of minor trends, the most notable of which is the willingness of businesses to look beyond the geometric sans-serif to a more expressive form of typography.

Reading through the prediction posts on sites other than this, almost everyone agrees on large hero text replacing images, which virtually guarantees it won’t happen. Still, at the start of 2022, this seems to be the direction we’re taking.

5. Bring the Noise

One of the unexpected consequences of the past couple of years has been a renewed connection with nature. The effortless complexity in nature is endlessly engaging.

We’ve already begun to popularise gradients — there are no flat colors in nature — and the next logical step is the addition of noise.

In visual terms, noise is the grainy texture that sits so beautifully in vector illustrations. Noise has dipped in and out of trends for years, hampered a little by the leap in file size it creates. However, with WebP and Avif file types, noise is now usable on production sites.

Designing in 2022, when in doubt, throw some noise at it.

 

Featured image via Unsplash.

Source

The post 5 Big Web Design Predictions for 2022 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

Every day design fans submit incredible industry stories to our sister-site, Webdesigner News. Our colleagues sift through it, selecting the very best stories from the design, UX, tech, and development worlds and posting them live on the site.

The best way to keep up with the most important stories for web professionals is to subscribe to Webdesigner News or check out the site regularly. However, in case you missed a day this week, here’s a handy compilation of the top curated stories from the last seven days. Enjoy!

Pure CSS NavBar Responsive Examples

A List of Games for Bored (and Curious) Designers

Free Black and White Images

5 Exciting Web Design Trends for 2022

22 Inspiring Web Design Trends for 2022

How to Find Business Ideas

What’s the Right Font Size in Web Design?

Unbelievable 100-year-old Font Can Be Read Both Backwards and Forwards

Top Web Design and UI Trends for 2022

Material Design 3

Source

The post Popular Design News of the Week: December 27, 2021 – January 2, 2022 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

The Cloud is ubiquitous: any company looking to ramp up quickly will provision its compute, networking, and storage with its preferred cloud provider, and get started rolling out their products.  That makes total sense from a business perspective.  The Cloud has simplified development and automation exponentially over the years, and emerging tech such as AI and IoT will only accelerate this.  

However, the catch is that the very same foundational architectures which drive the Cloud’s efficiency, flexibility, and cost benefits ultimately also are its weakest links from a security perspective.   The result is the daily march of headlines we all read about: ever larger and deeper breaches of data and systems.

Source de l’article sur DZONE

Maps are a fascinating method for delivering content. At their best, they can create an intuitive way of presenting information and interacting with it. This is the advantage that digital maps, through mobile apps and websites, have over print maps and images where no interactivity is possible.

But it’s important to understand that more data ≠ better experiences. We all now have so much data available to us through multiple services that, arguably, the greatest challenge isn’t sourcing information but filtering it out. We can only handle so much information input before we become overloaded. This issue risks being omnipresent with maps. There are so many potential points of interest on a map that it’s essential to be clear about what needs to be exposed to users.

Also, UX design, map design, and user interface are all critical. While maps can be a powerful way of drawing people in, if end-users feel that you didn’t even consider the visual design, they’ll ‘bounce off’ your site or app in moments.

Common Use Cases

When are maps useful, and what problems do they solve? Let’s dive right into the most common use cases for maps used in web design.

Navigation and Direction

Like Google Maps shows, navigation and direction are arguably the classic case study for interactive maps. You are in one place and need to get to another. You can enter your destination, your current location, and the map will present suggestions for getting there. You can select the method of travel and adjust desired departure or arrival times. But you need to understand first what functionality your users need. How these options are exposed to users is a critical piece of UX design.

Also, if users are searching for options such as somewhere to eat, it’s not so straightforward. Then, how your map handles panning in real-time as users swipe around a city is going to be a big issue.

Showing Relationships and Trends Geographically

This is something that you’ll see in every election in any western country. We’re all used to seeing maps that give us a state-of-play for which state or seat is held by which party. Then, we might see projections based on voter intentions and projected voting swings deriving from that. Then, exit poll data can be projected with the map updated on an ongoing basis until the final result is confirmed.

The capability to do this is essential because if a static map were used, it’d be out of date any time a new poll was released. Also, voting intentions can change over a campaign, so such maps need to be dynamic. Of course, such maps are only as accurate as the available data, as the US 2016 election map showed.

Show Points of Interest

As mentioned previously, there’s a lot of data that can be exposed to map users. However, that doesn’t automatically mean that it should be. Usability is key. For example, when you look at a map, you’ll typically first see key points of interest. Which points of interest are going to be presented to you can vary.

One variant is zoom level. If your map is currently showing an entire city, the level of detail the map presents is deliberately limited. You’ll see districts, large roads, or geographic features such as rivers. If more detailed information were presented, users on mobile devices, in particular, would be overwhelmed. Even at this level, you’ll notice typography differences. These can include the city name being in bold or the names of different areas in capital letters. So the level of detail is coupled with the scale of the map. Zooming in a few notches will expose significant points of interest, such as museums. Zooming in to specific districts will reveal restaurants, coffee shops, and universities. This visual hierarchy is a critical way of managing the exposed level of information.

But information is still being abstracted away. It’s not until you tap on the museum that you’ll see information on opening hours and busy times. This is also typically presented with user photos and reviews. Context is also taken into account, so you’ll start to see local hotels and restaurants. So it’s not just individual points of interest that are important, but the connections between them.

6 Tips For Improving Interactive Maps

What are the challenges of creating effective maps, and how do people address the data overload problem? We’ll answer this question and go over the must-know aspects of map creation.

1. Ensure Security and Brand Trust

GDPR or General Data Protection Regulation. This is a critically important European law that extends a wide range of legal protection to European citizens regarding personal data. It’s not possible here to cover the full extent of the law, but here are some quick key points:

  • Consent is required for the processing of personal data; it cannot be assumed
  • You need to have a retention policy for information that’s capable of identifying people

Be aware that the latter doesn’t just cover commercial purposes. Research students have to submit GDPR forms that address what kind of data they’re sourcing and how they’ll be retaining it.

But the most crucial context is commercial. If a business suffers a data breach, it can be fined up to 20 million euros or 4% of annual worldwide turnover in the preceding financial year, whichever is greater. Therefore, any business storing data that could identify their customers will need to assess risk and compliance. Remember: it’s 4% of worldwide turnover, not EU turnover.

Also, anything of your business that you expose to your customers or users is an extension of your brand. Therefore, you need to assess your maps for brand compliance too. If you have primary brand colors and your map doesn’t abide by them, that’s a very poor look. Source the color hex codes directly from your brand team and involve them in design.

2. Use the Appropriate Type of Map

It’s also important to consider what type of map is most appropriate for your use case. Think carefully about what your users need, what you’re trying to communicate, what information you need to present, and how best to present it.

For example, points of interest style maps in a tourist app will be way more helpful than heat maps: people want to know where something is, key data like opening hours, and how to get there. A heat map showing the number of visitors to each attraction or area of a city is unlikely to be useful to tourists. However, it could be useful to the attractions themselves to map their visitors by heat map over time. This could help larger museums chart which exhibits are most popular.

Transport for London is charting passenger movement on the London Underground by detecting when a device with Wi-Fi comes into range and then passes out of range. They’re using this to understand overall user journeys and movements within individual stations to better manage disruptions.

3. Avoid Pop-Ups

It should go without saying by now that auto pop-ups are despised. It doesn’t matter what they’re doing or what they’re offering; an unwanted pop-up can only get in the way. The level of impact is even greater on a phone where pop-ups take up even more screen space.

Given this, many users close them without even reading them. So if you’re using pop-ups, don’t kid yourself. You’re likely just irritating users and increasing the likelihood that they’ll ‘bounce off’ or uninstall.

4. Avoid Auto-Geolocation

Auto-geolocation sounds incredibly convenient but can result in some real problems. For example, if there are any bugs with auto-geolocation, you could get false results. If someone connects through public building Wi-Fi, you could get false results. If they’re connecting through a VPN then, unless you get the user’s IP address and check if it’s the exit portal of a VPN, you could get false results.

The problem is most significant with mobile maps. If a map user is looking at a points of interest map, they likely have a specific and immediate use. This means it’s in their best to get the most accurate results possible. So why not just ask them?

Precision and Accuracy

These terms have specific meanings in geolocation. ‘Precision’ is the exactness of the data. ‘Accuracy’ is how closely the information on a map matches the real world. So you want precision and accuracy to be spot on, or data risks losing value. This applies not just to the gathering of data but to the representation of it. For example, if you have street-level data but your maps don’t present individual streets, then any representation of data on that map is likely to have poor accuracy. That map might succeed in abstracting irrelevant information but presenting an imprecise and inaccurate view.

5. Avoid Map Legends as Much as Possible

In many cases, primarily points-of-interest maps, they’re just not needed anymore. An essential part of user experience design isn’t just visual hierarchy but information hierarchy. You can mouse over on a desktop or laptop to get the essentials of a location, e.g., the museum’s name and its opening hours. On a mobile device, you can tap on that location to get the essentials, and you can tap on another location to move on; you don’t even have to press back. Given that, a legend would get in the way. So this simple piece of information design solves information overload issues.

As with all rules, there are exceptions. A good one is a heat map where a density of what’s being measured needs to be communicated. It doesn’t matter what the data is; it just needs to be something where mapping provides greater insight, especially if it informs decision-making. Sales is an excellent example for a national or multinational company. Of course, weather forecasting can make use of literal heat maps.

6. Accessibility Compliance

Not everyone has perfect eyesight. Even if someone has excellent vision, they could still be colorblind (8% of men and 0.5% of women are). Given that, take the W3C’s accessibility standards into account and treat them as a baseline or minimum barrier to entry for compliance. You shouldn’t feel good about the possibility of excluding 8% of your potential audience or customers. Ensure you keep your UX designers involved and don’t shy away from creating senior-friendly web designs.

Put simply: imagine if you could appeal to a new demographic that’s not catered to. If your competitors ignore them, you could give them a real reason to choose you instead by taking some straightforward steps. If your competitors are catering to them, you also need to. If you don’t, you’re just giving potential customers a big reason to ignore you.

Conclusions

The key takeaway is that there’s far more to creating good maps than just good cartography. That can be critical, too, though this may vary depending on the use case.

This will be a team effort because your map will involve data sets, design decisions, and, yes, cartography. You’re going to need to involve brand and IT too. So think about design principles and development methodologies.

First and foremost, what are your users’ needs? If you haven’t done any user research or taken the time to understand the customer journey, are you adding anything or getting in the way? It’s easy to see the department that requested the map as stakeholders, but you should probably view your users as stakeholders too.

This sounds complex, but as you hopefully now appreciate, a map is probably more complicated than you thought.

 

Featured image via Pexels.

Source

The post The UX of Maps in Web Design first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

Every day design fans submit incredible industry stories to our sister-site, Webdesigner News. Our colleagues sift through it, selecting the very best stories from the design, UX, tech, and development worlds and posting them live on the site.

The best way to keep up with the most important stories for web professionals is to subscribe to Webdesigner News or check out the site regularly. However, in case you missed a day this week, here’s a handy compilation of the top curated stories from the last seven days. Enjoy!

Logo Design Trends 2022: The Future of Logos

Paperback – Simpler and Tidier Alternative to Wiki Pages

10 Captivating Examples of the Liquid Metal Effect in Web Design

Micro Digital Tools

Master Typography for Free with Google Fonts Knowledge

Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround

40+ Most Notable Big Name Brands That are Using WordPress

Pixel Patterns

Top Web Design and UI Trends for 2022

WordPress 5.9 Delayed Until January 2022

Source

The post Popular Design News of the Week: December 20, 2021 – December 26, 2021 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot