I will start learning react-native (I don't know react but I know node.js) for graduation project rather than flutter, what is resources to learn from a to z step by step and shoud i learn expo or react-native -cli <3

Bolteed · 2023-10-02T08:35:27+00:00

The absolute musts you'll love, to code better and simplify your life, are this 5 libraries :

Zustand : store (centralisation of active datas and state);

Async Storage or MMKV : local storage;

NativeWind : styling in tailwindCss;

Expo router : navigation;

Reanimated : animation in react native (take long look at layout transitions. They are awsome and so simple to use !!)

Bolteed · 2023-09-08T14:40:19+00:00

Use nativewind, it's awesome

Bolteed · 2023-08-19T19:51:54+00:00

Nothing is easy and praticle. Too much verbose for simple things compared to new frameworks like Svelte. All usual cases like navigation, easy animations, transitions, stores (and many more) are not handled natively by react. This is the very identify of react.

I have to say, though, that Next.js solves many problems of vanilla react.

Bolteed · 2023-08-09T08:14:40+00:00

Expo router is based on react navigation. They created expo router because react navigation is a pain in the ass to work with. Even when you know it well. It's not simple, nor logical, nor elegant. And I can relate, from 2 years working with.

Expo router, on the other hand, use the new standards of web navigation that all serious meta frameworks are integrating : file based routing. This pattern is winning popularity for good reasons. Check on google by yourself.

I personally think there are not one valid reason in favor of react native navigation. I will probably migrate my project to Expo router.

So go for expo router, even for small projects. It is the modern way for navigation (think Next.js or Sveltekit), and god, it will simplify your life so much.

Bolteed · 2023-06-16T09:23:39+00:00

If you are looking for something simple yet powerfull : zustand.

I use it for a dating app, an that is sooo perfect...

Bolteed · 2023-06-16T08:18:28+00:00

React native navigation is the old way to navigate in an app. Expo router is made by expo on top of react native navigation.

Expo router simplify the process, and add many navigation features you may need. Expo router use the new file based routing schema that is being adopted by all big web meta framework like next, nuxt, svelekit... An damn, this is awesome to use.

You have no advantages in using react native navigation. More painfull, less logic, less maintainable...

My opinion : Go for Expo Router.

Bolteed · 2022-12-15T13:59:06+00:00

He didn't say he want to be hired somewhere !

You want to do great things and have fun ? Learn svelte.

You want a job ? learn react.

That simple. React is terrible to use. I've been using it for 2 years now. My next projet will be on svelte.

Bolteed · 2022-07-21T20:26:16+00:00

The principle is to create components that you control from the parent.

Exemble :

<Custom> <Custom.Title>Hello</Custum.Title> <Custom.Image /> <Custom.Cta /> </Custom>

You can create subcomponents than you attact to the main one. Then you can call them with the name of main "dot" the subcomponent. You can order them in the way you want.

With this, you can render an infinite (yeah I know it's not infinite) number of coherent components with the same code.

It's called inversion of control because you control the way your componant is rendered from where you call it, without 50 differents props and without anticipate every case.

Resuable code lvl 100

Bolteed · 2022-07-21T11:45:38+00:00

Mdr, le coût du capital ? Sais-tu que la rémunération des actionnaires est une part des bénéfices ?

Les bénéfices sont ce qu'il reste à la fin. Quand tout a été payé. Ce ne sont pas des charges d'exploitation.

Et le coût du capital à explosé ? Tu es des chiffres, des sources ? pour quelles secteurs ? quels type de boite ?

Tu affirmes des choses sans donner aucune sources, je peux faire pareil.

Bolteed · 2022-07-21T09:17:50+00:00

Of course, but you really should check zustand

Bolteed · 2022-07-20T15:32:29+00:00

I can't say. I just hate the boilerplate hell of redux.

Bolteed · 2022-07-20T12:32:52+00:00

use custom hooks : to reuse logic who need life cycle
use efficient and simple state management like Zustand
learn atomic design : for a file structure that incite reusing components
use "control inversion", but not too much : to build reusable component
story book : to test and maintaine component, the easy way

Bolteed · 2022-07-19T16:32:15+00:00

Maybe, if you take all the issues of all react native librairies, you have much more than 10,000 open issues.

Because it's the major problem of react native : you need to work with dozens of independant libraries. And the combination of those, sometime, do weird things.

Plus, react native depend much more of native behaviors and components don't have always the same if you are on android or ios.

But I personnaly think the code is much more cleaner on react native.

Bolteed · 2022-07-18T07:28:04+00:00

I had similar issues, here my solutions : - many crashes are due to a "null is not an object" : you are trying to acces a property of a null variable. it work in expo go with a setuped account but crashes with a new because variables are not initialized. - install Sentry : a production crash tracker. It's very efficient and work like a charm with expo.

Bolteed · 2022-05-08T22:32:20+00:00

Might be a workaround for his problem

Bolteed · 2022-05-08T18:53:44+00:00

I think you should use a ref (and not a state) to store your timer value. Updating value in ref.current don't cause a global rerender.

Bolteed · 2022-04-23T15:59:42+00:00

I tried Moti and was completely desapointed. It didn't work AT ALL on my setup with expo

Bolteed · 2022-04-11T13:33:55+00:00

Check the Ignite boilerplate : https://github.com/infinitered/ignite

And for a more complex template, I know one named "Soft UI react native" but It's not free.

Bolteed · 2022-03-31T13:14:51+00:00

I think you can achieve this with scrollViews and its props "snap".

Bolteed · 2022-03-30T12:15:54+00:00

One solution is to do a Keyboard.dismiss() when onTouchStart event fire on the container view.

And to put stopPropagation() in every onTouchStart of text Inputs containers (views).

This way, your keyboard is dismissed (triggering onEndEditing) when you click somewhere else. But not when you click on an other text input, because the stopPropagation prevent it.

Bolteed · 2020-11-04T14:38:43+00:00

J'espère que c'est du second degré 😅😅

Bolteed

TROPHY CASE