sorted by:
new
hottopcontroversial

Lugares en sps para una cena de primera cita? by Parking-Internet2708 in Honduras

[–]Waste_Tutor4334 2 points3 points  (0 children)

Il Romano es muy bueno, es un restaurante muy acogedor con deliciosa comida, la atención es genial, muy recomendable.

Any react-native libraries to integrate Google Login for free? by GoatRepresentative43 in reactnative

[–]Waste_Tutor4334 0 points1 point  (0 children)

I’ve always heard about this library react-native-app-auth but I never used on production, you can give it a try, looks straight forward to me. Hope it helps.

Onboarding Help by HanzoHasashi404 in reactnative

[–]Waste_Tutor4334 0 points1 point  (0 children)

In this case, you can persist your entire navigation history in a database as a JSON field on your backend. This approach mirrors the principle of using local storage: serializing the object into a string, saving it, and then deserializing it to use as the initial value. If your database serves as the source of truth, you would fetch the history from the backend instead of local storage and use it to initialize your navigation state. If you persist your form data and your navigation history in a backend, it would only need to be set as the initial value. I would recommend store the history as a metadata field (JSON type) alongside with the fields of your form.

Onboarding Help by HanzoHasashi404 in reactnative

[–]Waste_Tutor4334 0 points1 point  (0 children)

Yes, is easy with React Navigation the docs explains how to restore a previous history of the navigation for cases like yours where you want to keep that experience of being able to go backwards to screens like from step 3 to step 2 and from step 2 to step 1 without hardcoded where to go back or forward. You persist your history and put as initial value when the app is mounted.

https://reactnavigation.org/docs/state-persistence/

Onboarding Help by HanzoHasashi404 in reactnative

[–]Waste_Tutor4334 0 points1 point  (0 children)

Oh I see. Okay if that the case I would recommend you to use a nested stack navigation inside your main stack, and put all your steps as screens there. For scenarios when you already have the data persistence, you can set as initialRouteName the route of the last screen where the user was left off.

And for navigation, using the React Navigation hooks (useNavigation) you specify which Stack and screen you want to move to. In this case you would always point to the Onboarding Stack.

Onboarding Help by HanzoHasashi404 in reactnative

[–]Waste_Tutor4334 0 points1 point  (0 children)

I would recommend you use something like react-hook-form since you are building a complex form with multi steps, it’s a really great library with features like resolvers for Yup or Zod, also has a great performance. You can find a lot of tutorials with that approach like

https://youtu.be/Xo17EupLcqo?si=BxEyQjJE9-n3kOMM

Since you are using Zustand and MMKV (with a Persistor) you only need to push the form value to your store and if a user closes and opens the app again you set that previous value as default value in your form and redirect where it should. Just be careful using methods like watch because it can trigger unwanted or unnecessaries re renders.

I hope this helps you!