Not really. If you are good at JavaScript, most of it will be easy for you. The last part of UI integration, that assumes you have some react knowledge, however, you should be able to follow . But Highly recommend you checking the react tutorials to get most of the last part

@@codingwithlulu Alright! Thanks a lot. I have already completed half of the tutorial. I loved it please keep posting.

Glad you like it, soon will be adding follow up courses that cover advance side of each part of the MERN stack, until then feel free to check out my react full course as start if you are not familiar with react, then cover react hooks, then best react pattern practices, full playlists available in my channel, hope that can help you as well

more Advance follow up courses in the way, stay tuned :)

soon I will be pushing one

So glad you found it helpful

Keeping in mind 😌

What type of Web app! Any thing I particular ?

Appreciate your feedback, keep that in mind next time

Thank you so much for the feedback and hope the content was helpful

Yes apologies for that, because my sore throat and flue 😷

No first part. But initial set-up is just basic todo app with redux toolkit

My pleasure!

Marhba, tmana ykono faydinak.

Alah yhafdak ❤ kenstafdo

Good point! Compound components and a well-structured data setup are great options for many use cases. Here’s why the Factory Pattern fits here, though: it’s useful for scenarios where each product (like a laptop, camera, or phone) has unique properties and logic that don’t overlap. The Factory Pattern helps us encapsulate that complexity, so when a new product type is added, we don’t have to rewrite or modify existing code. In contrast, compound components work best when managing UI elements that share similar structures or behaviors (like form elements or a grouped set of toggles). But in cases where logic varies significantly across types, the Factory Pattern can provide cleaner separation and scalability. Thanks for bringing this up-it’s definitely an interesting design choice!

i will be happy to create a new video to cover this in more depth, until then feel free to check the documentation :) tanstack.com/query/v4/docs/framework/react/guides/testing

Glad it was helpful! and keep going

Thank you, my next ones have bigger font size. Thanks 😊

A Singleton in React is useful when you want just one instance of something, like an authentication service or a connection, across the whole app. Think of it as a "one and only" object that's shared everywhere to avoid duplicates. You'd use it when: Global services like login or API need to be consistent everywhere. Expensive stuff (like a WebSocket) shouldn’t be created more than once. Shared state is needed across different parts of your app without duplicating logic. But in most cases, React’s own tools-like useContext or libraries like Redux-are enough, so only use Singleton if you really need that "one-instance-only" guarantee!

Welcome 👍

Great question! 🚗💡 Yes, you could absolutely just map over the Car component directly if you’re working with a simple use case. However, the Factory Design Pattern really shines when things get more complex! Imagine if, instead of just rendering basic cars, you had different types of cars with extra configurations - like some cars need custom props, some have additional behaviors, or you want to handle future types of cars without modifying your mapping logic all the time. That’s where the factory comes in handy! The factory component abstracts away the decision-making process for which car (or other complex component) should be created, keeping your rendering logic simple and flexible. It also makes it super easy to expand in the future. Need to add electric scooters next week? No problem, just drop them into the factory - no need to rewire your entire app. 😉 So while mapping directly is great for simple scenarios, the factory keeps things more scalable and manageable in the long run! I'll cover more on when to use this pattern (and when not to) in my next video, so stay tuned for that! 🔔 Thanks for the awesome question!

⁠Additionally, in enterprise software dev, there is a large focus on having code covered by unit tests. This abstraction makes it much easier to focus the unit tests on specific parts of the application. Great video @codingwithlulu

Wow, that’s an awesome point! You're absolutely right - seeing a design pattern in action, in real-world scenarios, really makes it click! 💡 I’ve actually got a great example coming up where we’ll dive into exactly that. Think about building an e-commerce app - handling different types of products (laptops, smartphones, cameras, etc.) and how the Factory Design Pattern can make adding new product types super easy and clean. 🎉 I'm going to cover that in my next video, so definitely stick around for it! I'll be showing how this pattern works in a real-world project and why it makes life so much better. I’m excited to share that with you - make sure to hit the notification bell 🔔 so you don’t miss it! 😎 Thanks again for the awesome comment, and stay tuned!

🤣🤣

Hope you enjoyed it and hope your exam went well too 😀

This method is very common to handle protected routes. Of course they are always many different ways to do a thing, as long your method is safe and works, you are good. Will create special video to handle protected routes 😉

@@codingwithlulu thanks!

Coming 😊

Thank you so much for the feedback 😊 hope it helped. Yes you are right. For this video, it's purpose it to explain this pattern concept, that is why