Illa Lynn

There is always a new feature to ship, a bug to be squashed, an improvement that seems necessary.

However, whenever I take time to speak to my customers, I always end up learning far more than I had imagined, and in some cases, discovering that what I had just built wasn t even worth it.

The hard part is when do you stop building and start listening.

How many hours of the week do you set aside for customer discussions?

As a product designer, I usually start by thinking through the main user flow first.

Vibe coding makes that flow surprisingly easy to turn into something that works.

The harder part starts right after.

What happens when there s no data? What if an action fails? What should happen while something is loading? Can the user undo what they just did?

I spent two weeks rewriting titles on pages that ranked on page one and earned no clicks. The fix I trusted was CTR.

Then I split the impressions by device. The query "workout app development" showed 2,246 impressions in Search Console. Semrush has no US search volume for it at all, and only 19 of those impressions were mobile. Site-wide over the last 90 days, mobile accounts for 20 clicks against 5,789 impressions.