News for hackers. Stuff that matters.
Re:Ask HN: React Native or Flutter when the back end is Node? by verdverm on Monday September 28, 2026 @02:01PM (#49881901)
If you aren't doing native apps, my recommendation is to use the same language across full-stack apps. You can share things like zod types and validation logic (in the frontend for quicker user feedback, on the backend because you never trust user provided values)
Re:Ask HN: React Native or Flutter when the back end is Node? by rearview on Monday September 28, 2026 @02:04PM (#49881947)
That's why it looks so tempting but the main reason having mixed feelings because of reviews everywhere about React Native that it's doesn't have that kind of performance! And yeah zod and tRPC is a lovely combo for building app loving it with Next.JS
Re:Ask HN: React Native or Flutter when the back end is Node? by verdverm on Monday September 28, 2026 @02:08PM (#49881992)
There are a lot of React Native apps out there, the issues I see are more around platform glitchiness or workarounds than performance.

The main thing to watch out for is blocking the rendering or event loop. I've definitely seen apps where a slow API call blocks everything else. So less about performance and more about knowing how to do concurrency well.

Re:Ask HN: React Native or Flutter when the back end is Node? by rearview on Monday September 28, 2026 @02:10PM (#49882024)
absolutely! got any tips that I should be using while working on it :)
Re:Ask HN: React Native or Flutter when the back end is Node? by verdverm on Monday September 28, 2026 @02:12PM (#49882058)
let the agents debug these things, without needing images, the feedback loop is key

I haven't done any mobile stuff in a while, but there should be enough around to wire the agents up into a good environment, like remote chrome-devtools (with or without the MCP).

pnpm workspaces, makes having multiple packages with internal dependencies (like core and components) easy to manage in the dev workspace