🚀 Day 6/100 — #100DaysOfCode Journey Update Today was all about strengthening my #ReactNative skills and exploring both functional and class components. Here's what I covered: ✅ FlatList – Learned how to efficiently render large lists and dynamic data. ✅ Grid Layouts – Created responsive grid layouts using both FlatList and the map() function. ✅ Class Components – Revisited class components, state management, and handling user input. ✅ Weather App – Built a simple weather app using wttr.in API to fetch live weather data and display it neatly in the UI. 📚 Key takeaways: Understanding when to use functional vs class components. Managing state effectively in both component types. Using FlatList for performance-optimized list rendering. Combining layout strategies to create clean, responsive UIs. 💡 Feeling more confident in structuring React Native apps and handling real-world data fetching! #ReactNative #Programming #DeveloperJourney #JavaScript #WebDev #TechLearning #AppDevelopment #100DaysOfCode If you want, I can also make a slightly shorter, punchy version for LinkedIn that’s more scroll-friendly but still professional. Do you want me to do that?
"Day 6 of #100DaysOfCode: Mastering React Native components and building a weather app"
More Relevant Posts
-
🚀 Mastering Props in React — The Key to Reusable Components! In React, props (properties) are one of the most powerful concepts. They allow you to pass data from one component to another, making your UI dynamic, reusable, and easier to maintain. Think of props as function arguments — you send data from parent to child so the child can render content based on that data. 🔍 Why Props Matter? ✔️ Help create reusable components ✔️ Support one-way data flow ✔️ Make apps more organized and modular ✔️ Keep components dynamic and flexible 📌 Simple Example // Parent Component function App() { return ( <div> <Greeting name="Amy" /> <Greeting name="React Learner" /> </div> ); } // Child Component function Greeting(props) { return <h2>Hello, {props.name}! 👋</h2>; } 💡 Here, the App component passes different name values as props to the Greeting component — making it reusable and dynamic. 🧠 Pro Tip Use destructuring for cleaner code: function Greeting({ name }) { return <h2>Hello, {name}! 👋</h2>; } ✨ If you're learning React, understanding props is your first big step toward building powerful, component-driven UIs! #React #ReactJS #WebDevelopment #Frontend #JavaScript #LearnReact #Coding #Developers #PropsInReact #ReactTips #WomenWhoCode #CodeNewbie #Programming #TechLearning #ReactComponents #FrontendDevelopment #100DaysOfCode #SoftwareEngineering #BuildInPublic
To view or add a comment, sign in
-
🧠 Project Story: Building My “Product Filter & Sort App” As part of strengthening my JavaScript fundamentals, I wanted to go beyond just reading syntax. I wanted to build something real — something that could take raw data and make it interactive for users. That’s how the idea of a Product Filter & Sort App came to life. At first, my biggest challenge was structuring the logic — how to handle multiple products, filter them dynamically, and sort them efficiently. My initial code didn’t behave as expected (yes, some frustrating console errors too 😅). But instead of giving up, I decided to dig deeper into array methods like filter(), sort(), and map(), and learned how DOM manipulation brings everything together. After debugging and refining the logic, I finally created a working app where users can: ✅ Filter products based on conditions like price or category ✅ Sort them dynamically in ascending or descending order ✅ View live updates on the webpage — all powered by JavaScript This small project taught me one big lesson: “Logic isn’t built by reading — it’s built by doing.” Each project I build takes me one step closer to becoming a Full Stack Web Developer and AI/ML Engineer. #JavaScript #WebDevelopment #Frontend #CodingJourney #LearningByBuilding #AIEngineer #FullStackDeveloper #Projects #SakethTechSpeaks
To view or add a comment, sign in
-
🔹 Mastering React Hooks (Part 2): The Power of useEffect ⚛️ If useState helps us manage what changes in our app, then useEffect helps us control what happens when things change. What it does: useEffect allows you to perform side effects in functional components — tasks that happen outside the normal UI rendering cycle. These include: Fetching data from APIs Updating the document title Managing event listeners or subscriptions Handling timers and intervals Simply put, useEffect runs after every render (or when certain data changes), making it essential for any dynamic, data-driven application. 🌍 Real-World Example: Imagine a weather application 🌦️ that displays live temperature data when a user opens the page. When the component first loads, it automatically fetches data from a weather API and displays it. Later, if the user changes their city, the app fetches new data instantly — all handled inside useEffect. This ensures: ✅ Data is fetched at the right time. ✅ UI updates only when data changes. ✅ No unnecessary API calls or reloads. Why it’s powerful: Controls component lifecycle behavior in a simple way. Helps manage asynchronous tasks like API calls. Keeps your logic clean and organized. Replaces complex lifecycle methods (componentDidMount, componentDidUpdate, componentWillUnmount) with one unified hook. Key takeaway: “useEffect bridges the gap between your app’s logic and the outside world — connecting your UI with real-time data, APIs, and user actions.” ✨ Stay tuned for Part 3 — where I’ll dive into useContext and how it simplifies data sharing across components. #KIT #StemUp #ReactJS #ReactHooks #WebDevelopment #Frontend #JavaScript #useEffect #Coding #DeveloperCommunity #LearningSeries #ContinuousLearning #TechInsights
To view or add a comment, sign in
-
🚀 Leveling Up with React.js Context API! In my recent React learning journey, I explored the Context API — and it truly simplified state management across my app. Instead of passing props down multiple layers, Context lets you share data globally in a clean, efficient way. Here’s what I learned and practiced: 🔹 Creating and using Context with createContext() 🔹 Providing values through a Context.Provider 🔹 Accessing data anywhere with useContext() 🔹 Structuring reusable and maintainable global state logic 💡 It’s perfect for handling themes, authentication, and user preferences — without bringing in heavy libraries like Redux for small-to-medium projects. Next up, I plan to integrate Context API with custom hooks for even cleaner and scalable architecture. If you’ve also used Context in your projects, I’d love to hear your experience — what use cases worked best for you? #ReactJS #FrontendDevelopment #WebDevelopment #JavaScript #LearningInPublic #ContextAPI
To view or add a comment, sign in
-
🚀 Day 8 of My MERN Stack Journey – Mastering Advanced React Patterns! ⚛️ Today’s focus: taking my QuizNova App to a more scalable, professional level with clean React architecture and better code reusability 💪 🎯 What I built today ✅ Implemented Protected Routes for secure navigation ✅ Created custom hooks (useAuth, useFetch) for cleaner, reusable logic ✅ Improved global state with Context API ✅ Added auth persistence (user stays logged in after refresh) ✅ Refined folder structure for a production-ready app 💡 Key Takeaways: 🔹 Context API eliminates prop drilling and centralizes app state. 🔹 Custom Hooks = cleaner, reusable, and testable logic. 🔹 Protected Routes ensure only logged-in users can access private pages. 🔹 A clean architecture = easier debugging + faster development later. ⚙️ Folder Snapshot: frontend/ ├── hooks/ │ ├── useAuth.js │ └── useFetch.js ├── routes/ │ └── ProtectedRoute.jsx ├── context/ │ └── AuthContext.jsx 📈 Next Up: Day 9 – Admin Panel + Quiz Management (CRUD Dashboard) 🔧 Time to empower the backend with full control from the UI side! 💬 Your Turn: Have you ever implemented Protected Routes or Custom Hooks in your React project? Share your experience below 👇 ✨ #ReactJS #MERNStack #WebDevelopment #JavaScript #FrontendDev #LearningJourney #QuizNova #FullStackDeveloper #ContextAPI #CustomHooks #LinkedInCodingJourney
To view or add a comment, sign in
-
🎉 Just hit a major milestone on the "Code Pulse" blogging app! The entire CRUD (Create, Read, Update, Delete) lifecycle for Categories is now fully functional. I’ve implemented: 🔍 Read Single (GET by ID): Created a dedicated API endpoint and an Angular component to fetch and display one specific category object for editing. ✏️ Update (PUT/PATCH): Developed the API endpoint and the Angular form submission logic to successfully modify and persist changes to existing categories. 🗑️ Delete (DELETE): Added a secure API endpoint and UI logic to permanently remove categories, completing the full data lifecycle. ✨ Improved UX: The editing workflow (View/Edit/Delete) is fully functional, ensuring a seamless experience for administrators. See the quick demo in action below! 🎥 👇 Up Next: Starting the core feature: Building the Blog Post Creation Form (UI/API) and listing the results! #DotNetDeveloper #Angular #ASPNETCore #FullStack #CRUD #CodePulse #Programming #WebDevelopment #Csharp #SoftwareDevelopment #Frontend #Backend #CodeLife #BloggingApp
To view or add a comment, sign in
-
🎨 React: More Than a Library — It’s a Mindset When I first started working with React, I thought it was just another front-end framework for building UIs. But over time, I realized — React teaches us how to think in components, how to separate logic from presentation, and how to make the UI truly dynamic. Here’s what makes React development exciting today 👇 ⚡ Component Reusability – Build once, reuse everywhere. It’s not just efficient — it keeps your codebase clean and scalable. 🔁 State Management Done Right – Whether it’s Context API, Redux, or Zustand — managing data flow is at the heart of great UI design. 🚀 Performance Matters – Lazy loading, memoization, and React Suspense are game changers when every millisecond counts. 🧠 Hooks Revolutionized Logic – useEffect, useMemo, useCallback — they’ve changed how we handle lifecycle and side effects entirely. 🌐 Frontend Meets Backend – With React Query, Axios, and modern APIs, frontends are more intelligent and data-driven than ever. React isn’t just about building interfaces — it’s about building experiences that feel alive. And the best part? The learning never really stops. 💡 What’s one React trick or concept that completely changed the way you code? ⚛️👇 #ReactJS #FrontendDevelopment #JavaScript #WebDevelopment #UIUX #CodingLife #SoftwareEngineering #TechInnovation #WebPerformance #TypeScript #ModernWeb #TechCommunity #SoftwareEngineering #DeveloperLife #FullStackDeveloper #DeveloperCommunity #ProgrammingLife #TechInnovation #ReactDeveloper #FrontendEngineer #WomenInTech #ModernWeb #CleanCode #WebDevelopment #CodeWithPassion #BuildInPublic #EngineeringExcellence #JavaScript #ReactJS #FrontendDevelopment #WebDesign #TypeScript #CodeNewbie #LearningEveryday #TechCareers #AgileDevelopment #DevOpsCulture #CloudEngineering #DigitalTransformation #GitHubActions #CICD #UIUXDesign #CodingCommunity #InnovationInTech #SoftwareCraftsmanship #DevelopersJourney #TechLeadership #CloudNative #OpenSourceCommunity
To view or add a comment, sign in
-
-
When you’re starting with React, one of the most confusing moments is when you update a state variable… and nothing changes on the screen. Here’s why 👇 React doesn’t react to value changes — it reacts to state triggers. When you call setState, React knows something changed, prepares a new “snapshot” of your data, and decides when and how to re-render efficiently. But if you change the state directly, React has no idea. It doesn’t re-render because it never got the signal. This is called immutability — React creates new versions of state instead of changing the old one. That’s how it keeps your app predictable, efficient, and bug-free. In this post, I’ve explained in plain language: ✅ How React’s state engine actually works ✅ Why direct mutation fails silently ✅ What “immutability” and “pure functions” really mean ✅ The mindset shift from “coding UI” to “managing data flow” If you’re a student or beginner learning React, this concept is a game-changer. It’s not just about syntax — it’s about understanding how React thinks. Once you get that, everything else starts to click. 💬 Share this with a friend who’s learning React — this one tip can save hours of debugging. #ReactJS #WebDevelopment #FrontendDevelopment #JavaScript #SoftwareEngineering #CollegeProjects #CareerInTech #LearnToCode #Codeviji
To view or add a comment, sign in
-
🌟 Day 20 – Wrapping Up React.js: Completing the Core Concepts 🌟 Today marked the final stretch of my React.js fundamentals journey — connecting all the dots and exploring the remaining concepts that make React a complete front-end powerhouse. 🔹 What I Covered Today 1️⃣ Conditional Rendering Learned how to display components dynamically based on certain conditions using simple if statements, ternary operators, and logical &&. This makes apps respond intelligently to user actions and state changes. 2️⃣ Lists & Keys Explored how React efficiently renders lists of data using .map() and why keys are crucial for maintaining stable identity between re-renders. Without keys, React wouldn’t know which elements changed. 3️⃣ Forms & Controlled Components Worked with form inputs, managing their values using state to keep everything in sync. Realized how easy React makes handling user input once you grasp the concept of controlled components. 4️⃣ Lifting State Up When multiple components need the same data, it’s better to store it in their closest common ancestor. This pattern keeps data consistent across the app and avoids confusion. 5️⃣ Props Drilling & Context API Understood the issue of props drilling — passing data through multiple layers unnecessarily. Explored the Context API as a cleaner solution for managing global state without complex libraries. 6️⃣ useRef & useMemo Hooks useRef → For directly accessing DOM elements or storing mutable values without re-rendering. useMemo → For performance optimization, preventing expensive recalculations on each render. 7️⃣ Project Structuring & Best Practices Focused on organizing components, separating logic from presentation, and keeping the folder structure modular for scalability. 🔹 Reflection Completing React’s core felt like unlocking a new mindset — it’s no longer about writing code, but about designing interactive systems. Each concept (from state to context) adds a layer of flexibility, making apps powerful yet maintainable. React isn’t just a tool; it’s a thought process — modular, efficient, and dynamic. With the fundamentals now solid, I’m ready to move toward real-world React projects next. #ReactJS #JavaScript #FrontendDevelopment #WebDevelopment #ReactHooks #ContextAPI #WebApps #100DaysOfCode #DeveloperJourney #ModernWeb #CodingLife #LearnReact #UIDevelopment #CodeDaily #WebDevCommunity
To view or add a comment, sign in
-
More from this author
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development