Feedback Thread

[u/AutoModerator]

Our weekly thread is the place to solicit feedback for your creations. Requests for critiques or feedback outside of this thread are against our community guidelines. Additionally, please be sure that you're posting in good-faith. Attempting to circumvent self-promotion or commercial solicitation guidelines will result in a ban.

Feedback Requestors

Please use the following format:

URL:

Purpose:

Technologies Used:

Feedback Requested: (e.g. general, usability, code review, or specific element)

Comments:

Post your site along with your stack and technologies used and receive feedback from the community. Please refrain from just posting a link and instead give us a bit of a background about your creation.

Feel free to request general feedback or specify feedback in a certain area like user experience, usability, design, or code review.

Feedback Providers

• Please post constructive feedback. Simply saying, "That's good" or "That's bad" is useless feedback. Explain why.
• Consider providing concrete feedback about the problem rather than the solution. Saying, "get rid of red buttons" doesn't explain the problem. Saying "your site's success message being red makes me think it's an error" provides the problem. From there, suggest solutions.
• Be specific. Vague feedback rarely helps.
• Again, focus on why.
• Always be respectful

Template Markup

**URL**:
**Purpose**:
**Technologies Used**:
**Feedback Requested**:
**Comments**:

Also, join our partnered Discord!

[u/No_Lock_7300]

scrolling through hoping someone actually follows the template this week. last thread was just a bunch of "check out my portfolio" with zero context

[u/Bee_140397]

Hey everyone! We run a wedding photography and cinematography business and recently tried building our own website.

Website: https://www.photographicallyyours.com

We're photographers, not developers, so we'd love feedback from people with web development experience on what we might have missed.

We're particularly interested in backend functionality, enquiry forms, technical SEO, website speed, security, mobile performance and anything else we should check before relying on the website for business.

We're not looking for a redesign — mainly an honest technical review and advice on what to prioritise.

Any pointers would be hugely appreciated. Thank you!

[u/Classic-Cod-1735]

URL: https://applore.app/app-store-screenshot-generator?utm_source=reddit

Purpose: A free App Store / Google Play screenshot maker. Pick a theme, swap in your own screenshots, edit headlines right on the canvas, and export every store size as JPG. No sign-up, no watermark.

Technologies Used: Next.js 15, React, Tailwind. Everything renders in the browser: the DOM is drawn to a canvas, scaled to the exact pixel sizes each store asks for, and saved as JPG, since both stores reject images with an alpha channel. Fonts are self-hosted so they embed in the export.

Feedback Requested: The editor UX. Is it obvious that you click a phone to replace its screenshot? Does the theme list on the left make sense, or would you expect to land in the editor first? Anything confusing on first load.

Comments: I built this over the past few days. The first version was a form that filled in a template and the results looked generic, so I rebuilt it around complete themes and on-canvas editing. Honest feedback welcome.

[u/Lightforce_]

URL: https://perf-sentinel.dev

Purpose: landing page for an open-source project (a devtool). No signup, nothing to buy, I'm only looking for design feedback. The target audience is back-end devs, back-end architects and DevOps folks.

Technologies Used: Rust 1.99.0 (the engine) and C# 14/.NET 10 (the hub)

Feedback Requested: general design feedback, plus whether the page explains what the tool does and who it's for quickly enough.

Comments: I'm a full-stack dev (mostly back-end) with a slight design background, so I'd especially like to hear from people who don't know the project. Be as blunt as you like, thanks!

[u/CyberWeirdo420]

URL: https://jstokowski.com/

Purpose: My Portfolio website, showing off my previous work and hopefully landing me some clients when they see it attached in an email

Technologies Used: Angular, Tailwind

Feedback Requested: Need feedback on overall design and UX, I tried to keep it simple with minimal animations. Only thing that I semi-bad is the projects section of desktop because it’s a scroll driven animation.

Also need advice on general feel of the text and wording, not my best skill for sure since I’m no marketer, just didn’t want it to sound so marketingly lol

Comments: no comments

[u/sebas-3261]

URL: https://vaulsoftware.com

Purpose: The website for my own small Colombian software brand, Vaul Software. It should help a small-business owner understand the services and find the next step without needing a technical background.

Technologies Used: Astro

Feedback Requested: Visual hierarchy, clarity of the service descriptions, and mobile usability. Is it clear who the site is for? Do web development, custom software, and automation feel like a coherent offering, or do they compete for attention? Which part of the layout or wording would you simplify first?

Comments: I’m the developer behind the brand and would appreciate specific criticism. Please leave feedback here in the thread.

[u/yihuaxiang → u/sebas-3261]

The layout is clean, but the first screen doesn't tell a non-technical owner what they'd hire you for. "Real-world challenges" could be a website, a booking tool, or an internal app, and the three service labels under the hero are easy to miss.

The phone is also doing a lot of the work, and it's a dark playzonevip screen. If the reader is a small shop, a calmer example (bookings, a catalog, a simple admin) would match that audience better than a VIP-looking app.

[u/Inner_Gear307]

URL: https://saramjh.github.io/space_atlas_student/moon/phases/

Purpose: I am developing Space Atlas, a free browser-based astronomy learning supplement for science teachers, parents and curious learners. The linked page should help a first-time visitor understand Moon phases by manipulating the Sun–Earth–Moon geometry rather than memorizing a chart.

Technologies Used: Static site generated with Python, HTML/CSS/JavaScript, deployed to GitHub Pages; interactive browser visualization.

Feedback Requested: Very specifically: on your first 30 seconds (desktop OR mobile), do you know (1) what to manipulate, (2) what you're meant to predict, and (3) what changes when you move the Moon? If not, which label, control or visual hierarchy is getting in the way? I'd value a diagnostic explanation more than generic design praise.

Comments: I'm the independent creator and haven't tested this in real classrooms. It requires no account/payment, but the site does use Google Analytics and AdSense (not ad-free/tracking-free), so adults should review suitability for children. This is a feedback request in the weekly thread, not a curriculum certification claim.