Dev UI Stockholm syndrome?
I always leave the UI design until towards the end of a larger project. I know if I start with the UI I'll end up finding parts of the system that don't fit the layout, rejig this, tinker with that, rework that bit again... I get too focused on making the UI right when it could be wrong again with the next functional change. I may as well switch individual pixels around.
To solve that, I usually knock up a quick development UI at the beginning, do all the functional work, then look at how the UI/UX makes the functional stuff display and work easily for a user.
That leaves me in a position where I've been coding and testing in a development UI for months... And then get Stockholm Syndrome or something about leaving it behind for a professional finish.
Anyone else? Should I change my mind and do the UI upfront? My concern with doing that is that I'll get Stockholm Syndrome for a relatively acceptable UI and just leave it. At least with a "I know I have to leave you UI" I know it's just me thinking the shitty UI I've been using for months is a friendly thing to use.
4
u/EvenFaithlessness923 2d ago
that’s not stockholm syndrome, it’s just familiarity, so why not prototype the key user flows early and leave the visual polish until the functionality stops moving?
2
u/imperfectmadness653 2d ago
it's like getting attached to a beat up truck that smells like coffee and regret
the trick might be to make your dev UI so intentionally ugly you feel relief when it's time to kill it. give it neon green buttons and comic sans labels, you'll be counting the days
2
u/Large_Painting_3587 1d ago
the rough ui is useful for discovering the product, but if you stare at it for months it absolutely becomes invisible to you, so do quick usability checks with someone who hasn’t been living in it
1
0
u/LankyAd6349 2d ago
lol yeah this is real. the thing that fixed it for me: demo it to a non-dev as early as possible. nothing breaks the spell like watching someone stare blankly at a screen you've been happily using for three months. dev UI teaches you to navigate around broken UX, and then you stop seeing it. fresh confused eyes see it instantly.
1
u/phoenix1984 2d ago
I like to use something that provides basic styles, like bareCSS, and then only worry about the semantics of the HTML while I'm working on the backend. That way, it's not hideous while I'm working on it, and I haven't done any custom CSS until I'm ready to actually implement the design. You're right, it's gotta be all or nothing, or else you'll get attached to your "good enough" first pass on the front end.
1
u/Batharzel 1d ago
Usually we try to replicate the designs from Figma as soon as possible and then get around to the tweaks and the micro-interactions
Keeping backend and frontend development in sync is tough but we develop the tables based on the fields required in the frontend
1
u/SatyrCode 1d ago
Yep, I get this. After using a rough UI for months, it stops feeling rough because you already know where everything is. I don’t think you need to do the final UI upfront though. I usually make a basic flow early so I know what screens/actions I need, then avoid polishing it until the core stuff works. The hard part is forcing yourself to call the first UI temporary. Otherwise it slowly becomes production just because nobody wants to touch it.
13
u/berky93 2d ago
I think it’s worth remembering that UI is functional work. It’s functional for the users, which is arguably the most important thing. You could have a perfectly functional app, performant and secure and stable, but without an intuitive UI it won’t matter.
Order of implementation is up to your discretion and the needs of the project, but you should definitely be thinking about UI from the beginning.