React-Native Server Components! Change Your Native UI From Your Server!

[@DominiqueBello]

You give replies to my questions just before I formulate them! R-N-SCs are fantastic! Thanks a lot for your crystal clear explanations as usual!

[@ExpoDevelopers]

Very nice demo Jack. Thanks for sharing!

[@ryansatriayudha]

Does that mean that React Native Expo now is already full stack on its own just like Next.js?

[@irjamon]

Awesome video, Jack! Thanks for doing such a great job explaining RSCs in React Native / Expo. Even I learned some things …

[@raddadslab5097]

Another Portland DEV! Thats so cool! Small world. That conference sounds cool.

[@irjamon]

Would love to have you next time!

[@shrutikapoor08]

Love this Jack!

[@orangekanso]

Great video, thank you, Jack!

[@YasinAkimura]

That's really cool! But that rises a few questions as applications could be entirely streamed from the server depending on the use case it can be a great experience for customers or a worse but for me thats a door to quickly get out some important bug fixes which are not caused by native code! I am also interested in how this might play out with static hermes could we stream machine code to devices (very difficult to validate) or efficient hermes byte code what‘s the current real output of the server? Sending raw Javascript would sound very bad when using hermes as it shines by using the byte code directly

[@andreaspaayt]

Jack, consider doing a follow-up video?

[@aymenbachiri-yh2hd]

Thanks for sharing

[@Korosu-ty5ir]

awesome

[@abannsunny3515]

How does the publish look like for something like this? Will it be a 2 step publish? How will you coordinate the app store publish and the api publish?

[@jherr]

Gooood question.

[@Baconbrix]

Once this out of developer preview you'll be able to run "eas build" to build, deploy, and link everything together. We'll also have a more custom pipeline for more advanced deployment.

[@lukemontana9792]

great

[@MMMH-f3o]

Hello, can you share the vscode theme you are using?

[@vvvvvvvvvwv]

How do you handle versioning with this setup? Users are not always going to update to the latest version of the app right away and there's going to be days of turn around time with getting an app update out. How do you make sure you're not including code in the server component that's going to blow up on the client?

[@ryansatriayudha]

Does that mean that React Native Expo now is already full stack on its own just like Next.js?

[@luix9612]

I don't get it, so the component lives within the app and it's instantiated with the server response, I understand that now your server logic and types is handled within the same project but calling it server components seems kinda weird, it's more like server actions or something along the lines

[@keepforever726]

Where is "the server" in this paradigmn if this was a real deployed application? Does the native code on the phone act as the server? Or do you need a server deployed somewhere to handle the serverside operations if you actually deployed this?

[@nikhilpsathyanathan]

I'm thinking the same stuff

[@devkumar9889]

So is it like server components will be ready to be rendered by react native and server will send xmls/configs to render then only those components render at run time ?? Or server will send entire component and then it will be dynamically rendered by js runtime at run time ??

[@lessko9]

RSC is a different thing from SSR, - SSR is where react goes to the server ONCE and then everything else is handled by the client. - RSC is when React runs ALWAYS on the server

[@vetrivendhan6122]

I know server side rendering in the Next JS for performance and SEO optimization. Does SSR helps React Native too? What are is benifits guys?

[@carlosterrazas8913]

I have the same question. if there is optimisation I would use this technique.

[@BenKingUK]

This seems like a huge nightmare for versioning, dependencies, backwards compatibility... what am I missing?

[@carlosterrazas8913]

What improvement is there if we use RSC in react native? benefits? or the video is just smoke, many people ask the same question and you don't answer.

[@jherr]

You can update your native app by just rolling a new version to the server, avoiding store updates.

[@ThomazMartinez]

whos server it sends it from?

[@IamYouWeAreEveryone]

mine

[@maddog2622]

No it’s mine

[@noobdragon6115]

Its Mine, okay, no more discussion

[@leularia]

@@noobdragon6115 but no it's not

[@twenty9str498]

where does the server exist? is it in your phone? appstore? or what?

[@jherr]

You deploy it to a hosting service. For example, you can deploy it to Expo's EAS service.

[@edunomatseye7262]

This is going to be revolutionary, having a native React app access server functionalities within its scope. Fire. 🔥🔥

[@DjLeonSKennedy]

Didn't catch, what doesn't mean "server"? server is running inside app?

[@jherr]

No. It's a deployed web server.

[@DjLeonSKennedy]

@ eeeeeeeemm, but mobile apps are about offline also, aren’t they?

[@jherr]

@@DjLeonSKennedyyou can use the fallback for that.

[@DjLeonSKennedy]

@@jherr fallback? okay

[@jherr]

@@DjLeonSKennedy Alternatively you could run the server function on mount and only on success replace a built version of the component that is part of the distro. Basically the same thing, but you get more control.

[@cunningham.s_law]

so expo is gonna become vercel smart move

[@KnowledgeDBman]

What about NextJS with React Native?

[@jherr]

That would not be compatible with this RSC method currently. But a RN app could call API endpoints on a NextJS server.

[@KnowledgeDBman]

@@jherr Thought so. Thanks my friend anyway :)

[@notarealperson9709]

but typescript/javascript on the server feels so wrong

[@nightlight3212]

This is a mentality that people need to get out of their heads. Millions of applications are powered by server side JavaScript, even at large companies like Netflix, Google, etc

[@RobertoFabrizi]

Am I the only one that gets old school jsp / monolithic applications vibes?

[@sachinmogha5168]

Sir pls give Black Friday discount on you ProNextJS course. All other are offering. Josh is also offering.

[@whynot9963]

Looks good from an engineering perspective. Makes 0 sense to use this in production. Using base64 is downside in every way, tying backend to mobile app (wtf). Great video, as always, though. I just don't see this being useful. I have been wrong before

[@JakobRossner-qj1wo]

Native devs often don't want to think about servers but at some point they need. Where is the data coming from???? There is always a backend and a frontend and it just makes sense to close the gaps to allow faster and better development.

[@irjamon]

I think what we will see is that there will be a front end (app, web), you’ll have a back end server, and then you’ll have an RSC server which acts as a go-between between clients and the back end and provides a really nice DX for both. You can then have a variety of back ends and services that the RSC server ties together nicely. I’ve been wrong before too. 😅

[@yvesrobertcharlesthior]

first here lol !😀😀

[@yvesrobertcharlesthior]

following you sir from Dakar in Senegal. and i really apreciate your content. willing to learn more from you.

[@selloramolelle]

On the pipeline, nextjs for react native 😅

[@mikkelwf1984]

expo is already there

[@selloramolelle]

@mikkelwf1984 obviously but that's not the point lol

[@genkoph]

react ecosystem is getting weirder by the day

[@omega.developer]

who uses/stick to the react native cli instead of expo cli? please like this comment. i don't use expo and don't want to use it. who agrees?