Your product design dictionary
A cheat sheet like no other
This cheat sheet is a great source of all the design phrases and abbreviations present during the process. Gathered and curated by our UX/UI designer, Bartosz Piekarz, this pocket design dictionary is an excellent help during your cooperation with UX/UI designers.
You will learn:
the essential vocabulary used in product design
the steps involved in creating a digital product
the purpose and use of prototypes, wireframes, and mockups
techniques like interviews and usability testing to improve designs
how designers ensure functionality and consistency
examples of design elements and their applications
What's inside
No more wondering what will be created at a given stage. No more asking about such concepts or google them and digging through unclear descriptions. You have everything in one place. Right here. Design review, IDI, moodboard, user flow - these are just a few terms that you'll find in our cheat sheet. You'll also see some exemplary products, design infographics, and learn more about the product design process.
I want the design dictionary.
Articles
![How UX copywriting affects your brand]()
Dominika Stankiewicz06/03/2023How UX copywriting affects your brand
You’ve got your UX designer, your technical writer, your marketing team, and your copywriters. Surely you don’t need any more roles in the mix? Wrong. You’re missing UX writers and your product is worse for it.
![React.js and Vue.js – JavaScript libraries comparison]()
Dominik Guzy05/02/2018React.js and Vue.js – JavaScript libraries comparison
Nowadays we have so many good JS libraries or even frameworks, that choosing the right one for our projects is really overwhelming. I would like to compare two great JavaScript libraries for frontend development – React.js and Vue.js.
![What if I told you not all tech debt is bad?]()
Dominika Stankiewicz13/05/2025What if I told you not all tech debt is bad?
Many entrepreneurs whose business depends on software development dread the words “technical debt.” They know that it effectively means developers nagging them about fixing “critical” issues (a critical issue being, seemingly, absolutely everything), spending time and money on invisible fixes, and slowing down the release of necessary new features.
