Mobile Devs Hate Servers. Expo Wants To Fix That. 

What when where

Nativewind v4, the dev was hired by Expo iirc - Using it on a new project and it's missing a couple of things but it's pretty smooth

what? where does it says that?

​@toparamennoodles9652 wait tauri supports native??

Co-signed… video on native Tailwind support please!

I second this

Me too 😢

absolutely! compare with tamagui

Samen

Exactly!!

Definitely give it a shot, it's a blast! Do you have any ideas for what app you could build?

@@seanblonien Ikr alot of cool stuff! Plus easy uploads with uploadthing 🤭

You mean don't see mobile devs adopting server endpoints for building RN/Expo Native apps? Why not? coming from a genuinely curious place as I have gotten into RN/Expo in the last year, and having a backend server out of the box sounds great to me. how do you manage your backend/server state/databases in your 11 years of development so far?

I don't think expo is really for native mobile devs.

Yeah @SulekSkelux makes sense

With expo it’s really not that bad anymore

And also you don’t want to push the need for a sever on mobile - you should be local-first when running an app on device.

​@@alastairtheduke???

Curious what plugins you used with Ionic. My biggest concern is having to rewrite all our BLE (Bluetooth Low Energy) and WiFi with React Native.

Why? Just why? 🫤

@@BassEffector I am pretty much just using Ionic/Capacitor as a shell for an adapted version of the web app, and also using Ionic's modals and popovers only. Not using any of their other components because they are too opinionated about design (for example, built-in padding that can't be removed on the select box). However, the Expo prototype is already not going well, and I literally started it. The way Expo/RN handles responsive image sizes utterly baffles me. Like, how does NextJS handle responsive images better than a literal mobile app framework? I think for this app I'm going to keep it on Ionic, but there are definitely some mobile-specific projects I would use Expo for in the future.

good to start, extremely expensive if scales

@@aliadowz thankfully, ive got 0 users 🙏

Because front end devs are noobs with backends. No hate, just true

I was thinking the exact same thing

yeah it's not even that hard to do this

You don't make mobile apps *yet*, but if you're a web dev you can now easily make them since Expo has amped up their game in the last year -- I encourage you to give it a shot with a small app idea you have always had

It’s just a lambda function that integrates with expo APIs which are primarily client side (js bundle)

yes. it actually is the simple. `+api.js` files are independent entrypoints for creating serverless/lambda functions the frontend app/JavaScript code has one entry point, typically `app/index.js`, and all of the code that file refers to is bundled (via Metro bundler) into the app bundle (and as of v3 of Expo Router, there is even some code splitting in the bundle, but practically speaking it's still one bundle, especially for Native platforms)

Please can we use Expo to create a react native into Production?

Servers are useful when your app require a data comparison feature. Like Highscores, market value tracking or difference in price(eg costco and walmart etc)

I think this perspective is what Theo is missing the most -- mobile devs spending their time on UX, native components, cross-platform compatibility, and testing is EXACTLY WHY we use backend-as-a-service tools because we already spent 36 hours doing app dev. If I only have 4 hours for backend leftover, why would I choose to write my backend from scratch? My users don't give a shit if I wrote it from scratch or Firebase did it for me, they want a great app experience

@@pehclark7256 To be fair many of these things can be running off your home desktop too. The occasions where you actually need a server specifically for customers data is a little rarer. Mostly servers are required if you want: * multiplayer / real time collaboration (can also use P2P here) * distributed alerts/notifications/messages * to share or sell customer data * perform financial/sensitive transactions. * processing intensive tasks But to be fair, in most of these cases you would be better building a PWA or website anyway... Then you hit a large consumer base. The intersection between these things and actual apps which need to be on a mobile device is fairly limited. For instance an app activatable with google voice which stores and shares audio recordings of customers around the country.

Learn a proper backend.

@@shadmansudipto7287 Not sure what you mean here? My job is a mixture of Node, Python, Go, and Rust backend/lambda/CLI code

Sandbox is the name of directory.

excalidraw

T3 turbo has that

Was confused by that too lol. Two very different things

I think his argument is React Native was so successful at bringing a framework, increased standards, and improved developer experience to native app development that it "forced" the existing native languages/platforms (Swift) to respond with their own framework (SwiftUI) that decreased boiler-plate, increased standards, and improved on DX

it's pretty nice! if you ever wanted to build that cool app idea of yours for iOS, Android, *and* web, it's quite fun to get into!

And a perm

You shouldn't. It's fun

😂

Flutter sounds really cool

You're not wrong, considering Expo's web bundler only introduced code splitting just over 1 month ago... BUT they are definitely making strides in the right direction. I'm sure the template app would be like 1MB for web with the basic boilerplate in it, but that's also because 99% of the users/devs use it for native only. (I don't blame them, they are infact a native-first platform, and for good reason) That 1% is surely to grow however if Expo continues to bring familiar Next.js/web like standards to its ecosystem

it is true if you are using expo in react native, this is not a case with bare react native cli

For the 0 people that asked, I ended up using Deno

Aren't API endpoint routes exactly the opposite use-case from server components? If we had server components, you would do the data fetching/processing on server component side, then stream in the data. With API routes, that only really makes sense if you are on the client-side only and have to do all of your data fetching to the server because there is no ability to render components at all, and everything must be fetched.

There are libraries that make it trivial

He didn’t say that at all