What do you think about using a monorepo to manage all apps in one project folder, such as API, web, admin, and mobile app? Is it a good idea for production?
some reason my profile is not updating..very strange..just rebuilding you code..and i have the fields correctly in Supabase. I am getting this error "Property 'avatar_url' does not exist on type '{ id: string; username: string; bio: string; }'.ts(2339)" and when i add the data in manually it will not display the image...but it does update the text..the file does upload to cloudinary though when i try to update..but it still says failed to update profile becasue supabase is not being updated...
Sir how to handle the situation if the puchToken is already stored in the db, and if user opens the app again that it will again the api request to save the push token to db. Should we stored the token in local storage too and conditionally make the api request based on the condition
I don't think that's a bad problem. In a way, you are updating the push token with the most recent one. If you want to optimize it, and not send the update request if it didn't change, you could either use the suggested approach of local store, or you could fetch the user profile data inside your Auth provider, and compare the new push token with the one from the user profile. If it's different, then send the update. Another thing around push tokens you should think about is multi-device support. With our approach, the user will receive the push notification only to the last device that he signed from. Because the user can only have 1 push token and we are overriding it. To support multi device, and send the notification to all devices that the account signed from, then you need a many to many relationship between user and push tokens. Create a separate table with tokens, and the token will have a user_id.
@@notjustdev I recently have many interviews for react native developer role none of them asked about expo not and they shared details about about their project they are using react native with cli big companies doesn’t use it
![🚨 7 hours [LIVE] coding: Build a Full Stack Project with NextJS - Day 9 🚨](http://i.ytimg.com/vi/_8xaAHD24zE/mqdefault.jpg)
![🚨 7 hours [LIVE] coding: Build a Full Stack Project with NextJS - Day 9 🚨](/img/tr.png)
You give hope to react native devs and that's amazing. Thanks much.
Thank you again 😊
you are realy an amazing person
love Supabase
Thank you bro ❤
What do you think about using a monorepo to manage all apps in one project folder, such as API, web, admin, and mobile app? Is it a good idea for production?
this is what freelancers face....im tired of different repos for day?
some reason my profile is not updating..very strange..just rebuilding you code..and i have the fields correctly in Supabase. I am getting this error "Property 'avatar_url' does not exist on type '{ id: string; username: string; bio: string; }'.ts(2339)" and when i add the data in manually it will not display the image...but it does update the text..the file does upload to cloudinary though when i try to update..but it still says failed to update profile becasue supabase is not being updated...
Plz, use appwrite for the backend 🎉
I dont want to see a homie just rondammmly disappear
hello im from india
Thank you save my life last 2 years 😂😂😂😂
You're welcome 🙌
may I know which vscode font are you using
how do you upload multiple videos?
really I'm tired of Expo errors. 90% of my time goes to fixing Expo errors
Sir how to handle the situation if the puchToken is already stored in the db, and if user opens the app again that it will again the api request to save the push token to db. Should we stored the token in local storage too and conditionally make the api request based on the condition
I don't think that's a bad problem. In a way, you are updating the push token with the most recent one.
If you want to optimize it, and not send the update request if it didn't change, you could either use the suggested approach of local store, or you could fetch the user profile data inside your Auth provider, and compare the new push token with the one from the user profile. If it's different, then send the update.
Another thing around push tokens you should think about is multi-device support. With our approach, the user will receive the push notification only to the last device that he signed from. Because the user can only have 1 push token and we are overriding it.
To support multi device, and send the notification to all devices that the account signed from, then you need a many to many relationship between user and push tokens. Create a separate table with tokens, and the token will have a user_id.
Thanks Brother
there is no tutorial, quiz app with pocketdb. if possible please create one.
be careful little wonderer
homey just dont
Stop using no company uses it 😂 its only for tutorials
what exactly?
@@notjustdev I recently have many interviews for react native developer role none of them asked about expo not and they shared details about about their project they are using react native with cli big companies doesn’t use it