I need a new web framework that can read cookies and communicate with an API
Long story:
I wanted to create an app, so I built an iOS/Android app using React Native and Node Express. I set up registration, password recovery, email verification endpoints, and a simple React website for basic app needs and hosting support, privacy, and legal pages. It took about a year to get everything set up and running in the app store close to my vision. After that, I wanted to get the website up to the same level as my React Native app. For some reason, I decided to use Next JS. It was supposed to be better than React, load faster, have server-side rendering, and improve SEO. You probably know the hype. But honestly, it’s thrown so many curveballs into my plan that I feel lost. I struggled for months trying to integrate an authentication package since I already had tools for that, only to scrap everything and create my own. I think I’m finally moving forward with basic development, but now I can’t manage user settings in a context the way I expected. It feels like a waste of time. Maybe I need to change my React query data from my user call, avoid storing anything in contexts, and do everything on the fly. Who knows
Now I’m thinking about switching to PHP or another language and starting my web project all over again because making progress with Next is such a hassle
I’m really frustrated and feel like I’ve got nothing to show for it
And to save you from your sarcastic comments, it’s probably a skill issue
For example, you have to do auth how Next JS wants you to do auth
That’s not technically true, but it’s much easier to do auth the way Next JS suggests. You can create your own auth, you just need to make sure the inputs and outputs match what Next JS expects.
Honestly, it’s only wasted time if you switch now.
Everyone knows the feeling of wanting to scrap everything and start fresh, but often you just need a break and come back with fresh eyes.
I say stick with it. This is your first Next app, so of course, it won’t be perfect, but the next one will be easier. You might regret switching when you face issues in PHP that you can’t even foresee right now.
This might not be super helpful, but if you already made a mobile app in React Native, I’d suggest just going with React. You might even be able to render your existing RN app on the web depending on how complex it is.
@Jaden
Yes, I was suggesting that if you’ve tried Next JS, there’s no point in trying React because he already tried React with Next JS and didn’t like it. Saying to go back to React seems a little silly after that. How you misinterpreted my meaning is beyond me, but I guess that’s what makes everything so interesting.
@Jessie
I was using React until I added Google Maps, and then hit the memory limits on Heroku. That’s when I saw the comparison charts for frameworks and decided to go with Next on Vercel. I’m worried if I switch back to RN that my codebase will get messy checking for web everywhere. I might have to rewrite it for the web.