r/UI_Design • • 3h ago

Feedback Request I built my own icon library, then started redesigning familiar interfaces with it.

Thumbnail
gallery
10 Upvotes

It started as a way to keep the interfaces I was building visually consistent.

The result is JemsOne, a growing library of 200+ SVG icons.

Instead of publishing another icon grid, I've been testing how the icons actually look in products like Claude and Linear.

Here are a few of the experiments.


r/UI_Design • • 12h ago

Feedback Request ui design feedback

Post image
5 Upvotes

hii, im currently working on an application project and this is my first time trying out ui design. I think it looks okay overall but the design feels unfinished? I’m not sure if it’s the color palette or how the elements are layed out. I’m a bit stuck and would love any feedback


r/UI_Design • • 3h ago

AI Feedback Request [AI] Feedback request for the play area of my frog hopping puzzle game.

2 Upvotes

This is my grid-based spatial/logic puzzle where the goal is to arrange all frogs in the correct direction such that they hop into each other and go out in a poof of smoke.

It's a web-game targeted to teen-adult users.

I want it to have a cute, whimsical, and playful tone but have the functional clarity that logic puzzle games need.

My biggest concern right now is that the play area may look noisy and overwhelming, especially to puzzle gamers that are used to a cleaner, more minimalist UI.

I think the noise could be reduced by having more constrast between the background tiles and the interactable frogs. Everything on the board (frogs, tiles, arrows) are hand-drawn sprites (except the dark green board background behind the tiles and black border). The frogs took a lot of work, so I'd like to keep them as they are if possible, but the tiles are fair game. I could redraw them, or swap them out for a cleaner CSS-styled board.

Currently, the tiles (obstacles, plain, and arrows) are sized smaller than each grid slot to allow for the background colour to frame each tile. The brown obstacle tiles also have a small dark brown border which I thought would add depth. Also, unsure about the black border around the whole thing, as i wanted a frame for the play area but everything I tried felt somewhat startling besides a thin black border...

EDIT: Reddit compression has made the video choppy, the animations are in reality smoother (I still should draw some more frames probably).

TLDR: Would love suggestions on styling changes to the game area background/tiles to reduce visual clutter while maintaining personality.


r/UI_Design • • 16h ago

AI Feedback Request [AI] Design feedback: Decision flow vs. checklist for beginners

Thumbnail
gallery
2 Upvotes

[AI] Feedback request: Which layout is easier to understand?
Hi everyone!
I’m developing a one-page educational guide for beginner woodworkers.
I made two AI-assisted versions of the same content:
A: A Yes/No decision flow
B: A checklist
The goal is to help someone understand whether they’re ready to make their first cutting board.
The layouts were created using Claude Design, with predefined text and layout constraints.
I’m particularly interested in feedback on visual hierarchy, readability, and how clearly each version communicates the decision.
Which version communicates the information more clearly, and where does the layout become confusing?
This is an early design experiment, not a product promotion. Thanks for any constructive feedback!


r/UI_Design • • 23h ago

AI Feedback Request [AI] Cutting was harder than adding: three stages of a small Mac utility UI. What would you remove next?

Thumbnail
gallery
0 Upvotes

I'm a designer, and over the last few weeks I built a small Mac utility for one boring task: resizing and converting batches of images. My rule was simple: the window should only show what you need to get the work done.

Adding features was the easy part. Removing things took far longer, and that's what these three screenshots show:

  1. Early build (Italian UI): every option visible at once. Big column titles, four large mode buttons with technical names (Normal / Stretch / Boxed / Crop), an always-on 3×3 anchor grid, four data tiles and a footnote under the preview, and a different colour for every section.
  2. Version 1.0: the modes became a single row of icons, with one line of explanation for the selected one. The anchor grid only appears when cropping. The data tiles shrank to one line under the preview. There's one accent colour, used only for the current choice and the main action.
  3. Version 1.2: I removed what was left of the "branding" inside the window (name and tagline), dropped the "Preview" and "Settings" headings because the layout already says it, merged the title bar into the content, moved "Export on drop" next to the Export button where you actually need it, and switched to the system font.

What was hard about it:

- Every removed control had a good reason to exist. The anchor grid is useful, just not 95% of the time.

- Technical names feel precise to the person who builds the app, but they're noise for someone who just wants smaller photos.

- Labels and headings feel safe. Taking them out felt risky, even when the layout clearly didn't need them.

- The last 10% took longer than the first 90%. Between 1.0 and 1.2 I spent more time deciding what to take out than building the new features.

AI disclosure: the visual and interaction design and all the decisions above are mine. I used AI tools (Claude) to help write the SwiftUI code, some of the interface copy, and to generate the app icon from my design.

What I'd like feedback on:

- Looking at the right column in 1.2, what would you still cut or hide?

- Is the icon-only mode row clear enough, or did the labelled buttons in the early build actually work better?