u/Gold_Whole_2372

I’m working on an education product and need feedback from real middle or high school teachers.

I’m not trying to spam or sell into teacher communities. I’m trying to find the right place to ask for honest product feedback, usability testing, or short conversations with educators who might understand the problem.

Are there any subreddits where this kind of request is allowed, especially for middle school or high school teachers?

Hey everyone,

I’m working on a real Next.js App Router project that has grown past the small app stage.

A few feature pages have become large client components that handle too much at once: forms, dialogs, tables, local state, helper functions, types, and server action calls. There is also some duplication across the app, especially around shared types, utility logic, and data-fetching patterns.

One feature in the project feels much cleaner because it uses a route-level feature pattern: the route owns its page, a local _components folder, smaller pieces for things like filters, tables, modals, headers, and pagination, plus a local types.ts and a small barrel file for exports.

I’m considering using that pattern more broadly, but what I’m really interested in is how larger Next.js projects stay structured over time. Once an app has many routes, shared UI, server actions, types, hooks, utilities, and domain logic, what keeps the codebase understandable?

For people who have worked on large Next.js App Router projects, what structure has actually held up in production?

Do you organize mostly by route, feature/domain, layer, or some mix of those? When do you move code into shared folders instead of keeping it colocated? How do you avoid both extremes: giant route files on one side and an over-engineered architecture on the other?

What has worked for you and what would you avoid?