Loginet was the first product that I worked on. I started freelance work with the company when I was working for Aspired and there was a lot of work to be done. Before my arrival, the position of designer in the company hadn't existed. The system was written in JS using only standard components.
I was faced with an enormous and difficult task. It was necessary to develop consistent principles and patterns for the entire system. I am proud of the results I managed to accomplish. Unfortunately, I cannot post all prototypes of the interface as I'm only able to show what does not fall under the NDA.
I was faced with an enormous and difficult task. It was necessary to develop consistent principles and patterns for the entire system. I am proud of the results I managed to accomplish. Unfortunately, I cannot post all prototypes of the interface as I'm only able to show what does not fall under the NDA.
Loginet
Navigation
Initially, it might seem that design navigation is a simple matter, however this is not the case. I believe that the more frequently a component or block is used, the more proficiently it should be designed. As a result, this process becomes more difficult.
The question arises once a user encounters the tabs that duplicate the browser tabs: "Why are they needed?"
This hasn't been done on a whim, but it is a technical limitation that needed to be satisfied. I had to design navigation that would allow all portal pages to be opened in one browser tab. The familiar pattern of browser tabs solves this problem perfectly.
The question arises once a user encounters the tabs that duplicate the browser tabs: "Why are they needed?"
This hasn't been done on a whim, but it is a technical limitation that needed to be satisfied. I had to design navigation that would allow all portal pages to be opened in one browser tab. The familiar pattern of browser tabs solves this problem perfectly.
Design system
From the very first day, I realised that such a project cannot be worked on without a design system. To my regret, Figma had not yet had a variant function and I had to solve this problem. The challenge was to strike a balance between the number of unique components and the weight of the file they affect. I wanted to make a system that allows one to design on the fly without requiring a lot of learning for new team members. Now, with the Variants tool, I would do it differently. However, even with such a result, the system solves its problems and speeds up the design process tenfold.
Each element has a description and a list of instructions for usage, but as previously mentioned, I cannot post these materials.
Each element has a description and a list of instructions for usage, but as previously mentioned, I cannot post these materials.
Dashboard
The dashboard is a delicate matter. I made this dashboard in the beginning of working on the product. Before I left Loginet, I had worked on a new dashboard, which greatly changes the way people use the product but that is another story. I included an old version of it to show how I work with graphs and colour.
Creation of Transportation
Transportation is the key process of the Loginet system and almost all business processes are somewhat connected with it. Following the link, you can see the clickable prototype. Usually, for each prototype, I record a video for documentation, so that the development team can quickly dive into the essence of the block's functionality. This video is available by clicking on the link on the first page of the prototype.
About my experience with the product
Working for Loginet has taught me a lot. Before Loginet, I thought that working on a product was a boring, monotonous routine. I was under the impression that designers had to work obediently, like slaves on a galley, and were subordinate to the product owner. To my surprise it turned out to be a creative process, where you, the designer, really influence how the product looks and works. This is an incredibly interesting and exciting process. For me, it's like an economic strategy, where you have to endlessly improve your city for the game to continue.
At my previous job, I interacted with both developers and customers, but service development is a different matter. When you work on a product, your immersion in the business process is much deeper. As no-one knows the entire system as a whole, you have to communicate with a huge number of people from different departments and levels. After a while, you no longer understand who you are (designer, marketer or developer). In essence, this is product design.
It is difficult to overestimate the experience that I gained after making a billion mistakes. Having all this new knowledge behind me, I would like to try to build something like Loginet again but from the very beginning.
At my previous job, I interacted with both developers and customers, but service development is a different matter. When you work on a product, your immersion in the business process is much deeper. As no-one knows the entire system as a whole, you have to communicate with a huge number of people from different departments and levels. After a while, you no longer understand who you are (designer, marketer or developer). In essence, this is product design.
It is difficult to overestimate the experience that I gained after making a billion mistakes. Having all this new knowledge behind me, I would like to try to build something like Loginet again but from the very beginning.
