I am a designer and developer. You could characterize my role as "a developer with design sense" or "a designer who knows how to code." Either one is mostly true. I've worked inside organizations as an employee, and outside them as a contractor.

Speaking broadly, good design reduces friction. Design is a methodology to solve a problem. Maybe there is a form that needs filling out, or an important message that someone needs to know. Good design makes the form easier to fill out and submit, and the message easy to read and understand. Bonus points if there's a little bit of joy to experience along the way!

Different problems require different solutions. Sometimes they require large teams, especially when user or customer research is important. Sometimes small teams or individuals can get things done faster, because they communicate well with each other. Still other times, a single opinionated outsider can move the needle with management far more than an entrenched internal team.

What you are looking at when you see a user experience that looks 'nice' may have happened by any one of those avenues. With the best design, you may never even know.

Design is a job. Good design takes work. That work happens in the infinity of ways that any work happens. A solid understanding of the problem domain makes the solution obvious, and it's a designer's job to gain that understanding, and work out solutions.

Thanks!

Are you a 'designer' in the sense of UX, or visual design?

I (sort of) get how usability happens, but have less experience on the visual design, layout, color, graphics side.

Like are you able to sit down in an afternoon and convert a page with working UX into a consumer-ready interface? Is there standard prep that goes into this like design systems or theming?

I design both user experiences and visual ... things ... too. I'm able to sit down in an afternoon and convert a page _if_ I have some guidance: For example, if the customer already has "their" colors and "their" fonts -- meaning, they have an existing visual system -- then yes!

Coming up with that visual language is more work. Typically companies like to be unique (but not too weird) so while you can identify "best practices" among larger brands, most of your time is identifying what makes them different, and finding the best way to highlight those features visually. There tends to be some back and forth with this, and there are a lot of feelings to navigate, especially if the customer has strong preferences about how things look.

Color, layout, heirarchy, history and perception are all part of a good design education! It's worth your while to find art and artists that you like, and find how they solve problems. Paul Rand and Massimo Vignelli are two significant personal influences, and they have written extensively (or had things written about them) about their process and thinking.

(Edit: I spelled Massimo Vignelli's name wrong, oops)

thank you, will check them out

not sure if this is exactly your wheelhouse, but do you have a sense of the time + expertise that goes into the design system of a consumer app at launch? Like are most apps using an agency, a freelancer, people on the team?

That’s a little like asking “do you have a sense of how much a car costs?” It’s a difficult question to answer without more detail.

ah, fair point. was hoping for a take like 'most polished consumer apps you see have gone through a largish, standard process', can see how that would not be the case