CEO at Idealogic.Design

Seasoned professional in UI/UX and Product Design with over 10 years of experience, specializing in crafting intuitive user experiences and innovative product solutions. Experienced across diverse industries including Fintech, Blockchain, Aviation, Social Media, AI, Real Estate, and Education, delivering impactful, user-centered designs. 

Skilled in solving complex challenges with strategic design thinking, enhancing user satisfaction, and driving business growth. A proactive and adaptable approach is emphasized, focusing on comprehensive problem-solving and service design. 

Extensive industry knowledge and attention to metrics contribute to organizational success, ensuring that every design project not only meets but exceeds expectations. As a Senior Product Designer, UX/UI insights are integrated with strategic business goals to deliver high-quality, impactful products, continuously improving design delivery and maintenance for users.

Viktor Zhytomyrskyi

One of my favorite parts of designing interfaces is when the correct solution feels… a bit illegal 😅

Because if you follow pure “logic”, you end up with UIs that look clean on paper… and fail the second a real person touches them.

Hover hints are a perfect example. If they appear instantly, they become clutter. If they wait a beat, they become information.

So you add a tiny delay. Slightly less “responsive”. Way more humane.
Same story with menus + submenus. The “logical” version says: hover changes the moment your cursor leaves the item.

But humans don’t move in straight lines. They move diagonally. They hesitate. They overshoot.

So you add an invisible safe zone that “forgives” the path to the submenu. It looks out of logic. And it feels amazing.

When you design submenus, do you go with (A) hover+intent, (B) click-to-open, or (C) both, depending on density?

The original idea is by Siyam Afroz from this Linkedin post -  https://lnkd.in/gSu6zDPY

#uxdesign #productdesign #interactiondesign #uidesign #menu #submenu #uxui #userexperience

Senior Product Designer | UI/UX Designer | UX Researcher @ HP

The hardest part of a design system isn’t building it.

It’s staying creative inside it.

At first, design systems feel like freedom.

Everything is cleaner.
Faster.
More consistent.
Buttons are ready.
Spacing is defined.
Patterns are documented.

Then one day, you get a genuinely good idea. Something that would actually make the experience better for the user. And suddenly the design system becomes that pink character from the meme standing behind you like:

“Yeah… but we don’t have a component for that.”

That’s where the real struggle starts. Because now you have to choose:

Do I force the idea into the existing system and lose what made it good? Do I create a new pattern and make the system heavier?
Or do I spend the next hour trying to convince everyone that this is not “breaking consistency,” it’s solving a real problem?

I think a lot of designers live in that tension. A design system should give you structure. But it shouldn’t take away judgment. It should speed up the obvious things so designers have more energy for the non-obvious ones. Because real products are messy.

Users don’t behave like component libraries. Edge cases don’t care about your token setup. And the best solutions are not always the most reusable ones on the first try.

The strongest design systems I’ve seen were not rigid.
They had principles.
They had logic.

But they also had room to grow.

That’s the balance I’m always chasing:
Enough consistency to scale,
Enough flexibility to still design something smart.

What’s harder on your team right now: keeping consistency or keeping flexibility?

#uxdesign #productdesign #designsystems #uidesign #uxcommunity #designthinking #figma #productdesigner #uxstrategy

The more “simple” a product feels, the more terrifying the logic behind it usually is.

A lot of design education teaches us how to design interfaces. Modern product work forces us to design systems. That gap gets bigger every year.
This Slack notification map is a great example of why. Because on paper, the problem is tiny: decide whether to notify the user. But real products never operate on paper. They operate in context. And context multiplies everything.

The message type matters.
The device matters.
User preferences matter. 
Timing matters. 
Subscription state matters. 
Presence matters. 
Overrides matter. 
History matters. 
Priority matters.

So the challenge is no longer just: what should the UI look like? It becomes:
What logic deserves to exist behind the UI? 
How do we keep that logic understandable? 
How do we keep it from collapsing under exceptions? 
How do we make it feel human instead of robotic? 
How do we make users trust it?

That last one is huge.

Because in modern products, trust is often designed through behavior, not visuals. A product that shows the right thing at the right moment feels smart. A product that interrupts at the wrong moment feels selfish. A product that ignores context feels broken. And users are incredibly sensitive to that.
So when products get more complex, I don’t think designers just need “better UX skills.”

I think we need stronger decision design. Stronger systems thinking. Better collaboration with PMs and engineers. More comfort with flows, logic trees, states, and rules.

Because the most important design choice might not be what appears on screen.

It might be whether something appears at all.

#ProductDesign #UXDesign #UX #UIDesign #SystemsThinking #InteractionDesign #DesignSystems #ProductStrategy #UserExperience #DesignLeadership

The name “edge case” is kind of misleading. Because for a lot of users, those are normal cases.

They skip steps. 
They tap too fast. 
They close the app and come back.
They’re on an old device. 
Their Wi-Fi is dying. 
The data is messy.

And in production, it goes from “very nice” to “why are people stuck here?” real fast.

I don’t even think edge cases are “extra work” anymore. They are the work. Because users don’t remember the moment when everything went right. They remember the moment when things went weird… and the UI either helped them or abandoned them.

Do you have a “we didn’t think of that” edge case story?

#UXDesign #UIDesign #ProductDesign #UserExperience #EdgeCases #InteractionDesign #Usability #UXResearch

Qwerty.Software

My passion for programming exists to this day and I find enjoyment in building middle and large scale projects that have exceptional value and work well. I'm unique in that in addition to being a respected technical leader I'm still active in developing software on a daily basis.
My background has led me to participate in building a company (Qwerty.Software) that provides custom software development to growing firms. We have successfully helped small companies that are growing fast and established businesses that needed systems and software built quickly and reliably. Also, by partnering with a company having software development focus and a high level of accountability our clients are more able to focus on their own core competencies.

I'm interested in connecting here and will accept invitations to connect.
Also, you can reach out directly via email -partners@qwerty.software.

My duties:
- Platform selection and technical design 
- Provide options
I never say "that's impossible" or "we'd never do that." I'm trying to find the solution and impossible things become possible
- Help with platform selection and technical design
Well, that’s obvious. If your plan is to create a highly iterative lean product, you'd better be using foundational tools that make that easy rather than hard. My work is to make others work easier rather than harder
- Own the development methodology
In this aspect, I'm responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases
- Grow technical leaders
I believe that every CTO being a great architect, evangelist, interface designer or incredible debugger must want to share his/her knowledge with the team to increase the average knowledge skill of it. So do I.

Chief Technology Officer

K2 Partners

Co-Founder

Youslim

Foodle Inc.

Foodle is a solution for eating out abroad. It helps people at a language barrier find dishes, understand menus and make orders in the best local restaurants.
Foodle is your personal food advisor and waiter abroad. It will help you to find a restaurant, understand its menu and make an order in Chinese, French, Arabic or any other language you don't speak.
Unlike Foursquare, Yelp or Foodspotting that help users find a place to eat, Foodle caters specifically for foreigners to ensure they are properly understood and served on the spot.
We believe that public services should be equally available to everyone disregarding the language they speak, but they are not. Foreign guests often face language barriers that impair their experience. The English language should be a solution, but it is still not for 2 out of 3 Europeans that don't speak it, as well for millions of visitors from China and other developing countries. With over a billion international tourists in 2013 and over 280 million monthly TripAdvisor visitors, international travelers are a valuable yet underserved share of restaurant-goers.  People love using their native language, and we let them do just that by making different restaurants’ menus available in multiple languages. It is a single app that makes you understand what you are about to eat, and order it with a couple of clicks.
To achieve that we gather menus both from restaurants and users, translate them and display in the app for free. Being the all-menus-in-one-place service, we count on generating revenues from paid analytics (the most popular meals in the menu/in the city, place's actual and would-be clients behavior, etc.) and Foursquare-like advertisement.  You can check us out at justfoodle.com

Co-founder & CTO

AMgrade GmbH

Responsibilities:
- PM trainee
- Reporting and managing activities of developers
- Ensuring that all stakeholders are updated - Providing weekly highlight reports
- Helping project teams to move through the various stages and decision points of the program
- Helping clients meet and exceed their goals
- Maintaining credibility with the customer at a high level
- Provided escalation route for any outstanding issues
- Understanding and creating technical specifications
- Implementation of Agile Planning

taplio

The Battle

Viktor Zhytomyrskyi

Yevhenii Seliutin

Followers

Posts

Engagements

Likes

Performance ScoreViktor Zhytomyrskyi's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Viktor Zhytomyrskyi

Yevhenii Seliutin

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Viktor Zhytomyrskyi's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreViktor Zhytomyrskyi's LinkedIn Performance