Articles

6 Simple Steps to a Career in Web Design

,

No one likes talking about money. Most of us got into web design because we loved it. But the fact is, we’ve all got bills to pay.

If you’re a half-decent designer or a relatively competent developer, then there’s no reason you can’t make a living as a web designer. Here are six simple steps towards earning a living using the skills you already have.

Step 1. Freelance Work

Many individual bloggers and small company owners require websites to reach a larger audience. You might exploit this opportunity to begin a side business as a freelancer.

One of the most efficient ways to start is to look through employment networks and online classifieds. Eventually though, you’re going to need a portfolio. Building your freelancing company website could be your first opportunity to demonstrate your web development talents. As you embark on new projects, this website can display client testimonials that demonstrate your expertise. Ensure that it’s up to date, relevant, and follows current design trends. Also, make sure your website is linked to your social media profiles. 

Even though you are responsible for finding clients, you have a great deal of flexibility: you can choose your working hours and exercise more freedom and creativity. However, you’d still be accountable for your work and have to execute assignments on time to keep your clients satisfied.

It’s also important to remember that you’ll have to keep track of your taxes and other financial paperwork. Furthermore, you would not have a standard employer who will provide you with health insurance and other perks.

Step 2. Specialize

Today’s market offers a wide choice of web design services most suited to our needs. From designing and building custom websites to creating social media websites to managing SEO and PPCs, web design services offer various services. And while it is beneficial to have a general understanding of what all these services entail, it is always good to identify and refine your expertise. Becoming proficient in one aspect of web design will give you more confidence and direction regarding the kind of work you would like to do.

Allowing yourself to land repeat clients specializing in one type of service will make it easier for you to create processes in your business to complete work accurately and quickly. These processes will also help you build a team should you need one.  

Step 3. Networking Effectively

You should leverage social networking sites such as LinkedIn, practical tools for engaging with colleagues and potential customers. Ensure your profile is updated with all the services offered and all talents you deliver. Make sure you include links to any past projects you’ve worked on. There’s also a career board on LinkedIn that can help you avail yourself of many freelance projects. Registering and engaging with relevant organizations can allow you to acquire more visibility.

Freelancers are generally matched with modest design/development assignments through these websites. Although some developers heavily vouch for them, getting work from these websites when you’re just starting may be exceedingly challenging, considering most of your time will be exhausted in securing billable employment. 

Step 4. Start Your Own Blog or Podcast

Blogs and podcasts are an excellent way to organically acquire fresh customers and other relevant parties. A well-written blog is a terrific source of amusement and knowledge for potential clients. Aside from showcasing your services, a blog may be used to earn money in various ways. Once the blog grows large enough, you can incorporate backlinks, ads, or author-sponsored content. Many popular blogs eventually grow into fully-fledged businesses.

When you start a blog from scratch, it can take a long time to see a return on investment. Consider producing freelance articles for a blog with a constant stream of traffic to help you get started. This will enable you to demonstrate your skills while also getting compensated for them. 

Step 5. Work at a Design Agency

Working at a design agency or in-house could be an ideal option if you desire a more traditional job title. It also helps you build your portfolio with larger and more recognizable clients than those you can secure as a freelancer.

Instead of stressing about the management side of things, you can focus on serving clients and constructing websites with this approach. You wouldn’t have to look for new clients, and you’ll get all of the paid benefits that regular employees get. However, you’d have to work under strict supervision and have less creative control over your projects. There will also be harsh deadlines looming over your shoulder. And this procedure will also set a wage ceiling for you. On the other hand, obtaining employee insurance and securing a source of income can be very reassuring.

Step 6. Start Your Own Agency

Once you feel you have enough relevant experience and are confident in your abilities to perform and manage things well, you can start your own agency. It’s like freelance work, but on a much larger scale. The flexibility to employ others to do your work is the fundamental advantage of having your own agency. You can recruit additional designers and eventually recruiters to help you secure clients.

Having your own agency allows you to do the work you want and how you desire. As a general rule, start as a freelancer and gradually create the foundations for your agency as you gain expertise. You can eventually automate the entire process with hard effort and an innovative business plan.

You must actively network with other people in your business and reach out to new clients in addition to working on your skills. If you can create a solid customer base and take measured chances with your chosen projects, you can procure meatier projects and become prominent in the corporate sector.

 

Featured image via Unsplash.

Source

The post 6 Simple Steps to a Career in Web Design first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Blink a LED on a Raspberry Pi With Vaadin

,

As I’m becoming a senior developer in terms of age, I’ve transitioned from one language to another. One of my main interests has always been clean, easy-to-understand UIs (User Interface). That journey started for me with Director (to create multimedia CD-ROMs), Flash website animation, and Flex Rich Internet Applications (= « Flash on steroids »). When I started developing with Java over 10 years ago, we had some projects with the early versions of Vaadin and JavaFX. As I went on with serverside applications, I only continued with JavaFX for some personal and side projects and loved the way you can create a UI both with XML (FXML actually) and code, exactly the same approach I loved with Flex. Since then, my love for Java and JavaFX only grew and it’s still my major programming environment.

But JavaFX has one missing piece: running it in the browser… Yes, JPRO can do this, but it needs a license and a dedicated server. And yes, there are some projects ongoing to bring JavaFX fully to the browser, but they are ongoing and not mature yet… Let’s look at another approach: Vaadin Flow and run it on a Raspberry Pi to control a LED and show the state of a button.

Source de l’article sur DZONE

/par

How to Scale Your Design Process and Improve Handoff

,

It’s something every design team dreams about – a better design process and handoff procedure. Your design team is not alone if you are looking for a better solution.

Imagine what your workflow would look like if you could forgo the struggles of image-based technology, design and handoff with accurate components that have interactive features. Projects in the design phase will look more like final products and, most importantly, interact like final products. 

Let’s imagine a new design process together.

Challenges of an Image-Based Design Process

Here’s what we all know – image-based design tools provide pictures of components in the visual form but lack the interactivity and conditions that exist in the end-product. There’s not a high level of functional fidelity there, and it can cause confusion among design teams and rework.

These tools require you to redraw the fundamental components and design with boxes and rectangles, which takes too much time and can create a disconnect between the design and development teams. 

Further, you don’t fully maximize the potential of a design system because of inconsistencies between code-powered systems that developers use and these image-based systems for designers. There’s an innate gap between maintaining the environments and creating consistency in components. 

The final and maybe most difficult challenge with an image-based design process is in usability testing. You just can’t test an image the way you can working components. If the prototype is not interactive enough, you lose valuable feedback in the testing process. Functional fidelity is a must-have design and development tool in 2022. 

Iress, market-leading financial software, had many of these same problems in its design system process. You can probably relate to its story, which includes a designer and engineer who aren’t entirely on the same page, hit the deadline and have to deliver, and then get customer feedback. The result was a lot of extra headaches and work. 

But there is a better way: Import all user interface components into a code-powered design system in sync with a design tool so that your team can work in harmony to build, scale, and handoff projects with ease. 

Scale Design With Accurate Components

Here’s what most design and development teams want en route to building products: Accurate components with built-in interactivity, states, and conditions. No redrawing boxes and rectangles; no trying to figure out what states and interaction should be.

And if you can do it with ten times the speed and agility? Now you’re really in business. 

“It used to take us two to three months just to do the design. Now, with UXPin Merge, teams can design, test, and deliver products in the same timeframe,” said Erica Rider, Senior Manager for UX at PayPal. “Faster time to market is one of the most significant changes we’ve experienced using Merge.”

The time and workflow savings come from the ability to maintain only one environment as a product team. Rather than image-based tools, a code-powered design system that will push updates to components as the design evolves is the modern way to work. This workflow can also eliminate duplicate documentation so that your team has a single source of truth for whole product teams. 

Now you can be more agile in the design process and scale. And as Rider hinted at, there is a solution already available in UXPin Merge. 

Scalability with accurate design components has other benefits as well. 

Teams can onboard people faster because the design system is in the design tool. There’s less searching for answers with drag and drop-ready building blocks. New team members will find more success and be more valuable to the team quicker due to fewer inconsistencies and errors. 

Testing also gets a boost as you scale with a single source of truth. You can actually create better usability tests with a high-fidelity, functional version of the prototype, allowing users to leave more valuable and detailed feedback that can improve your product in the early stages. 

Better Handoffs Start Here

As you imagine a better design process, take it one step further. Better handoffs are a goal for most teams. 

An interactive component-based design tool can eliminate the need for multiple iterations of the same meeting to explain how a prototype works. Everyone can see and interact with it for themselves with accurate, true components that ensure the prototype works the same as the product. 

Designers will feel more like their vision is making it into the final product, and developers have a better idea of how to work. Everyone has the exact same components written in code. Thanks to the single source of truth, devs can speed up as they build the product because they start with components that include production-ready code.

A typical design to developer handoff might have multiple steps: Create vector design elements, create a model for interactions, and then send the prototype with documentation. Not to mention the meetings that are required to make sure everyone is on the same page.

In a model with interactive component elements, the developer handoff is fast and easy; they create a prototype with true components and all the built-in properties. The developer copies the JSX code and pastes it into his tool to build the final product. All the component properties and their coded interactions already exist in the source code. This is possible because the source of truth is the code itself, the source code.

Quick Tool Solution and Technical Use

This solution to this common challenge is not somewhere in the future; it’s already here.

UXPin, a code-based design tool, has Merge technology, which allows you to bring all interactive components into UXPin. Then you can use your own, or the open-source library with the ready-made building blocks to get products ready faster.

Here are just a few of the things you can do with Merge by UXPin:

  • Integrate your developer’s storybook to use it as a single source of truth (works for all frameworks)
  • Import design system components from a dev’s Git repository, such as GitHub, Bitbucket, GitLab, or others (works with React)
  • Work with the built-in MUI library
  • Add the npm component package to UXPin on your own (no developer required)
  • Design with the confidence that your work can be ideally reflected by developers
  • Create and share a library of interactive components

Summary 

Say bye-bye to redrawing rectangles – build more accurate prototypes easier and end-products faster with Merge by UXPin.

Now is the time to solve one of your biggest design challenges while upgrading and scaling the design process and improving handoffs. 

Merge by UXPin is user-friendly and made for scalable projects of almost any size. The line between design and development blurs with quicker product release and a fully-interactive solution. Request access today.

 

[– This is a sponsored post on behalf of UXPin –]

Source

The post How to Scale Your Design Process and Improve Handoff first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

GitOps Takes DevOps Teams To Higher Levels of Maturity

,

Stream-Aligned and Platform Teams

The 2021 State of DevOps report identifies two types of teams as the way high-maturity teams organize themselves: stream-aligned teams and platform teams. The idea of a « platform » or « internal developer platform » is fundamental to GitOps. While a GitOps pipeline begins with committing code to a Git repository, it is made possible by a platform that paves the way for that new code to move in an automated way from the repository to a production environment.

The platform is how the Ops team provisions resources such as cloud services, storage, service meshes, and security and monitoring tools in a ready-made template. These templates are created even before they are needed and made available to any developer within the organization. The big shift due to this is that developers need not raise a ticket for the resources they need: they can pick a ready-made template and deploy their code in a matter of minutes. From the Ops side, they have peace of mind knowing they have configured this template and that it follows security protocol by default. It does not require developers to separately configure security for deployments.

Source de l’article sur DZONE

/par

What is the “Minimum” in Minimum Viable Product?

,

“Minimum Viable Product,” or “MVP,” is a concept of agile development and business growth. With a minimum viable product, you focus on creating the simplest, most basic version of your product, web application, or code possible.

Minimum viable products include just enough features to attract early adopters and validate your idea in the early stages of the development lifecycle. Choosing an MVP workflow can be particularly valuable in the software environment because it helps teams receive, learn from, and respond to feedback as quickly as possible.

The question is, how exactly do you define the “minimum” in MVP? How do you know if your MVP creation is basic enough while still being “viable”?

Defining the Minimum Viable Product: An Introduction

The concept of “Minimum Viable Product” comes from the Lean Start-up Methodology, introduced by Eric Ries. The purpose of MVP is to help companies quickly create versions of a product while collecting validated insights from customers for each iteration. Companies may choose to develop and release minimum viable products because they want to:

  • Introduce new products into the market as quickly as possible;
  • Test an idea with real users before committing a large budget to product development;
  • Create a competitive product with the use of frequent upgrades;
  • Learn what resonates with the target market of the company;
  • Explore different versions of the same product.

Aside from allowing your company to validate an idea for a product without building the entire concept from scratch, an MVP can also reduce the demand on a company’s time and resources. This is why so many smaller start-ups with limited budgets use the MVP and lean production strategy to keep costs as low as possible.

Defining an MVP: What your Minimum Viable Product Isn’t

When you’re building a Minimum Viable Product, you’re concentrating on developing only the most “essential” features that need to be in that product. For instance, you might be building a shopping app for a website. For the app to be “viable,” it would need to allow customers to search through products and add them to a basket or shopping cart. The app would also need a checkout feature and security components.

However, additional functionality, like the ability to send questions about an item to a customer service team or features that allow clients to add products to a “wish list,” may not be necessary straight away. Part of defining a minimum viable product is understanding what it isn’t. For instance, an MVP is not:

  • A prototype: Prototypes are often mentioned alongside MVPs because they can help with early-stage product validation. However, prototypes are generally not intended for customers to use. The “minimum” version of a viable product still needs to be developed enough for clients and users to put it to the test and provide feedback.
  • A minimum marketable product: An MVP is a learning vehicle that allows companies to create various iterations of an item over time. However, a minimum marketable product is a complete item, ready to sell, with features or “selling points” the company can highlight to differentiate the item from the competition.
  • Proof of concept: This is another similar but distinct idea from MVP. Proof of concept items test an idea you have to determine whether it’s attainable. There usually aren’t any customers involved in this process. Instead, companies create small projects to assess business solutions’ technical capabilities and feasibility. You can sometimes use a proof of concept before moving on to an MVP.

Finding the Minimum in your MVP

When finding the “minimum” in a minimum viable product, the primary challenge is ensuring the right balance. Ideally, you need your MVP to be as essential, cost-effective, and straightforward as possible so that you can create several iterations in a short space of time. The simpler the product, the easier it is to adapt it, roll it out to your customers, and learn from their feedback.

However, developers and business leaders shouldn’t get so caught up focusing on the “Minimum” part of Minimum Viable Product that they forget the central segment: “Viable”; your product still needs to achieve a specific purpose.

So, how do you find the minimum in your MVP?

1. Decide on Your Goal or Purpose

First, you’ll need to determine what your product needs to do to be deemed viable. What goal or target do you hope to achieve with your new product? For instance, in the example we mentioned above, where you’re creating an ecommerce shopping app, the most basic thing the app needs to do is allow customers to shop for and purchase items on a smartphone.

Consider the overall selling point of your product or service and decide what the “nice to haves” are, compared to the essential features. For instance, your AR app needs to allow people to interact with augmented digital content on a smartphone, but it may not need to work with all versions of the latest AR smart glasses.

2. Make a List of Features

Once you know the goal or purpose of your product, the next step is to make a list of features or capabilities you can rank according to importance. You can base your knowledge of what’s “most important” for your customers by looking at things like:

  • Competitor analysis: What do your competitors already offer in this category, and where are the gaps in their service or product?
  • User research: Which features or functionalities are most important to your target audience? How can you make your solution stand out from the crowd?
  • Industry knowledge: As an expert in your industry, you should have some basic understanding of what it will take to make your product “usable.”

3. Create Your Iterations

Once you’ve defined your most important features, the next stage is simply building the simplest version of your product. Build the item according to what you consider to be its most essential features and ask yourself whether it’s serving its purpose.

If your solution seems to be “viable,” you can roll it out to your target audience or a small group of beta testers to get their feedback and validate the offering. Use focus groups and market interviews to collect as much information as possible about what people like or dislike.

Using your feedback, you can begin to implement changes to your “minimum” viable product to add more essential features or functionality.

Understanding the “Minimum Viable Product”

Minimum viable products are evident throughout multiple industries and markets today – particularly in the digitally transforming world. For instance, Amazon might be one of the world’s most popular online marketplaces today, but it didn’t start that way. Instead, Jeff Bezos began purchasing books from distributors and shipping them to customers every time his online store received an order to determine whether the book-selling landscape would work.

When Foursquare first began, it had only one feature. People could check-in at different locations and win badges. The gamification factor was what made people so excited about using the service. Other examples include:

  • Groupon: Groupon is a pretty huge discount and voucher platform today, operating in companies all around the world. However, it started life as a simple minimum viable product promoting the services of local businesses and offering exclusive deals for a short time. Now Groupon is constantly evolving and updating its offerings.
  • Airbnb: Beginning with the use of the founders’ own apartment, Airbnb became a unicorn company giving people the opportunity to list places for short-term rental worldwide. The founders rented out their own apartment to determine whether people would consider staying in someone else’s home before eventually expanding.
  • Facebook: Upon release, Facebook was a simple social media tool used for connecting with friends. Profiles were basic, and all members were students of Harvard University. The idea quickly grew and evolved into a global social network. Facebook continues to learn from the feedback of its users and implement new features today.

Creating Your Minimum Viable Product

Your definition of a “minimum viable product” may not be the same as the definition chosen by another developer or business leader. The key to success is finding the right balance between viability – and the purpose of your product, and simplicity – or minimizing your features.

Start by figuring out what your product simply can’t be without, and gradually add more features as you learn and gain feedback from your audience. While it can be challenging to produce something so “minimalistic” at first, you need to be willing to release those small and consistent iterations if you want to leverage all the benefits of an MVP.

Suppose you can successfully define the meaning of the words “Minimum” and “Viable” simultaneously with your new product creations. In that case, the result should be an agile business, lean workflows, and better development processes for your entire team.

 

Featured image via Pexels.

Source

The post What is the “Minimum” in Minimum Viable Product? first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Exciting New Tools For Designers, February 2022

,

One of the most talked-about digital elements of the new year leads our roundup of tools and resources this month – NFTs. The NFT landscape seems to be exploding right now and that includes tools for designers to get in on the game as well.

Here’s what is new for designers this month…

Zero Code NFT

Zero Code NFT offers an advanced no-code tool to simplify the smart contract development and deployment process, allowing you to launch your NFTs with no previous coding experience. It includes a smart contract wizard that supports Ethereum, Polygon, Fantom, and Avalanche, with Solana and others underway. The tool has a waitlist if you are interested.

54nft

54nft is a tool to create a customized NFT store. It is a complete commerce platform that lets you start, grow, and manage an NFT business. Create and customize a store, publish and mint assets on available blockchains, and sell. The tool is free but charges a transaction fee on sales.

NFT-Inator

NFT-Inator is a free toolkit to accelerate the design and development of procedurally generated NFT projects. Create custom and randomized designs, test layer combinations, and export images and metadata for Solana, Ethereum, and Polygon.

Gradientos

Gradientos makes finding gradients that work with your design easy. Pick your colors and see the gradient live on a demo website with common UI elements.

Web Almanac

Web Almanac is an annual state of the web report from HTTP Archive. It is a comprehensive report on the state of the web, backed by real data and trusted web experts. The 2021 edition is comprised of 24 chapters spanning aspects of page content, user experience, publishing, and distribution.

Straw.Page

Straw.Page is a new take on website builders. It is a super simple builder that you can use to create websites from your phone. It’s a drag and drop builder that’s highly experimental and allows you to connect via a subdomain or with a custom domain.

Placy

Placy is a simple placeholder generator. Set the size, color, and fonts and you’ll get a usable data URL to include on your website. Available and JPG, PNG, or SVG.

MetaSEO

MetaSEO is a tool to generate meta tags in one click for the best SEO of your website, rank high in search results, and appear unique when someone shares your link. It’s a no-brainer SEO tool for web designers and developers that aren’t as versed in search engine optimization.

Glitch Image Generator

Glitch Image Generator is a tool to create a trend effect of the same name. Upload an image, pick a color mode, set glitch preferences, and save it as a PNG for projects. It’s that easy.

Smoothly Reverting CSS Animations

Smoothly Reverting CSS Animations is a simple and easy-to-understand tutorial that will walk you through how to create a keyframe animation that moves smoothly. Pragmatic Pineapple explains the steps with code snippets to help you understand how to make this animated element work for you.

Alternate Column Scroll Animation

Alternate Column Scroll Animation is a nifty little tutorial and demo (with downloadable source code) from Codrops. The result is a grid layout with columns that scroll in opposite directions and a content preview animation.

Waldo

Waldo is a premium tool that can help you ship mobile apps faster with fewer bugs (that’s a win-win). The no-code testing platform allows you to upload your app to the platform, run tests, and fix any issues that might arise to help you provide a better experience when it is time to make your app live.

Monad

Monad offers an efficient and simple way to share and discover code snippets. Create an account to easily find snippets relevant to you using tags or browse and create snippets anonymously. One of the best features is the ability to work collaboratively or privately.

Doodle CSS

Doodle CSS is a simple hand-drawn HTML/CSS theme that you can snag from GitHub. It’s fun and whimsical. Practical application for a look like this is up to your style and imagination.

Pixel Patterns

Pixel Patterns is a concept pattern set that implements a function to create patterns with minimal syntax. They are in a pixel style with code snippets that you can play with.

Protodeo

Protodeo is a tool to make 3D video website templates to help show off new products or services. Just upload a few images, customize your settings, and the tool will give you a Bootstrap template with video mockups in less than a day.

VanillaList

VanillaList is a repository of handpicked JavaScript plugins and resources to save time as a developer and create high-performance web apps. And as the name implies, they are all vanilla.

The Mouse Mover

The Mouse Mover is a fun little tool with questionable ethics – it simulates real mouse movements on your PC. Plus you get the source code and won’t have to worry about going to sleep or triggering a logged-off status.

Ground Zero

Ground Zero returns Mac apps to the state they were in when first installed, without deleting the app. Fix issues and get back the default settings, or simply re-claim disk space by cleaning up data that would normally be left behind when uninstalling an app.

Alonzo

Alonzo is a premium typeface family in a modern style with high contrast stroke weights. The family includes 24 styles and with an almost condensed style fits nicely in tight spaces.

ContaneText

ContaneText is the more readable text version of the Contane typeface family. It’s a solid serif with 20 styles including Romans and matching italics. Stronger hairlines, solid serifs, and slightly more comfortable proportions make it appropriate for bold headlines, as well as for small text sizes.

Plinc Flourish

Plinc Flourish completes our roundup this month with an interesting, premium typeface that’s beautiful and functional. Part italic, part roman, this iconoclastic font is all style. It includes formal pen strokes in a taut upright framework to create a typeface that looks defiantly forward.

Source

The post Exciting New Tools For Designers, February 2022 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Popular Design News of the Week: January 24, 2022 – January 30, 2022

,

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!

16 Leading UI/UX Design Trends to Dominate in 2022

Unused Nintendo Wii Logos Include Some Serious Design Crimes

The Baseline for Web Development in 2022

60 Bootstrap Examples for Website Design

M&M’s Redesign by JKR

Frontend Predictions for 2022

Minze – Dead-Simple JS Framework for Native Web Components

Cheet – Create Developer Cheatsheets

What’s New in WordPress 5.9 (Features and Screenshots)

20 Best New Websites, January 2022

Source

The post Popular Design News of the Week: January 24, 2022 – January 30, 2022 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

3 Things Every Engineer Should Know About Inclusive Design

,

Fact: Over 26% of adults in the United States have some sort of disability. To ignore such a massive part of the population would be ill-advised for any company, legally, financially, and above all, ethically. How can you stay ahead of the curve when it comes to maintaining a progressive and responsive organization? 

We reached out to two experts – Alwar Pillai and Perry Trinier of Fable – on the topic of designing products that have inclusivity for people with disabilities at their core. Here are the 3 things they think every engineer, developer and product designer needs to know about inclusive design and how it will inevitably affect the future of their companies.

Source de l’article sur DZONE

/par

How to Get Started with the MVP Workflow

,

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

/par