Blog – Best practices for subtitle text for images

More important than writing, size and style is the use of spaces. You need to make sure your readers know that this text belongs to the image as a caption. You can use 2em between the image, the narrow label, and the surrounding text to see if the effect of the caption belongs to the image or not.

From what I've seen, subtitles usually make up 80% (0.8em) of body text size. However, if you make the text smaller, reading is even more difficult for users. And that affects the readability. A second style change with italics would mean exaggerating the desired effect. Decrease the size or italicize the text.

The meaning of italics is often the emphasis of the word or phrase. If you make the text smaller, send the message that this text is less important. Decide what message to send before changing the style or size.

Website Design – Best Practices for Asynchronous User Experience?

Can anyone suggest some good examples and resources for asynchronous user experiences?

I'm working on a web application that needs to process bills asynchronously to improve usability. We'd like to allow them to submit an invoice, receive feedback that it has been received, and process it asynchronously in the backend. The current synchronous transmissions require a lot of processing and may take several minutes or more to integrate with another system. I'm not lost that waiting 1-2 minutes in a web UI is horrible.

Note: We can perform a sufficient number of checks to reduce the likelihood of errors in the submissions. However, there is still a low probability of errors.

I'm looking for real-world examples of asynchronous user experiences for processing where it's done well. I know, for example, that does this for processing orders. You will receive an answer to your order almost immediately, but it is still pending. There is still a low probability that an issue is out of print or another problem exists. You communicate this by notifying by e-mail and in the user interface.

Users often submit multiple invoices in the same session. Therefore, we want you to be able to quickly transfer invoices in quick succession as follows:

  • Make it clear that the submission has been received, but more processing is needed.
  • Surface defects clear
  • Improve the perception of speed
  • Provide a more natural and improved UX workflow.

Examples or resources that are specific to this type of UX topic are highly appreciated.

Javascript – "alert", "confirm" and "prompt" are considered bad practices?

This is not a bad practice, because good or bad practice is an excuse for those who do not know what they are doing. Think about it, what does good practice mean? A cake recipe someone dictated to you because someone practiced it and said it was good. What is this helpful for learning?

These windows are modal, so the question starts from a false premise. You can replace this modal with another created with HTML / CSS and edited with JS. In this way you can give it the desired look and edit it very flexible. This is a better way than using what browser are you ready In some scenarios it looks better and improves the user experience, in others it does not make a big difference and just requires more work.

Doing the right thing and the wrong thing for the scenario is the only good practice you should follow. So you need to understand the whole thing, gain experience to make the right decisions, and not follow any ready-made prescriptions. Most of the software we see there is bad because it follows good practices and seems incoherent, but that's exactly what people use for the wrong task the right tool. This is not a horrible case, but there are many bad cases, but it works and people do not realize how bad it is. How many times have you seen something bad and wondered why someone you know did and did?

It's ugly, but why should it be a bad practice? If it does not meet the need, that's the wrong tool and not a bad practice. It is the requirements that must determine this. Do you need to maintain an aesthetic side pattern? Do you need a different behavior than you have ready? Can you do something better and well done? These are factors in deciding to use your own mechanism. If it gets worse, that's good.

Online test with 80 questions Best Practices

If you're using a long form, you should use different methods to get a good user experience. For very long forms with many questions, try the following:

1. Group your questions into sections

Sort your questions into manageable parts. If you have a long form, you probably ask questions about many different topics. Your goal is to identify these topics and break your questions into easy-to-understand sections.
Once you have sections, you can more clearly map where a person is at the time of completing the form. Filling in sections also allows for small rewards in a long and probably not fun form completion process.

2. Make the position visible

A key difference between short and long forms is that they require a different user experience. Short forms are completed in minutes, long forms can take hours – and participants are expected to take breaks between sessions. For long forms, you'll need to include a "You're here" feature that will help you orient the person while providing the ability to estimate the time remaining.

To make the place visible, you want to show where the person filling the form is. You can use a percentage to complete symbols, page numbers, breadcrumbs, load bars, a stepper, and so on. There is no standard design for it. You need to find a system that works with your form. In your case, this two-tier tree indicator is fine. tree

3. Set expectations before the start

To prepare the person to start the form, give them as much context as possible. This increases the completion rate for people starting the process.
Questions that an introduction might answer are:

  • Why is the person filling out this form?
  • How long should the completion of the form last?
  • What is the schedule for the next steps?
  • Do you need to prepare something in advance (eg have a driver's license or prepare documents)?
  • What happens to the information provided?
  • Who has access to it, how is it used, how are privacy standards respected?
  • Does filling in the form cost money?
  • Do not surprise the people with the costs.

4. Save each question automatically

When the user fills out a long form, some problems may occur. Connection issues, session expiration, etc. Make sure each step of the user is saved and does not need to be rerun.

5. Do not ask questions out of focus

Hide fuzzy questions around the fuzzy question only for very short forms. This design is suitable for a simple form such as a survey, but is not suitable for long-form online questionnaires.
When I fill out a form like this, I feel my heart rate increase because I'm trying to figure out if I have the impression that the form is shorter than it really is.

This kind of opacity reduction for fuzzy questions can not be accessed. People will inevitably feel they should read the blurry text before it gets into focus. Since the colors of the text on the screen do not meet the standards for the accessibility of contrasts, the readability is reduced, which causes both difficulties for the person who tries to read the fuzzy question, if they can even see them.

hide other questions

Best Practices – MySQL Sharding. Application layer vs. MySQL layer

I'm going to create shards in the MySQL table, and I'm stuck if I should choose application-level sharding or let Mysql handle it.
I mean, if I should find out which shard to query at the application level, or if I pass the query to the MySQL driver and let it decide.
I've read about some pros and cons of both [insert the link description here1, but I can not draw a conclusion.

My personal opinion is to choose MySQL drivers. Open for discussion.
Please share your views / experiences on the same.

Architecture – Structure AWS environment according to best practices

I recently completed "AWS Certified Cloud Practitioner 2019" from aCloud.Guru. Essentially, the course will provide an overview of the various AWS services and some best practices for use, as well as some practical examples that you will learn to work with, for example: Deploy a WordPress site for AWS.

Finally, I have some knowledge now, but no "real" experience. My goal is to provide a standard installation of nopCommerce 4.20 and provide an environment that would be useful to a small business.
I want to use AWS Organizations and have four accounts that manage specific tasks. Each account has the minimum privilege to perform its role.
– dev would only have been written in global (to pass logs)

What I want to know is what I should consider to work if I miss something? Or is there anything that you would normally expect in this kind of setup and that I have missed in my design?

Should the security have a separate account and, if so, what services should I include?

Finally, I try to keep the costs as low as possible, so I have to keep an eye on the costs so that some options are defiantly lacking. I want to imitate a business environment, but this will come from my own pocket, so my options have some limitations

Enter image description here

Technology – Good Health Practices for Photographers

Like many other professions. Photographers usually suffer from certain health issues that are related to the way we use the first and most important part of our equipment: our body.

Manufacturers are making great strides in this regard, but photographic equipment can still be very heavy if it is to be worn all day, especially if it includes telephoto and zoom lenses with large aperture. This daily muscle effort can lead to tendonitis, shoulder girdle contracture, lumbar spine loading, torticollis, and related disorders. After a whole day at work, I usually even feel my fingers are tense!

There are also health issues related to excessive use of the view to which this answer sheds some light.

I'm just trying to carry most of my gear on a belt or in a hip bag rather than in a backpack. Avoid letting the camera hang on my neck, try to rest and stretch my muscles whenever I can, and keep regular physical exercise, but do not really know much about health and anatomy, so just go for my intuition and the general recommendations of the trainers / doctors.

Are there any advanced practices and / or exercises to minimize the negative impact of photography on our bodies?

Customization – Best practices for designing layouts for highly configurable / customizable web applications

As the title implies, I am looking for best practices or guidelines for designing highly configurable web applications.

We are currently redesigning our HR application completely. There is no screen without discussion about the problem of configuration options. Customers love that they can tailor our platform to their needs. In fact, it is one of our main selling points. But how can you ensure an aesthetically pleasing layout if you do not know how many buttons are displayed or how many options are available? Or how complex the search masks will be … you get the idea.

Examples of configuration options are:

  • QuickActions (one button per action)
  • QuickFilters (check boxes that enable a number of filters to suit your needs)
  • Labels and pictures
  • Visibility of certain features or content
  • etc.

Our current strategy is to make sure that standard configuration looks and feels good and we even validate our designs through user testing. However, since the configuration options are almost unlimited, we may not be able to test for all cases. We try to account for extremes or corner cases, but can not ensure that the layout is still fine on "bad" or overly configured pages.

Are there best practices or design guidelines on how to ensure a minimum of usability and aesthetics? How do you deal with this kind of "blur" in your layout? Any experiences or resources are highly appreciated!