Excited to finally share what I’ve been building.
Over the past few months, I’ve been working on 'Intra’ an omnichannel customer communication platform that helps businesses manage customer conversations from Facebook and Instagram in one shared inbox.
Handling account balances or ticket check-ins without database transactions is asking for race conditions.
Prisma interactive transactions with row-level locks ensure concurrent API requests never double-spend or overwrite state.
Storing JWTs in localStorage leaves web apps wide open to XSS token theft.
Using HttpOnly, SameSite cookies with silent refresh rotation keeps tokens out of JavaScript scope while keeping Next.js and NestJS sessions seamless.
Broooooooooooo, Neverrrrrrrr Everrrrrrrr look desperate in life. Remain calm during hard times. Understand it's just your time to suffer like every great man before you.
Most mobile performance issues are not rendering bugs, they are payload bloat.
When mobile networks drop to 3G, heavy JSON responses and unoptimized bundles lock up user interfaces fast.
SWR caching, route-level code splitting, and lean API responses keep web and mobile dashboards instant.
Most mobile performance issues are not rendering bugs, they are payload bloat.
When mobile networks drop to 3G, heavy JSON responses and unoptimized bundles lock up user interfaces fast.
SWR caching, route-level code splitting, and lean API responses keep web and mobile dashboards instant.
Client-side redirects after payment are an illusion of success.
Never deliver value or upgrade accounts based on a frontend return URL.
Verify cryptographic signatures on raw webhook payloads in Node.js before modifying state.
Bro we live a very low quality life in this side of the world! How is a whole NIMC app and website whack…the face verification feature that you implemented before I log in on the website keeps blurring my face and then the app doesn’t sent an OTP after I request for one… yall should sack your web developer and app developers…they don’t deserve the pay!!!!
I wouldn’t rewrite everything at once. I’d first audit the existing app, understand its structure and identify potential breaking points. Then I’d migrate it gradually, page by page, keeping the React app running while testing each migrated section. I’d also verify API integrations, authentication, routing and existing user data. Before fully switching over, I’d run staging tests, monitor errors and have a rollback plan ready. The goal is to make the transition feel invisible to existing users.
A company hired you to migrate an already functional React application with active users to Next.js,
how would you approach the migration to ensure a smooth transition without disrupting existing users or breaking anything in production?