Design

Looking for the right AI image generator? We review and compare top tools like Midjourney, Picsart, Craiyon, and more — highlighting their strengths, limits, and best use cases to help you make the right choice.

While video-based learning continues to rank high in the latest trends, there are a few points that are regularly overlooked in the production of learning videos, with a focus on user experience (UX) and user interaction 

People really enjoy watching videos. According to a survey conducted among consumers worldwide, respondents watched an average of 19 hours of online video content per week in 2022. And nearly half of all internet users watch online videos at least once a week.

The Challenge of Mandatory Learning
Once we had several mandatory learning courses designed to be passed successfully by all employees. Still, many of them struggled to do so. Reminder emails to all participants could not solve the issue. And that is when my team was summoned to develop a thorough plan to reduce the number of overdue courses to a minimum. Of course, we were asked to develop something fun and engaging.

Uncovering the Root Problems
While working on the project, we managed to uncover several problems with course assignments, including the fact that they were not offered just in time, there were too many of them, and all of them had different due dates, which made it impossible to remember when to complete them. Additionally, we found that the content itself was often dry and unengaging, further contributing to the lack of motivation among employees. Finally, we came up with a system of notifications that included clear explanatory reminder emails, an escalation system, and a redesign of the course content to make it more interactive and relevant to employees' daily work. The result was almost no overdue courses after system integration.

The Myth of Mandatory Fun
So the case first seemed to be about motivation and engagement, but it is actually about smart course design that allows people to worry about work tasks instead of worrying about course assignments. It's also about creating content that resonates with the learners and helps them see the value in the training.

Introduction to ADRs

ADRs are critical for documenting architectural decisions in software projects. They provide a historical record of decisions, rationales, and impacts, vital for future teams and stakeholders.

Defining ADRs

An ADR is a document capturing key architectural decisions along with their context and consequences. It helps stakeholders understand why certain choices were made during a project, promoting transparency and clarity.

This article was originally posted at Product Identity.

What comes to your mind when you hear the word Telegram?

I wouldn’t be surprised if drugs, sex, or crypto are your first associations. Throughout the years, Telegram earned a shady reputation, perhaps not strategically, but for a “good” reason.

I feel like Telegram is a mystery. On the outside, it might be perceived as a platform designed for drug traffickers, crypto scammers, and sexual abusers.

I shared this feeling when I joined the early team of Bancor in 2016, as I also joined its internal group chat, needless to say, on Telegram.

However, the app was quickly removed from my list of stigmas. Instead, I started to appreciate Telegram for its well-crafted product and care for design. From its meticulous attention to small details to have a unique brand — it stands as a dogma of an opinionated product (and a company) in many aspects. In addition, it helped me recognize the benefits of separating my private and professional lives early on.

After using Telegram extensively over the past 7+ years, I feel the urge to write about it, but this time not in the spirit of its typical news headlines.

Every day a new neural network appears and every day more opportunities are opened to designers to simplify their workflow. Someone fundamentally refuses to use them, because “there is no life in machinex and technologies”, and someone is only happy to find a way to reduce the amount of work. Personally, I belong to the second type and want to share the most detailed gait on neurons I have acquired lately. 

Getting a task from a client, UX designers tend to pay attention to the design goals, not the contents of the website/app itself. There’s something completely wrong with it because the visual part might be superb, but when it frames a vague or wordy message, the client's goals won’t be reached.

To avoid this, a UX designer should dive deeper into the content, analyze it, and restructure it in an interface-friendly way. It doesn’t mean doing the copywriter’s job, it means collaborating. The reality is that sometimes the writing team is used to praising the product (because clients like that), or there is no copywriter involved in the project at all.

Provide proof instead of opinion

An impression is more powerful when the customer can conclude the product’s benefits on their own. Instead of a colorful line of adjectives like “ultimate” or “leading” you should aim at what exactly makes the product that cool. The trick is to be precise, preferably with an example.

It feels like everything about LPs has already been said, however, I still keep seeing the same mistakes being made over and over again both by start-ups and established companies. Here are some tips, backed up by my 10-year experience as a UX/UI Director in agencies and product-led companies. These alone will give a nice increase in your conversion rate, I guarantee. 

Use a descriptive, not a salesy hero header 

Answer the questions “What?” and “For whom?” as early on the page as possible. A very common pattern is the largest copy being an inspirational abstract slogan and below it in smaller font the actual statement about what the product is and what it does. 

On average, online store users make 64 clicks before adding a product to the cart. Some clicks are useful - so-called discovery clicks that help lead to users finding a product they wish to buy, and some are useless that come as the result of poor UX. With great competition for convenience and increasingly reducing attention spans of users, each useless click reduces the number of visitors that will reach checkout.

You all know our mascot — a unicorn — many people grew fond of him! However, PVS-Studio has a supporting character who is also the antagonist of our product — a bug! Well, a bug is not omnipresent, indestructible evil. It's more like an everyday or a work-related trouble. In this article, you'll learn how we created a new character, and why he looks like a ladybug. Oh, and if you wonder why the hell he has a belly button — keep reading!

I know that my article can help a designer who spends a lot of time working and not feeling his or her growth. This article has some tips on how to start building your soft skills.

So, I finally found a moment to write a bit about how we created the water for TReload. Our basic goal was to flood all of the levels with acid - a lot of acid, as the flooded area is massive :) Here’s one of the results which we got out of this process:

PVS-Studio has a mascot that became inseparable from the brand - a unicorn. Lately we've been getting many questions about our magic steed: why the unicorn, why has he changed so much, does he have hooves, how come he doesn't wear pants, and how do we draw him. The answers are finally here, in this very article.

Attention: there will be a lot of pictures. And I mean A LOT.

In this series, I would like to discuss some reaches of Go programming language. There is no shortage of Go-Language-Of-Cloud style articles in which you can explore the great benefits that Go indeed provides. However, there are lees to every wine, and Go does not go without blemish. In this highly opinionated series, we cover some controversies and, dare I say, pitfalls of the original Go design.

We start tough and begin with the essence of Go — it's inbuild data types. In this article, we put slice to the test. Let's move a step further from the Go Tour and use slice more extensively. For example, there is no separate data type as stack in Go, because slice type is intended to cover all its usage scenarios.

Let's briefly recap the usage of the stack. We can create a stack in two seconds using a couple of paper stickers. You write "buy milk" on the first sticker and put at the desk, and then "make the dishes" on the second and pile it on the first sticker. Now, you have a stack: the dishes sticker came last but will be served first, as it is on the top of the stack. Thus, there is an alternative name for stack — LIFO, Last-In-First-Out. To compare, there is the "opposite" data structure queue or FILO — first in, first out. In programming, stacks are everywhere, either in the explicit form or in the implicit as stack trace of the execution of a recursive function.

Ok, let's put slice into use and implement stack.

English translation of Philip Ranzim's post at his blog page here. (With author's permission)

Once upon a time, my girlfriend started using Instagram. She asked me to sign up for it and subscribe to it. I tried — I couldn't do it because you couldn't register at Instagram from a desktop computer. I then thought — how weird people are. Well, what kind of fool would make a software product that can't be used with a normal computer? They won't succeed, and this Instagram will be a marginal service for a bunch of strange women, who for some reason don't like desktops.

It has only been a few years, the market has put everything in place — and the biggest fool was me. And the geniuses at Instagram predicted how and where everything would develop. Today, most of the user applications are made primarily for mobile platforms. At best, they include a universal web client, which is still optimized for mobile phones. Because users love iPhones, not computers. Business people sat down, counted, and made a decision — let's make more money, let's have mobile First everywhere.