The heart, which did not know the pain of disappointment, did not know the joy of flight

© The Host (Stephenie Meyer)

This post was inspired by a recent post by Alexander Pogman25 about the pain of front-endrs and the uneasy story of love and hate between fronts and front-end designers. The story is as old as the world, and the main reason for the pain is really the lack of dialogue and the unwillingness or inability to be on the other side of the layout. Unwillingness may be the result of professio- nism, inability – insufficient skill. You can work with both.

I think that in the not too distant future, No-Code / Low-Code products will do their job, and UI / UX and front-end developers will no longer know what it is when the eye twitches in sync with the button in the web version of the layout. What now? To make it easier for the designer and the front to get along with each other, and to make their collaboration easier, we came up with Quarkly.

The co-founders of the project – Sasha and Artem – are not hearsay familiar with all the sores that arise during communication between the designer and the front. Alexander is a full stack developer, Artem is a UI / UX developer. In this case, as they say, the cards came together.

At Quarkly, we strive for the notorious Low-Code and even No-Code when building sites and web applications, and when we launch a catalog-marketplace of ready-made components in release, this will become generally very possible.

As of February 2021, we do not yet have a marketplace, but we have the entire basic set of tools both for a designer who is used to making layouts / prototypes in popular design tools (Figma, Framer) and for a developer.

Already now, a ready-made layout from Figma is not easy, but you can quickly drag it into Quarkly, below I leave a tutorial with Russian and English subtitles:

How Quarkly can help relieve pain

Designers often fail to understand the pain of fronts, because they create layouts in tools that do not allow them to feel the layout in dynamics. Plus, with Quarkly, collaboration takes less time.

In order not to count the length of the working cycle in elephants, monkeys and parrots, let’s clearly compare two situations:

1. The designer and the front work, as they are used to doing it each – the designer creates the layout in Figma, then the front transfers everything to the code;
2. The designer and the front jointly create a project at Quarkly.

And let’s not forget that in addition to speed, we are also interested in what pain points can be bypassed. Dangerous moments I will refer to on a scale of 1 to 5 pinky bangs on a dresser.

A good specification in a live environment (it doesn’t matter if it’s a large company or a small studio) is very important. A good specification is not a guarantee, but a weighty claim that you can avoid pain in the process.

Incomplete specification – time bomb. Maybe everything will be all right if the lunar cycles converge, Mars in the constellation Aries will not mind, and the designer and developer will understand each other as needed.

Another dangerous moment is when the layouts are drawn by a designer who does not understand what will happen to them next in the next stage. It is hardly necessary to explain where and what kind of pain can happen here.

Finally, the saddest thing is when such mockups get to the developer. It will hurt him, it will hurt the designer, to whom he will constantly come with questions.

The designer’s layout is already code. The developer only needs to test complex logic that the designer cannot handle.

Our YouTube channel where you can find helpful tutorials: watch

Our chat in telegram: https://t.me/quarklyapp