Product and UI/UX design, so your users can stop guessing

People hesitate, make mistakes or call support over something that should be simple. We rework the flow and the screens with you, all the way to mockups you can click through and your developers can build from.

When someone freezes at a button, the button is usually to blame

Watch someone pause over a button labeled “Submit.” They aren't slow. They're doing the math: submit what, does this go to the customer, can I take it back? Change the label to “Send invoice to customer” and those questions answer themselves. A good share of product design comes down to that kind of attention. What is this person trying to do, what do they already know, what are they afraid of, and how do we spare them the guessing?

You'll hear two terms a lot. UX is the flow, the sequence of steps someone goes through. UI is what they actually see: words, buttons, colors. We care about both, and we have a soft spot for the moments everyone forgets. Error messages tend to get written last, in a hurry, and then get read at the exact moment someone is most worried. Same goes for loading, empty screens and the phone version. Motion earns its place when it helps, like a transition that shows where you're headed instead of a screen that just swaps out.

Codetics is a French company, and we work remotely with clients in France and abroad, including the United States. We're engineers as well as designers, which changes how we draw. A mockup isn't done until it can be built, and we'll tell you when an idea would cost more than it brings in. We'll also try to talk you out of a full redesign you don't need, because your users spent real time learning where things are and moving everything takes that away from them. If one screen is the problem, we work on that screen. Video, motion graphics and 3D are a separate craft, and we handle them separately.

From the first conversation to the file your developer opens

You probably don't need all of this. Pick what helps, and the quote spells out exactly what's included.

Understanding the need

The most useful work happens before anyone draws anything. We talk with you, and with your users when we can, and we watch for the workarounds they've invented. A sticky note on the monitor or a spreadsheet open on the side tells you plenty. Broader user research is scoped separately.

  • User research and needs analysis
  • A review of the current flow and where it breaks down
  • Priorities written down and agreed with you

Organizing the flow (UX)

People look for things where they expect them, the way you head for the dairy case without reading the signs. A menu organized around your org chart only makes sense to people who work for you. We organize around what users came to do, and we settle the steps before any final screen gets drawn.

  • Information architecture, meaning how content and menus are organized
  • UX design: steps, decisions, mistakes that can be prevented
  • Interface states: loading, success, refusal, recovery

Designing the screens (UI)

Someone who stops by once a month and someone who lives in your tool all day need different screens. The first one wants a guide. The second wants everything in view and doesn't want to lose a few seconds on every single action.

  • UI design and interface design
  • Web interfaces
  • Mobile interfaces for iPhone and Android
  • Business interfaces: internal tools, dashboards, monitoring screens

Testing, then handing off

Moving a button on a mockup costs next to nothing. Moving it in a finished product costs a lot more, so this is the place to get things wrong, before you pay for development. After that, your developers know what to build.

  • Prototyping: a mockup you click through like the real product
  • Design systems: shared rules for colors, buttons and wording that keep a product consistent
  • Specifications developers can work from
  • A walkthrough with your team

Where a screen is quietly wasting someone's day

These come up a lot, and one of them may sound familiar. If not, tell us about yours in your own words.

  • Business software your staff puts up with

    Nobody judges an all-day tool by its first impression. What wears people down is the extra click, the re-entered data, the question they have to ask a coworker. Our goal is to remove those one at a time.

  • A mobile app in the planning stage

    A thumb doesn't aim like a mouse, and people often check their phone standing up, one-handed, in the middle of something else. We design iPhone and Android screens for those conditions and try them out as a mockup before development starts.

  • A dashboard nobody can read

    A dashboard exists to help someone decide. For each number, we ask what that person would do if it changed. When the answer is “nothing,” that number can often go.

  • A flow where customers drop off

    Sign-up, checkout, a quote request: every field you ask someone to fill in is one more small reason to leave. We look for where people bail and why, then we simplify.

  • A product that has lost its consistency

    Three kinds of buttons and five shades of gray sound like a detail. But each variation makes people relearn something they already knew. A design system cleans that up, and your developers stop redrawing every button.

  • An idea to show before you fund it

    You'd rather hear “I don't get it” now than later. A clickable mockup gets real reactions from users or partners before you commit to development.

Figma to work in the open, Sketch to think

You don't need to know either one. The part that matters to you is that you see the work as it moves, instead of getting a surprise at the end.

  • Figma

    Software for designing screens that opens in a browser and is shared like a document. We like it for a simple reason: you watch the mockups take shape, you drop a comment right on the spot that bothers you, and your developers pick up the measurements and colors there instead of guessing.

  • Sketch

    Software for designing screens on a Mac. We use it to explore and refine visual directions, back when it's still fine to be wrong a lot.

The drawing comes after the listening

Understand the problem before drawing anything

We talk with you, and with your users when we can, looking for the exact moment they get stuck. Sometimes the real problem isn't the one anyone expected, and it's better to find that out before the first line gets drawn.

What you have in handThe problem written down in a few lines, and priorities agreed together
  • Interviews
  • Paper
Pricing

How to get started

Two ways in, one rule: you know the price before any work begins.

For a problem that's still unclear

Technical Assessment

€390Fixed price, paid online

A senior engineer studies one specific problem and gives you a written report: the current situation, causes and risks, the recommended approach, and the scope and estimated budget for the next stage.

See the Technical Assessment
To design, build, modernize or integrate

Quoted project

Custom quoteTotal price in writing before work starts

The price depends on scope, complexity, constraints and risk. Every proposal spells out the deliverables, milestones, estimated timeline, total price and payment schedule.

Tell us about your challenge

You can write to us without buying the assessment. It helps when the problem is still unclear; it's never required. VAT not applicable, art. 293 B of the French Tax Code.

Frequently asked questions

No, and sometimes it helps, because you see your product the way your customers do. Tell us where they get stuck, in your own words. We take it from there and explain every choice until it makes sense to you or you've changed our minds.

Yes, if the problem is specific: a flow, a screen, a prototype. The quote says so in writing, along with what isn't included, such as a complete redesign, extensive user research or unlimited revisions. If the job turns out to be bigger, we'd rather tell you.

The list of files you receive is set with you in the quote. If you want the Figma or Sketch files, ask at the start. Once the price is paid in full, the rights to the mockups created for you are assigned to you under our terms of sale. Pre-existing and third-party elements stay under their own licenses.

No. Listening to your users, deciding what to take out, calling a screen ready: that's a person's job. Claude, an AI assistant made by Anthropic, sometimes helps us try out an animation idea. We don't use it every time, we decide what stays, and a person reviews the work before it reaches you.

Yes. You follow the mockups through a shared link and comment on them directly, at whatever hour suits you. Calls are booked ahead of time. Codetics is a French company working remotely, and prices are in euros.
Get started

Show us the screen that drives you crazy

A screenshot and a few quick lines are plenty. You talk directly with the engineer, then you get a scope and a price in writing.

  1. 01You describe the problem
  2. 02We talk it through
  3. 03You get a scope and a price in writing
Talk to an engineer
Technical Assessment

Is the problem still unclear?

€390

Fixed price, paid online · VAT not applicable, art. 293 B of the French Tax Code.

The Technical Assessment tells you what's behind it and what the next stage would cost.

See the Technical Assessment