Is Next.js a Good Choice for a Small Crowdsourced Website?
Asked by
MellowPine42
I'm starting over on a website after hiring someone who left the project unfinished and stopped responding. I'm planning to learn as I go, use Claude for guidance, and get additional help when I need it.
The site will depend on user-submitted information, somewhat like a much smaller eBird, and it will include an interactive map. Claude suggested Next.js for the frontend, but I'm wondering whether that recommendation could be biased because Anthropic uses Next.js for Claude.
For a small project that relies on user accounts, crowdsourced submissions, and maps, is Next.js a sensible choice? Would something simpler, such as React with Vite, be easier for a beginner?
Answers
The framework is probably less important than the data and backend design. A crowdsourced map site will need user accounts, a database for submissions and coordinates, and some kind of moderation to handle spam or inaccurate reports.
A common setup would be Next.js with Supabase, which provides authentication, Postgres, and geographic database features through PostGIS. Leaflet with OpenStreetMap tiles could handle the map at a small scale. Next.js itself doesn’t provide those pieces automatically.
Reply to this answer
There are many valid technology combinations, so don’t get stuck searching for a perfect answer. Choose a reasonably common stack, set up a local development environment, and build a very small working version first—such as signing in, submitting one location, and displaying it on a map. That will reveal what you actually need before you commit to more features.
Reply to this answer
If you’re starting from zero, React with Vite plus Supabase or Firebase may be easier to understand than Next.js. You can still build the map and user-submission features, but you’ll avoid some of Next’s server/client and App Router concepts. Next.js is not wrong, though—the best choice is the one you can understand and maintain.
Reply to this answer
Before asking an AI tool to build the application, have it help you write a project specification. Keep that specification in files in your project folder rather than relying on one long chat session. Define the pages, user roles, database tables, submission workflow, map behavior, and moderation rules first. Then ask the tool to create the project in small, testable stages.
Reply to this answer
Next.js is a perfectly reasonable choice and can scale well, but it’s a full-stack framework rather than just a frontend library. The main challenge for a beginner is learning its routing and understanding the difference between server and client components. If you use it, keep the initial architecture simple and let Claude explain each part instead of blindly generating everything.
Reply to this answer
Add your answer
Answers are reviewed before publication.
MellowPine42: That makes sense. I don’t want to ask for help on every individual decision, so I’ll start by writing down the requirements and learning the basics as I build.