Trying to design the UI myself — where am I going to hit a wall, and when should I hand it off to an agency?

In environments like warehouses, mobile touch targets should be at least 48x48 pixels. You also need to maintain generous spacing between form inputs and keep contrast ratios at a minimum of 4.5:1 to meet accessibility standards. Off-the-shelf component libraries are typically optimized for desktop screens in well-lit offices.

There are three main roadblocks you'll hit doing it yourself: 1) Weak information architecture where users lose track of where they are when navigating between screens, 2) Tiny buttons that don't support one-handed mobile use, 3) Ambiguous UI states whenever the connection drops or an action lags.

Designing with a developer's mindset is really hard because the interface makes total sense to us—we already know how the underlying logic works. I mean go stand next to a couple of warehouse workers and hand them the app with zero guidance. The moment you see where they get stuck, you'll immediately know whether you need an agency or not.

Most agencies will just draw flashy gradients and slick animations without knowing the first thing about working in a dusty warehouse. For a field-use mobile app, skip the generic digital agencies; work with a boutique designer who specifically specializes in B2B SaaS or industrial mobile UX, otherwise you're throwing money away.

I also did the design myself for my first B2B product. During the pilot phase, we were getting 15 support tickets a day from clients. We paid a professional designer 40.000 TL to completely redesign the mobile UI and user flows from scratch, and in the very first week, user-support calls dropped to 2 a day.

You shouldn't budget for a designer just to make the screen look pretty, but to completely eliminate user error when they're performing a task. Every operator wasting time in the field is a direct hit to your bottom line.

Don't jump straight into massive agency budgets. Check out popular mobile UI libraries shared on design tools. If you simplify the screens as much as possible and leave just one primary action per screen (like only a scan barcode button), it'll make your life a whole lot easier.

Let's separate the concepts, they're getting mixed up. The cheapest quote is usually the least thought-out one.

Ask who prepared the quote and who will actually do the work. Good luck with that.

Saved. When you try to change everything at once, nothing settles.

The real issue isn't the number, but what it's based on. If you have questions, write them; I'll answer as best I can.

i've been down this road, let me tell you. btw payment schedules should be tied to project phases not calendar dates.

the cheapest quote is usually the least thought-out one. just leaving this note, it might be useful.

I've been down this road, let me tell you. Trying to do this alone is the most expensive way.

When making decisions, write down the worst-case scenario too, not just the best.

I'm in the same situation, that's why I'm asking. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

Proven by experience.

Let me speak from the other side; I'm on the supplier side. People defend habits, not processes. Resistance comes from there.

When you try to change everything at once, nothing settles.

Let me summarize the topic, since several different answers were given. When you try to change everything at once, nothing settles.

Code without setup documentation isn't yours, even if you have it.

Noted, thanks.

I went through the same thing two years ago. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

If code ownership isn't in the contract, you have no bargaining power when leaving. If you post the result here, it will help others too.

Correct.

Yes, that's exactly how it is with designing UI. If you don't write this down from the start, it leads to arguments later.

If you post the result here, it will help others too.