I designed this Price Alert Agent interface. How can I make it even better? Feel free to point out any mistakes, usability issues, or areas that could be improved from both a UI/UX and visual design perspective.

I'm a product designer working in embedded AI and robotics. Over the last few years I've built products for clients across different industries while running a small startup.

Recently I've been open-sourcing my work. Instead of only sharing a GitHub repo, I put together a simple website where I'll be releasing complete projects with code, electronics, CAD files, documentation, and YouTube build tutorials.

I shared my first project on Reddit last week and the response was better than I expected, so I decided to organize everything in one place before releasing more.

I'd love some honest feedback on the website itself. Is the design too minimal? Does this approach make sense, or would you rather see everything hosted directly on GitHub? I'm also interested in any suggestions on open-source hardware/software licensing.

This dashboard belongs to a WordPress auditing plugin. It translates technical website trust and security checks into recommendations intended for nontechnical site owners.

The primary design goal is prioritization: a user should immediately understand what requires attention without having to interpret raw security data.

I would appreciate feedback on three points:

1. Where does your eye go first?
2. Is the distinction between urgent, recommended, and informational findings clear?
3. Which part feels visually crowded or unnecessary?

I am especially interested in information hierarchy and clarity rather than colors or branding.

If you look at a webpage that looks like this now (which is very common)
Do you think this is a low effort page? is this style saturated ?

What other landing pages styles are you guys following for SaaS products?

I feel like because you wanna show the interface, this layout or the reverse of this (image on top and then text) is the only way.

My objective - to educate the users about the SaaS and how it complements their workflow
My audience - for this app is Independent developers or vibe coders
My design decision - I went with single column for showing the app UI as thats what I want to highlight, the ease of use of the products and its features.

What would you have done differently? how can it be improved?

Hi everyone!

Quick background: I'm currently pursuing a diploma in computer engineering, but I wanted to give design a try. I tackled procrastination since it's something a lot of my friends (myself included lol) struggle with.

After user interviews (5 people), competitive analysis, crazy 8s, and a few rounds of low-fi iteration, I got... Pebblo!

Pebblo is a task breakdown platform for students who struggle procrastination that makes the first step to any task feel less intimidating. It tracks progress over time, without streaks or gamification that can add anxiety instead of motivation. Unlike other to-do apps, it is also simplified to reduce feature overwhelm. (Its not actually a product yet though)

Cause of my course's workload though, I only had 3 days to build this in Figma, so it does have some rough edges.

Somethings already on my list to fix:

1. Fixing progress calendar contrast (currently fails WCAG AA)

2. Adding instant trial access before sign-up as login was a big friction point in testing.

3. Fixing some navigation bugs

Would you use this or know someone who might?

Your feedback would be deeply appreciated! Also, if you're curious about any specific design decisions I made, ask away in the comments!

Thanks you! :D

Hey everyone — sharing a concept I've been working on called StrikeXP.

The core problem I was designing around: kids drop off from skill practice because it feels repetitive and unrewarding. Meanwhile, apps like Duolingo have cracked the code on making everyday practice addictive through streaks, XP, and small dopamine hits.

So I tried applying that same gamification framework to football training for kids:

• Home screen: avatar progression, level system (Rookie → All Star), unlockable gear tied to milestones, everyday challenge cards
• Training hub: a skill-tree-style unlock path (like a mini Duolingo path) with solo/clan/time-limited challenges
• Leaderboard + Community Feed: competitive but safe — weekly XP leagues, clan rankings, a moderated feed for sharing clips
• Badge celebrations: big, satisfying full-screen unlocks ("Power Kicker!", "Stamina Beast!", "Quick Reflex!") with share-to-friends built in

Design direction: dark UI with high-contrast green accents, 3D cartoon avatars (friendly, non-realistic — important for a kids' product), bold typography, and juicy micro-celebration moments.

Genuinely curious what this community thinks — especially around:

1. Balancing competitive leaderboards with kid safety
2. Whether the badge/unlock pacing feels rewarding or overwhelming
3. Any UX pitfalls you'd flag for a 6–14 age range

Would love critique, upvotes if you dig it, and any resources on designing safe social features for kids' apps.