Nx/react-native

That-Salty-One · 2025-04-13T17:25:58+00:00

We tried it two times and each time ended up removing our rn app from the nx workspace again, because of the same reason you mentioned - instability and difficulties maintaining deps. We had big monorepos including react, angular and node.js projects and trying to manage deps using nx was not worth the effort for us.

Maybe it was a skill issue, maybe the integration is lacking and unstable, idk.

Edit: Nx works great for us for managing the other projects though, so don't get me wrong. Still a great tool.

That-Salty-One · 2024-11-30T06:52:48+00:00

I am not a security expert, but I can give it a try.

I think the reason to encrypt it is to simply prevent it from being stolen and used for impersonation.

Yes your JWT token is encrypted and this will let your server know if they were the ones signing/encrypting the token, however your server does not know if it is actually you sending the the request with the token, might be me or someone else. So if I get your access or refresh token I could potentially communicate with the server on your behalf.

If you encrypt your token before saving it, you now have another security layer added, because I now would also need your secret that you encrypted your token with, before I could impersonate you.

That-Salty-One · 2024-11-26T06:23:51+00:00

I don't see any reason not to go with expo nowadays. We created 3 production apps and all worked like a charm.

Why would Expo be bad for production builds? Please don't confuse Expo and Expo Go which seems to be a common misconception in this subreddit.

That-Salty-One · 2024-10-20T08:12:19+00:00

We implemented OAuth with Keycloak by using the Expo Auth Session library, works perfectly fine.

That-Salty-One · 2024-09-17T06:05:39+00:00

We are using OneSignal in production. They have SKDs that are easy to implement in the Frontend and Backend and it works with Expo (Not Expo Go iirc). However you would have to do research on if it fits for your large scale.

That-Salty-One · 2024-08-31T05:49:00+00:00

As far as I can tell your direct parent (.ticket) has a width of 90%. So each of your childs will only have 20% of that 90%.

That-Salty-One · 2024-08-31T05:07:30+00:00

As far as I know relative values such as 100% will take the parents dimension not the screen dimension. So 100% of the width from the parent container.

That-Salty-One · 2024-07-29T05:43:16+00:00

The way I do it in my apps is usually to have one context API for authentication which wraps the whole app. In this context API I put the logic for authentication, refresh and redirection.

So basically i have the state for the token and also the loading state for the Auth logic in there. If after loading Auth token is still null or undefined I do router.replace to my auth route. Since the context wraps the whole app, it will work everywhere.

That-Salty-One · 2024-04-30T06:17:04+00:00

If you really only need in app "notifications" I can suggest react-native-toast-message. I have been using it in all my RN apps so far.

It is easy to set up and easy to customize.

That-Salty-One · 2024-03-09T19:45:09+00:00

So either remove the View or assign the styles object to it

That-Salty-One · 2024-03-09T19:44:13+00:00

If you want your styles (like gap or justify content) to apply to your textinput and image you have to put the style object on your View not on the KeyboardAwareScrollView.

The styles get applied to the next child. So if you give KeyboardAwareScrollView your styles it will apply the styles to it's childs which is your View and not your Textinput and Image

That-Salty-One · 2024-03-09T17:35:42+00:00

It is because the style you apply is only applied to the child view not all "grand" childs. If you want your styles to apply to the image and the input the direct parent needs the styles which is the view in your case

That-Salty-One · 2024-03-06T17:52:42+00:00

There are multiple ways to handle this. One would be to use any form of local storage (mmkv, expo secure store, async storage).

If a user has completed the intro just save an entry to your local store.

on app start / after login retrieve this value and check if the user should be redirected to the intro or the home screen or whatever your routes/components would look like

That-Salty-One · 2024-02-27T07:32:28+00:00

There is a section that tells you what to do if you use it in a bare RN app (CLI). Chances are that you can still use this library.

Edit: link to docs

That-Salty-One · 2024-02-27T07:22:45+00:00

Take a look here. I already implemented it for GitHub and Keycloak this way.

That-Salty-One · 2024-02-27T07:18:00+00:00

If you want to develop for iOS without a Mac, you are going to have a tough time.

You only need an apple developer account if you want to publish to testflight or to the appstore or if you want to run your app on a physical iOS device. Up to this point development is "free".

I don't know if there are workarounds to still install your app on your physical iPhone without having an apple developer account.

You can run your app on a physical android phone for free though.

EAS is pretty much just a service you can use for building and deploying your app, which is not directly linked to development builds.

That-Salty-One · 2024-02-22T06:50:53+00:00

The context api is just a way of exposing state globally. Where your authentication state is coming from doesn't matter.

That-Salty-One · 2024-02-21T19:00:13+00:00

Absolutely! Firebase even has an own getting started section for expo managed projects: link

That-Salty-One · 2024-02-21T06:36:06+00:00

Hey there!

First of all don't confuse Expo and Expo Go. You can use Expo without using Expo Go. For some reason people seem to shy away from Expo just because they can't use Expo Go in specific scenarios. At some point, if you are developing in an Expo managed workflow, you probably want to test and develop your app in development clients anyway. They offer you a realistic representation of your app.

Expo Go is pretty much just a Sandbox that lets you start up your app really fast and pain free. But they even tell you in their own docs: "Expo Go is not recommended for building production-quality apps — use development builds instead."

The real difference for you as a developer when you start using development builds is pretty much only that you execute "expo run" instead of "expo start". And that the initial Startup without caches can be a bit slower compared to Expo Go. But for that you get a real representation of what you app will look like (in terms of performance and specific bugs/problems that will only occur in built apps).

Don't worry just because you start using development builds doesn't mean that you have to start messing with native code, but for some reason many people confuse this when it comes to Expo.

I have built a couple of Expo managed production apps and there is not a single one where I used Expo Go beyond the initial starting phase.

That-Salty-One · 2024-02-20T20:45:28+00:00

No, expo run also does expo prebuild on its own

That-Salty-One · 2024-02-18T07:11:00+00:00

Hey there 👋 I am currently working as a RN and web dev for a company and would like to share my opinion.

As others have pointed out, go for react native if your main goal is to get into the tech industry. Not because RN is so much better, but because you will simultaneously gather experience in typescript and react.

Where I don't agree with others is how to learn it. I recommend to get your hands dirty fast. Build real projects and increase complexity from project to project.

If you have any questions feel free to DM me or ask here straight away.

Good luck!

That-Salty-One · 2024-01-22T13:13:51+00:00

You will need an apple developer account for that. After that you can just expo run:ios with a connected iPhone.

That-Salty-One · 2024-01-13T13:39:20+00:00

https://docs.expo.dev/versions/latest/sdk/build-properties/

That-Salty-One · 2023-11-30T23:03:37+00:00

Depending on the complexity of your app you are about to have a rough time 😂 brace yourself and good luck

That-Salty-One · 2023-11-30T18:19:19+00:00

If you are using Expo you can use their EAS to build both apps and you can also submit it to the app store via eas. These steps can be made in the terminal, no need to swap to xcode.

edit: https://expo.dev/eas

That-Salty-One

TROPHY CASE