Building Movie Search App with React.js

🚀 Day 7 of Building React Projects Today I built a Weather Application using React.js. This project allows users to search for any city and view the current weather information using a weather API. ✨ Features: • Search weather by city name • Display temperature and weather condition • Shows weather icon • Simple and responsive UI • Real-time data using API 🛠 Tech Stack: React.js JavaScript HTML CSS Weather API 💻 Source Code: https://lnkd.in/dasKibUN #ReactJS #JavaScript #FrontendDevelopment #WebDevelopment #LearningInPublic

most React developers have too many useEffects. i did too. until i read this rule and couldn't unsee it: if you're using useEffect to sync state with another state you don't need useEffect. here's what i mean. (the pattern 1 .. i see everywhere) but pattern 2 give same result . no effect. no extra render cycle. useEffect is for syncing React with something outside React. - fetching data from an API - setting up a subscription - manually touching the DOM not for calculating values you could just... calculate. every unnecessary useEffect is a hidden render cycle your users pay for. before you write useEffect ask one question: am i syncing with something outside React, or am i just doing math? if it's math delete the effect. #reactjs #typescript #webdevelopment #buildinpublic #javascript

🚀 React Re-rendering — Key Concepts Re-rendering is the core of how React keeps UI in sync with data. Without it, there would be no interactivity in our applications. Here are some important insights I've learned: 🔹 State updates are the primary trigger for re-renders 🔹 When a component re-renders, all its child components re-render by default 🔹 Even without props, components still re-render during the normal render cycle (without use of memoization). 🔹 Updating state in a hook triggers a re-render, even if that state isn’t directly used 🔹 In chained hooks, any state update will re-render the component using the top-level hook 🔹 “Moving state down” is a powerful pattern to reduce unnecessary re-renders in large applications #ReactJS #FrontendDevelopment #WebDevelopment #JavaScript #SoftwareEngineering #LearningInPublic

import React from 'react'; Feels like just a line. But that one line can quietly pull in ~100kb - 1mb of bundle size …and all that JavaScript your browser now has to, download, parse, and execute. It introduces layers—abstractions, dependencies, and more JavaScript to the browser. And before you realize it, your “simple project” has grown into hundreds of KBs… sometimes MBs. React isn’t heavy. It just makes it very easy to be careless. If your project truly doesn’t need complex state, routing, or heavy UI logic—why start there? Frameworks like Petite Vue or Alpine.js let you add interactivity without committing to an entire ecosystem. Or if you like JSX (like I do), Preact would do just fine. Just this one decision—choosing simplicity over overengineering— could save you in costs, and probably users you’d otherwise lose to slow load times. And remember, React exists because Facebook had a problem, and you probably don’t have it yet. #WebDevelopment #Frontend #JavaScript #ReactJS #SoftwareEngineering

🚀 Understanding useEffect in React — Made Simple! While learning React, one concept that really stood out to me is useEffect. It helps us handle actions that happen after a component renders. 🔹 What is useEffect? It runs code after the component renders and reacts to changes in state or props. 🔹 Basic Syntax: useEffect(() => {   // your code here }, [dependencies]); 🔹 How it works: 👉 Component renders 👉 useEffect runs 👉 State/props change 👉 Component re-renders 👉 useEffect runs again 💡 Key Idea: Runs after render & reacts to changes This hook is very useful for: ✔ API calls ✔ Data fetching ✔ Updating UI dynamically Still exploring and improving my frontend skills step by step 🚀 #ReactJS #useEffect #FrontendDevelopment #WebDevelopment #JavaScript #LearningJourney

Mastering useState: The Most Important Hook in React If you're working with React, useState is one of the first hooks you learn — and also one you’ll use in almost every component you build. Yet many developers still use it incorrectly and run into stale state or unnecessary re-renders. useState allows you to add state to functional components. It returns an array with two values: the current state and a setter function. const [count, setCount] = useState(0); The real power (and common pitfall) comes when your new state depends on the previous state. Correct way: Using the functional updater (prev) => guarantees you always get the latest state, even when multiple updates happen quickly. A few best practices I always follow: Never mutate state directly. Always create a new object/array using the spread operator (...prev). Use computed property names [dynamicKey] when your key comes from a variable. Keep state as simple as possible. If your state object gets too complex, consider useReducer. I’ve seen many bugs disappear simply by switching from setState(newValue) to the functional form when the update relies on previous values. Whether you’re building a small UI or a complex audio/video player like the one I was recently working on, mastering useState patterns makes your code more predictable, cleaner, and easier to debug. What’s one useState trick or gotcha you’ve learned? Drop it in the comments #React #JavaScript #WebDevelopment #Frontend #CodingTips

This is where React actually starts making sense… At first, everything looks confusing — but then you learn Props & State, and suddenly… things click. ⚡ Props are how your components communicate. They pass data from parent to child — clean and predictable. State is what makes your app alive. It controls changes, updates UI, and handles user actions. 👉 Props = Data coming in 👉 State = Data changing inside Master these two… and you move from writing static pages to building interactive, real-world applications. Most beginners skip deep understanding here — and that’s exactly why they get stuck later. Don’t just learn React… understand how it thinks. #ReactJS #FrontendDevelopment #JavaScript #WebDevelopment #CodingJourney #LearnToCode #DevelopersLife #UIEngineering #ReactBasics #TechSkills

🚀 Day 9 of Building React Projects Today I built a Login & Registration System using React.js. This project focuses on user authentication flow where users can register, log in, and manage their access with a simple and responsive UI. ✨ Features: • User Registration • User Login Authentication • Form validation • Error handling for invalid inputs • Responsive UI 🛠 Concepts Used: • React Hooks (useState) • Form Handling • Conditional Rendering • Basic Authentication Logic 💻 Tech Stack: React.js JavaScript HTML CSS 🔗 GitHub Repository: https://lnkd.in/dDTrzHXW #React #JavaScript #WebDevelopment #FrontendDevelopment #LearningInPublic #ReactProjects

Starting My React.js Journey – Basics with Code! Today, I revisited the fundamentals of React.js, and I believe mastering the basics is the key to building powerful applications. Sharing a quick snippet that demonstrates how simple and clean React can be import React from "react"; function Welcome() { const name = "Developer"; return ( <div> <h1>Hello, {name} </h1> <p>Welcome to React Basics!</p> </div> ); } export default Welcome; What this covers: - Functional Components - JSX (JavaScript + HTML) - Dynamic Data Rendering using variables Key Learning: React is not just a library — it's a mindset of building reusable and maintainable UI components. Next Steps: - Props & State - Event Handling - Component Lifecycle Consistency beats intensity. Small steps every day = Big growth #ReactJS #WebDevelopment #JavaScript #Frontend #CodingJourney #100DaysOfCode

Day 26 #100DaysOfCode 💻 Today I learned about Function, Component, State & Event in Next.js. 🔹 Function Functions are reusable blocks of code used to perform specific tasks. 🔹 Component In Next.js, everything is a component. It helps to break UI into reusable pieces. 🔹 State State is used to store dynamic data inside a component and re-render UI when data changes. 🔹 Event Events handle user interactions like clicks, input, form submission, etc. 💻 Code Snippet: "use client"; import { useState } from "react"; export default function Counter() { const [count, setCount] = useState(0); const handleClick = () => { setCount(count + 1); }; return ( <div> <h2>Count: {count}</h2> <button onClick={handleClick}>Increase</button> </div> ); } 🚀 Small reflection: Understanding these core concepts makes building dynamic and interactive apps much easier. #NextJS #ReactJS #WebDevelopment #JavaScript #Frontend #CodingJourney #Akbiplob