Why a UI designer's website is all text.

I know. I'm a product designer. I've spent 15 years making interfaces look and feel great. So why does this site look like it was written in a text editor?

Fair question. Here's the honest answer.

I don't have time.

That's it. That's the main reason. I'm designing apps for clients, running discovery sessions, building prototypes, and having calls every week. I don't have time to sit down and art-direct a portfolio website with perfectly staged mockups and pixel-perfect case study layouts.

I already have a portfolio. It's at robcot.com and it shows the visual work. That site exists for people who want to see what I can do with pixels. This site exists for a different reason.

This site is about talking to you directly.

The people who land here are usually thinking about building an app. They've got questions. They want to know what the process looks like, what it costs, what they'll actually get, and whether I'm the right person to help. That's a conversation, not a gallery.

Text lets me do that quickly. I can share everything I know, the experience, the process, the thinking, without spending weeks polishing screenshots. And honestly, I think that's more useful to you than a grid of pretty mockups.

I'm also the product designer here.

This is me solving my own problem. I've got years of experience and knowledge to share, but no time to package it all up into a traditional designer portfolio site. So I built a solution. A fast, simple, text-first site that gets the information out there and lets me focus on the actual work.

That's what I'd tell any client to do. Start with the core problem. Solve it simply. Don't over-engineer it. I'm taking my own advice.

It lets me move fast.

I built this site using the latest tools and technology, including AI. It lets me experiment, test ideas, and get content live quickly. No waiting for photo shoots, no custom illustrations, no fiddling with layout grids. Just clear writing, clean structure, and useful information.

It's simple, but it works. And it lets me spend my design hours where they actually matter, on client projects.

It's also great for SEO.

I'll be honest, this is a keen interest of mine. I've been experimenting with building different types of websites and seeing how they perform in search. A text-heavy, content-rich site like this gives Google exactly what it wants. Clear structure, useful content, fast load times, and real answers to real questions.

If you're curious about how it's going, or if you want to see the results, feel free to ask. I'm always happy to talk about what's working and what I'm learning. And if you're someone who needs a site like this built for your own business, that might be a conversation worth having too.

You'll see the visual work on the call.

When we get on a call, I'll walk you through real projects. You'll see the wireframes, the high-fidelity screens, the prototypes. You can ask questions about specific decisions and I'll explain why things were designed the way they were.

That's more useful than scrolling through a gallery anyway. You get context, you get the thinking behind the work, and you can see how the process applies to your idea.

Want to see the visual work?

My portfolio site has the full picture: case studies, UI design, branding, the lot. If you want to see what fifteen years of product design actually looks like, head over to robcot.com.

View my portfolio at robcot.com

Related: A bit about me · How the five-week process works · What happens on your free call