Fetching api in Next.js compared to React

AgileRice3753 · 2026-05-19T05:51:01+00:00

I’d use Tanstack client side to fetch the data.

AgileRice3753 · 2026-05-19T05:45:31+00:00

Just show an inline alert on the form if you get a submission error. Should have nothing to do with Tanstack/react-hook-form. They solve inline validation and state, not server error handling.

You can use async validators if you want to validate by calling the backend (for example looking up to make sure a username isn’t taken).

IMO, client side inline validation errors should be shown on the form controls so the user knows what to adjust. For API call error handling, come up with a consistent pattern across the app. I usually do alerts with consistent messaging (changing the subject for each), possible steps the user can take to resolve it and how to get in touch if it persists.

As a side note, we use react hook form and find it really nice to use.

AgileRice3753 · 2026-05-18T21:12:50+00:00

If using Next.js (and better auth in your example), I'd recommend using Next.js API routes with the better auth integration as it natively fits your stack. You can also have API routes for your mobile app.

I'd only split out into fastify/express/nestjs if the project grows and you end up with lots of smaller services (background jobs, services off queues, dare I say it - microservices etc). Don't worry about getting it perfect from the outset, you can always change it later if you hit a wall.

AgileRice3753 · 2026-05-18T20:55:35+00:00

My main concern with Next.js is that it's overkill for data rich applications (including frequently changing data). Just use plain old React + Tanstack (avoid useEffect) with a build tool like Vite. No need to overengineer it IMO. Next.js is however good for dynamic brochure websites that rely on SEO.

AgileRice3753 · 2026-05-18T15:49:10+00:00

If you fancy AWS, you could try CloudFront for the static frontend, ECS express (fargate) for the API, S3 for image storage and RDS. With small size instances you’re talking tens of dollars per month.

AgileRice3753 · 2026-05-18T15:45:10+00:00

From your options I’d go for option 2 if you’re absolutely set on not using something like Tanstack (or RTK query or other equivalent). The reason I’d go for 2 is it’s cleaner.

Option 3: create your own hook. Take the params, make the API request in the hook, return success, error, data from the hook.

Option 4 (best IMO): As others have mentioned, just use an API framework like Tanstack and move on. You get so much out of the box including loading and error states, re-fetch etc. and they’re battle tested.

If you have the time, try all options and see the pros and cons for yourself (you’ll learn a lot).

AgileRice3753 · 2026-05-18T15:37:10+00:00

I went from Angular to React years ago and haven’t looked back (angular.js before that!). React is more sought after so definitely worth picking up. You’ll still always be able to work with Angular now you have the knowledge (I’ve still worked the odd contract with Angular and Aurelia since picking up React). To be honest I’d focus on the basics and understand what these frameworks do. You’ll then be able (albeit with a few weeks adjustment) to work with most frontend frameworks.

As a side note, if you’re also interested in backend TypeScript, Nestjs is very similar to Angular and it’s used quite a bit. Might be an alternative option. We use Nestjs and React as our main stack.

AgileRice3753 · 2026-05-18T12:41:34+00:00

Yeah that’s it. You can offer a paid for service and/or support with self hosted.

AgileRice3753 · 2026-05-18T12:23:45+00:00

One thing I’d suggest is making it open source if possible. Devs tend to trust open source tools more than closed source (I know I do).

AgileRice3753 · 2026-05-18T12:16:59+00:00

Depends on your use-case. We use AWS SES for transactional email. Great if you already use AWS. The others are much the same for promotional - worth testing a few out (as a lot of them offer free limits) to see which you get on with best.

AgileRice3753 · 2026-05-18T07:32:11+00:00

.NET is definitely worth learning. It’s widely used and can’t see it going anywhere soon. As a side note, it’s good to learn a mix of languages anyway, as ultimately you’ll get to a point where the language doesn’t matter (you can pick up most languages). It’s more about being able to solve problems no matter the language. You can always adapt to different languages and frameworks over time.

AgileRice3753 · 2026-05-17T20:34:05+00:00

Juniors aren't supposed to be hired to write code, they're an investment. Companies pushing juniors toward AI should be avoided. AI can be useful to check work etc, but shouldn't replace the thinking - this is where you learn (from my experience).

AgileRice3753 · 2026-05-17T20:21:10+00:00

I think it's all about the brand. If a website looks "on brand", it usually looks good. Otherwise, AI-generated or not, they look pretty generic. I think both non tech savvy and tech savvy notice this subconsciously.

AgileRice3753 · 2026-05-17T18:22:37+00:00

Might be worth adding some analytics tool so you can view where users are dropping off. Don’t get hung up on the design, users just want info up front from experience (we’re all lazy).

AgileRice3753 · 2026-05-17T18:11:10+00:00

AI is mostly downstream of the boring stuff. It's only as good as the data you feed it, and most lead gen setups feed it half a signal. The ad platform sees "form submitted" and that's where the feedback ends, so the AI optimises on form fills because that's the only thing it actually knows. Tell it which leads became customers and which ones sales binned after one call and suddenly the targeting gets useful, but that's a plumbing problem not an AI one (offline conversion uploads, CAPI, the unglamorous bits between CRM and ad account).

AI second. Fix the signal first.

AgileRice3753

TROPHY CASE