u/Impressive-Track-551 — reddlx

This is the design system I created for my first UI/UX project. I'm aiming for an industry-level portfolio, so I'd really appreciate honest feedback. What did I do well, and what should I improve?

Thanks!

u/Impressive-Track-551 — 1 month ago

▲ 10 r/UIUX

From ideas to structure.

Before focusing on colors, typography, or visuals, I spent time creating low-fidelity wireframes in Figma.

This stage helped me:

Validate user flows

Explore different layouts

Prioritize features

Identify usability issues early

Working in low-fi allowed me to iterate quickly and make changes before moving into high-fidelity designs.

These wireframes are part of my travel planner project, and every iteration brings me one step closer to a better user experience.

I'd love to hear your feedback—what's your approach to low-fidelity wireframing?

u/Impressive-Track-551 — 1 month ago

▲ 21 r/UserExperienceDesign+2 crossposts

My travel app didn't start in Figma. It started in this notebook.

When people see a polished UI, it's easy to think that's where the work begins.

For me, it started with a notebook.

Before opening Figma, I spent days writing down ideas, sketching layouts, mapping user flows, and questioning almost every feature.

These pages aren't pretty.

They're messy.

Some screens were redesigned multiple times. Some ideas were completely removed. I even changed the navigation after realizing it didn't make sense.

Looking back, these rough sketches probably saved me dozens of hours in Figma because I could explore ideas without worrying about colors, typography, or perfect alignment.

One thing I've learned so far:

It's much cheaper to erase a pencil line than redesign a polished screen.

These notebook pages are the foundation of the travel planner I'm building now.

I'm still learning every day, but it's exciting to look back and see how a simple sketch slowly turns into a real product.

I'd love to know—do you still sketch on paper before designing, or do you go straight into Figma?

u/Impressive-Track-551 — 1 month ago

▲ 1 r/UIUX

Building a travel planner that solves a problem I keep running into

After talking about why I switched to UI/UX, I thought I'd share the project I'm currently designing.

I'm working on a travel planning app.

At first, I thought the problem was booking trips. But after doing research and thinking about my own experiences, I realized booking isn't the hardest part.

The real problem starts after that.

When people travel, they jump between multiple apps. One app for flights, another for hotels, another for maps, another for weather, another for notes, another for sharing plans with friends, and another to save memories. Planning a trip ends up feeling scattered instead of exciting.

So I started asking myself:

What if one product could organize the entire journey?

That's the idea behind my project.

Some of the features I'm exploring:

Trip planning and itinerary builder

Budget planning

Weather information

Saved places

Trip checklist

Group trip planning with friends

Booking integration

A personal trip gallery where users can revisit memories from completed trips

One thing I'm trying to avoid is feature overload. Just because something sounds useful doesn't mean it belongs in the product. Every feature has to solve a real user problem.

Right now I'm working through user flows, information architecture, wireframes, and the visual design. I'm treating this like a real product instead of just another portfolio piece.

I'd love to hear your thoughts.

If you've ever planned a trip, what was the most frustrating part? What do you wish existing travel apps did better?

reddit.com

u/Impressive-Track-551 — 1 month ago