Your product already works. Let’s make it clear.
Fiksum is a workshop where people bring existing apps and sites so they become easier to use. We find where people stumble and fix it by hand: in the interface, the copy and the code.

How we think
A confusing interface is not the person’s fault. It’s a part you can adjust.
Sound familiar?
Things people bring to us
We hear phrases like these from teams of every size. Each one is a symptom, not a verdict. Usually the cause sits in a few specific places in the interface.
“People ask support what is already on screen”
“Sign-up gets started but not finished”
“We kept adding features and now it’s cluttered”
“The update has been rejected twice”
“On phones the buttons are tiny and crowded”
“Developers write the copy, and it shows”
Before and after
The same form. A different conversation.
Move the slider. On the left is a typical form grown out of a database: every field at once, grey buttons of equal weight, an all-caps title. On the right is the same task after the workshop: two fields that are really enough to start, labels above fields, one clear action.
A schematic illustration, not a screenshot of a real project.
Why small things matter
People don’t write that an interface is confusing. They just leave.
Most people don’t report friction. They close the tab, delete the app or call support with a question whose answer is already on screen. The team only sees the consequences: calls, low-star reviews, unfinished sign-ups. The cause is often entirely mundane — a vague label, a button that looks like text, an error message with no hint of what to do next.
That’s why we begin not with a new design but with a careful walk through the product. We note every place where a newcomer stops, hesitates or makes a mistake. Such a list is usually shorter than you’d expect, and it shows exactly where a small change brings the most relief.
What usually changes after a fix
- fewer repeated support questions
- forms people actually finish
- copy that sounds like a person, not a system
- an interface comfortable on phones and by keyboard
These are typical directions of change, not a promise of specific results.
On the bench
Five kinds of work, one goal — clarity
Open a drawer to see what’s inside. Every service is for products that already exist or have mock-ups.
Everything we fixYour app works, but people get lost on the third screen, can’t find the right button or abandon sign-up halfway. We take the scenarios apart, rework the problem screens and, if needed, make the code changes for iOS and Android ourselves.
Long forms, unclear navigation, copy nobody finishes. We simplify the structure, rewrite microcopy and make forms shorter and usable by keyboard and on phones.
You don’t have to redo everything. We start with a review, find where people struggle most and propose changes you can roll out gradually without stopping the product.
An app update stuck in store review? We help bring listings, screenshots and data explanations in line with App Store and Google Play requirements.
We don’t say goodbye after the changes. Requests come through the helpdesk form, each gets a reference, and fixes happen in working hours in priority order.
How a fix goes
From first look to a quiet “finally, it makes sense”
We work in small steps so you see the effect of each change and the product never stops. You can stop after any step.
First look
We walk the key scenarios as a newcomer and note every stumble.
Prioritised list
Problems ordered by how much they get in people’s way.
Sketches of changes
We show how it will look before changing any code.
The fix
We make the changes — ourselves or with your developers.
Check
We look at whether it got easier and decide what’s next.
Toolbox
Check your colour contrast right now
Aa Ґґ Її
Walnut on bone: 14.0 : 1
Three tools we use ourselves every day
A WCAG colour-contrast checker, a plain-language text checker and a request priority sorter. They run in your browser, send nothing you type and need no sign-up.

Workshop rules
Six rules we keep to
- Look first, fix secondNo changes before we have seen the product through a newcomer’s eyes.
- The smallest change that helpsWe don’t rewrite what can be adjusted.
- Plain wordsWe explain without jargon — and write interface copy the same way.
- Accessibility is not optionalContrast, labels, keyboard, large tap targets.
- You see every stepSketches, changes and checks come to you, not “we’ll show you later”.
- Honest about limitsWe don’t promise metric growth or store approval.
Publishing
When an update gets stuck in review
An improved app still has to reach people. App stores have their own rules for listings, screenshots, data and permission disclosures. We help read the review feedback, understand what is actually being asked, and prepare corrected material.
We cannot guarantee the store’s decision — it is always theirs. But we can remove the usual reasons for rejection.
Rejections are often not about code but about how the product is described: screenshots from a previous version, promises of features that don’t exist yet, or camera or location access with no explanation of why. Such things are easy to miss when a team is focused on development, and just as easy to fix once you know where to look. We go through the material with you and explain every edit.
Pre-submission list
- Privacy policy published
- yes
- Screenshots from the real build
- yes
- Every permission explained
- yes
- Test access for review
- yes
- Data questionnaire completed
- yes
- Listing without empty promises
- yes
Helpdesk
Something broke? Write so we understand straight away
The helpdesk takes requests about bugs, awkward spots and publishing for products we work on. The sorter helps judge how urgent a problem is, and the form passes the description to the support address.
To the helpdeskBlocks people
Bothers many
Has a workaround
A wish
Our focus is improving what exists: apps, sites and mock-ups already in place. If you only have an idea, we will honestly say whether we can help or suggest starting with a simple prototype.
For a review — no: a working product or mock-ups are enough. For code changes, access is agreed separately and securely, never through the website form.
Almost never. Rewriting is expensive and risky. We look for the smallest change that brings people the most relief, and move in steps.
It depends on scope. After a first look you receive a prioritised list of problems and an estimate per change — and you decide what to do first.
Yes, we work in Ukrainian and English. The site forms accept both.
When we’re in
Working hours
Mon–Fri 09:00–18:00
We work Monday to Friday, 09:00–18:00 Kyiv time. Messages sent in the evening, at weekends or on holidays are read on the next working day.
124 Soniachna Naberezhna St, Dnipro, Dnipropetrovsk Oblast, 49022, Ukraine
This is the registered address from the company data. It is not a confirmed walk-in workshop — please don’t visit without arranging it first.
Bring your product
Show us where people struggle. We’ll work out the rest together.
A product link and a few sentences are enough for a first conversation.
Write to the workshop