🔀 Productivity for coders: Try to understand UX of product
Tags: ux, productivity, tutorial, beginners
Published: 2021-03-05 16:55:30

## Introduction

Hey, DEV friends! 👋 Let's talk about a topic that most programmers try to avoid when it comes to the product for which they write the _business logic_ on the backend or create the _user interface_ on the frontend.

Yes, I want to talk about **understanding** user experience (UX) of the particular product you're working with. Why? To become **more productive** in the area of responsibility for which you're writing code!

<a name="toc"></a>
### 📝 Table of contents

- [What are we developing?](#ch-1)
- [How can understanding product UX help us?](#ch-2)
- [Simple tricks on how to train yourself to pay attention to UX in your product](#ch-3)
- [Instead of a conclusion](#ch-4)

<a name="#ch-1"></a>
## What are we developing?

I can already see the chuckle on your face that "_why am I asking such a stupid question?_", but that is the question that makes a lot of sense, if you want to become **even more productive** (_and get a higher salary_) in your workplace.

So, what is your answer to this question? Let me guess, something like this:

- _I develop an interface in React.js and use such-and-such libraries_.
- _I develop a highly loaded API in Golang that can withstand a DDoS attack_.

No. Unfortunately, none of these answers are right! But which one is right? It's as simple as always. The right answer is: **I develop a product to successfully solve user problems**.

> ☝️ Stop for a moment and take it for yourself!

[↑ Table of contents](#toc)

<a name="#ch-2"></a>
## How can understanding product UX help us?

Okay, okay. I'm already anticipating the thought that's going around in the minds of some of you, my dear readers: "_but I do the backend, why should I think about UX?_".

And it's these thoughts that keep you from raising your professional level in this workplace and being as helpful as possible in solving user problems. **Because product UX isn't just about pretty icons and a red colored action button**! 

It's also processes that are _invisible to users_, such as saving intermediate results when filling out a large form or preload data in the cache that the user might need at the next moment.

Exactly the same applies to the frontend of the project. Understanding "_when_" and "_what_" to show your user is crucial for a successful UX of the whole product. If you know that it's better to show dynamic placeholders when product cards are being loaded, then suggest this option and make it so! 

Anything, that facilitates user interaction and allows you to more clearly understand "_what's going on now_", will help your product become **even more useful** to the user.

> 🔥 And that's money to business and loyalty to you as a more valuable professional, who understands the product rather than _just writing code_.

[↑ Table of contents](#toc)

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/sxdd8lct1b52loogx3ab.jpg)

<a name="#ch-3"></a>
## Simple tricks on how to train yourself to pay attention to UX in your product

1. **Start using your product**. Seriously, this may sound ridiculous, but many developers have never tried the result of their work as an ordinary user in their lives.
2. **Get more involved with the backend/frontend development team and designers**. This will allow you to look at the same part of the product from completely different angles and notice what has been hidden.
3. **Identify for yourself a few products that you really like as a user and that you enjoy using**. Try to compare the common places in these products and in yours, write down all the places you liked and the ones you would like to change and why.

[↑ Table of contents](#toc)

<a name="#ch-4"></a>
## Instead of a conclusion

And remember the most important thing: **UX depends on everyone, who works on the product**! It's in the DNA of the product from the first line of code, from the first draft of the design, from the first phrase of the presentation.

👉 How successfully your product will solve the user's problems is up to you!

[↑ Table of contents](#toc)

<a name=""></a>
## Photos by

- Álvaro Bernal https://unsplash.com/photos/QPRd_UC3nE4
- You X Ventures https://unsplash.com/photos/X8H8vPcelPk

<a name=""></a>
## P.S.

If you want more articles (like this) on this blog, then post a comment below and subscribe to me. Thanks! 😻

And of course, you can help me make developers' lives even better! Just connect to one of my projects as a contributor. It's easy!

My projects that need your help (and stars) 👇

- 🔥 [gowebly][gowebly_url]: A next-generation CLI tool for easily build amazing web applications with Go on the backend, using htmx & hyperscript and the most popular atomic/utility-first CSS frameworks on the frontend.
- ✨ [create-go-app][cgapp_url]: Create a new production-ready project with Go backend, frontend and deploy automation by running one CLI command.
- 🏃 [yatr][yatr_url]: Yet Another Task Runner allows you to organize and automate your routine operations that you normally do in Makefile (or else) for each project.
- 📚 [gosl][gosl_url]: The Go Snippet Library provides snippets collection for working with routine operations in your Go programs with a super user-friendly API and the most efficient performance.
- 🏄‍♂️ [csv2api][csv2api_url]: The parser reads the CSV file with the raw data, filters the records, identifies fields to be changed, and sends a request to update the data to the specified endpoint of your REST API.
- 🚴 [json2csv][json2csv_url]: The parser can read given folder with JSON files, filtering and qualifying input data with intent & stop words dictionaries and save results to CSV files by given chunk size.

<!-- Footer links -->

[gowebly_url]: https://github.com/gowebly
[cgapp_url]: https://github.com/create-go-app
[yatr_url]: https://github.com/koddr/yatr
[gosl_url]: https://github.com/koddr/gosl
[csv2api_url]: https://github.com/koddr/csv2api
[json2csv_url]: https://github.com/koddr/json2csv