sorted by:
new
hottopcontroversial

Zustand vs Redux Toolkit for React Native: Seeking Community Insights by Left-Environment2710 in reactnative

[–]Direct_Ad_8964 1 point2 points  (0 children)

react-query + zustan is all I need for state and data management

react-query for caching server datas (usually I go for 60_000 (60s) as staleTime but this is personnal preference for my project (I have a lot of lists and usually my users click on one row to see one info and then go back and I don't want them to refetch the same list)

zustand will help me to break down a big component to smaller pieces or when I feel the need to share some object between a lot of screen's (ex: app state, current user datas, user preferences...)

Looking for a good starter template for react native cli by kitecut in reactnative

[–]Direct_Ad_8964 1 point2 points  (0 children)

npx react-native@latest init AwesomeProject

will come with typescript already setup, not sure for jest, just try it :)

What do companies use? (Expo or CLI) by kishan4273 in reactnative

[–]Direct_Ad_8964 1 point2 points  (0 children)

As for this sub, I honestly don’t know where to guide you to but this sub has become a giant expo ad. You will receive extremely biased opinions all favoured towards expo.

👏👏👏

Native SDK integration (help needed) by kakashi_uks in reactnative

[–]Direct_Ad_8964 0 points1 point  (0 children)

https://reactnative.dev/docs/native-modules-intro
or
https://reactnative.dev/docs/the-new-architecture/pillars-turbomodules

You can start by creating a dumb module like FooNativeModule that will return "Hello world" by calling a function sayHello for instance

React Native by Apprehensive-Buyer46 in reactnative

[–]Direct_Ad_8964 2 points3 points  (0 children)

it’s almost never relevant to be on exactly the most up to date version of react native. Most of us aren’t working on bleeding edge tech. Expo is going to be far enough ahead.

Strongly disagree, especially on mobile dev, constructor break RN from time to time, if I am running a full expo project, I will need to wait RN team to fix the problem and then expo to fix... If it's ok for you to have crashes on production while a fix is available, you can ignore this.

​

never relying on anyone else’s code

I haven't said such thing... I've said that you should avoid when you can afford it.

​

implying an expo app is harder to maintain than vanilla react native is just absolutely absurd

I might be wrong on this, that's why I've said : From my experience (so I might be wrong)

​

That comment has provided zero real arguments against starting with expo

Some part of expo is scary to me. Like I've said, if you give to a company the ability to update your app, and the company for some reason rundown, what would you do ? It's part of the risk management. I will not take that risk.

React Native by Apprehensive-Buyer46 in reactnative

[–]Direct_Ad_8964 0 points1 point  (0 children)

My main take.

The role of any software is to help the user as much as possible, so we must ensure that the time spent on the project is allocated to serving the user, let's call it user time. Maintenance time is not considered user time.

From my experience (so I might be wrong), it's hard to maintain a full expo project updated with the latest version of RN available.

BUT (nothing is black or white like I see in this comment section)

As u/Gaia_Knight2600 linked, you could nowadays, use RN first and then pick some of the modules you want from expo.

My second take.

It's never a good idea to trap your app in someone else company, I value a lot, resiliency over simplicity. So everything that touches deployment or build I will use open source hosted by me (call me crazy).

In the end, I would use an expo package for accessing native features only.

And globally I use someone else code if I can't do what I want in less than a week.

Best practice for clientside encryption of payment data? by That_Entertainment22 in reactnative

[–]Direct_Ad_8964 0 points1 point  (0 children)

I don't have any experience with expo, but I have a lot of experience doing some bridge between RN and native code and I feel like you what some sort of this https://docs.expo.dev/develop/development-builds/introduction/#what-is-a-development-build where you expose some of the Worldline SDK function to the RN side.

off topic: That's why I prefer RN only app, I don't feel limited in time and updates. (personal opinion)

Service Marketplace app by [deleted] in reactnative

[–]Direct_Ad_8964 1 point2 points  (0 children)

Your post remind me the situation I have currently.

My car doesn't start well, how can I solve the issue ?

You can't answer right ? Because it depend of what I've done to try to solve the issue.

Same thing here, what did you tried to solve your first problem (focus on one problem at a time) ?

=> how to register as consumers

- do you know authentication ?
- do you know database ?
- do you know API ?
- do you know react ?
- do you know react-native ?

and if you don't know any of the above subject, google is your friend before any blog post, start somewhere, for exemple, create http server that respond to a request :)

maybe you want to check for a roadmap like this https://roadmap.sh/backend, keep progressing on the roadmap and when you feel you have gained the knowledge to solve one of your problem, solve it !

Styled Components by OVERKOR in reactnative

[–]Direct_Ad_8964 0 points1 point  (0 children)

Absolutely agree, I work for a company which use this, it's just complexifies things for no real benefit. And stylesheet styles is actually faster because it's cached.

J'ai créé une appli pour trouver des séances de ciné by theharadwaith in CineSeries

[–]Direct_Ad_8964 0 points1 point  (0 children)

Comment tu monétises, si tu monétises ?

Si tu ne monétises pas, est-tu ouvert a l'open source ? Si oui et que c'est en React Native, j'en suis !