Fatima Hamid - Web Developer

𝐁𝐮𝐢𝐥𝐝𝐢𝐧𝐠 𝐟𝐞𝐚𝐭𝐮𝐫𝐞𝐬 𝐢𝐬 𝐞𝐚𝐬𝐲.
𝐁𝐮𝐢𝐥𝐝𝐢𝐧𝐠 𝐜𝐥𝐞𝐚𝐧 𝐔𝐈 𝐛𝐞𝐡𝐚𝐯𝐢𝐨𝐫 𝐢𝐬 𝐭𝐡𝐞 𝐫𝐞𝐚𝐥 𝐰𝐨𝐫𝐤.

This screen recording continues the same e-commerce project we started without React Router, focusing first on component structure and UI state.

In this step, we introduced routing...
→ without changing the core architecture.

𝐖𝐡𝐚𝐭 𝐭𝐡𝐢𝐬 𝐩𝐫𝐨𝐣𝐞𝐜𝐭 𝐧𝐨𝐰 𝐝𝐞𝐦𝐨𝐧𝐬𝐭𝐫𝐚𝐭𝐞𝐬:

• Client-side routing with React Router DOM
→ Home, Shop, Cart, Checkout, and Contact pages using the same codebase.

• State-driven UI behavior
→ Checkout flow and thank-you popup controlled entirely by local state.

• Conditional rendering for clear UX
→ Feedback appears only when a user action is completed.

• Clear separation of responsibilities
→ Pages manage flow, components stay reusable and focused.

Same project. Same codebase.
Just improving the frontend foundations step by step.

If you followed the earlier post about building the shop without routing, this shows how much you can achieve with clean React fundamentals alone.

Follow — Fatima Hamid - Web Developer.
➥ Tags:

𝐀 𝐬𝐭𝐫𝐨𝐧𝐠 𝐑𝐞𝐚𝐜𝐭 𝐚𝐩𝐩 𝐢𝐬𝐧’𝐭 𝐛𝐮𝐢𝐥𝐭 𝐛𝐲 𝐚𝐝𝐝𝐢𝐧𝐠 𝐦𝐨𝐫𝐞 𝐭𝐨𝐨𝐥𝐬.
𝐈𝐭’𝐬 𝐛𝐮𝐢𝐥𝐭 𝐛𝐲 𝐠𝐞𝐭𝐭𝐢𝐧𝐠 𝐭𝐡𝐞 𝐟𝐮𝐧𝐝𝐚𝐦𝐞𝐧𝐭𝐚𝐥𝐬 𝐫𝐢𝐠𝐡𝐭.

In this project, we focused on frontend structure before introducing anything new.

𝐖𝐡𝐚𝐭 𝐰𝐞 𝐚𝐩𝐩𝐥𝐢𝐞𝐝:

• Clear component responsibility
→ ProductCard, CartItem, shared UI components

• Props vs local state
→ State at page level, data flowing down

• Controlled inputs
→ Checkout form with predictable updates

• Conditional rendering
→ Empty cart, empty lists, loading states

• List rendering with keys
→ Stable product and cart UI

• Derived state
→ Cart total calculated, not stored

• Layout-driven pages
→ Cart summary and items structured at page level

𝐒𝐢𝐦𝐩𝐥𝐞 𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞. 𝐏𝐫𝐞𝐝𝐢𝐜𝐭𝐚𝐛𝐥𝐞 𝐔𝐈. 𝐍𝐨 𝐨𝐯𝐞𝐫𝐞𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐢𝐧𝐠.

Follow — Fatima Hamid - Web Developer.

➥ Tags: