I paid someone to build a website, but they left the work unfinished and stopped responding. I had been using WordPress hosting, though I now realize it may not be the right fit for what I want to build. I'm going to continue the project myself with help from Claude and learn as I go.
The site will collect user-submitted information on a relatively small scale, somewhat like a much smaller version of 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.
Is Next.js a sensible choice for a small project that depends on user submissions, or would a simpler frontend framework and separate backend be easier for a beginner?
4 Answers
Next.js can work, but it may not be the easiest starting point if you’re completely new. React with Vite plus Supabase or Firebase is a simpler split: the frontend handles the interface and the service handles accounts and data. You avoid some of Next.js’s server-versus-client behavior while still getting a practical stack for maps and user submissions.
The framework is only one piece of the puzzle. For a crowdsourced site, you’ll need user accounts, a database for submissions and coordinates, and some way to handle spam or inaccurate information. A common setup would be Next.js with Supabase, which provides PostgreSQL, authentication, and geographic database features. Leaflet with OpenStreetMap tiles could cover the map at small scale. Add moderation early, even if it’s just a report flag and an approval workflow.
Next.js is a perfectly reasonable choice and can handle both the frontend and backend parts of a project like this. It works well with maps and user input, and there are plenty of examples for Claude to draw from. The main learning hurdle is understanding its routing and the difference between server and client components, so expect some guidance and debugging while you learn.
That’s helpful to know. I’m expecting a learning curve, but it’s good to hear the framework itself shouldn’t be a problem.
Before writing much code, have Claude help you create a project specification in files outside the chat. Define the types of submissions, user roles, database fields, map behavior, moderation rules, and the first version of the site. Then choose the technology and build one small feature at a time. Whether you pick Next.js, Vite, or another framework matters less than having a clear plan and understanding the decisions well enough to maintain the result.
That’s a great suggestion. Writing down the requirements first should make the project feel much less overwhelming.
I appreciate the alternative. I’ll compare the two approaches instead of assuming Next.js is automatically the best answer.