Abstraction & Interface 🚀

Mentor's Note: Abstraction is about "Focus." You don't need to know how an internal combustion engine works to drive a car. You just need to know the steering wheel and the pedals! 💡

---

🌟 The Scenario: The Universal Remote Control 📺

Imagine you have a high-tech universal remote.

• The Logic: The remote has a Power Button 🔘 and a Volume Up button 🔊.
• The Abstraction: You don't know how the button talks to the TV. You don't care if the TV is a Sony, LG, or Samsung. 📦
• The Result: You just press the button (The Interface), and the TV responds. The complex electronic signals are Hidden from you. ✅

---

📖 Concept Explanation

1. Abstract Class

An abstract class is a "Semi-finished" blueprint. It can have both regular methods and abstract methods (methods without a body). - Rule: You cannot create an object of an abstract class.

2. Interface

An interface is a "Contract." It only defines what an object should do, but not how it does it. - Rule: A class can implement Multiple Interfaces but can only inherit from one parent class. 🤝

---

🎨 Visual Logic: Contract vs Blueprint

graph LR
    subgraph Contract: ["Interface: RemoteControl 🎮"]
    A[powerOn()]
    B[volumeUp()]
    end
    Contract -- implemented by --> T1["Sony TV 📺"]
    Contract -- implemented by --> T2["LG TV 📺"]

---

💻 Implementation: The Remote Lab

Java (JDK 17+)

// 🛒 Scenario: A Remote Control Contract
// 🚀 Action: Using an interface to define behavior

interface RemoteControl {
    void powerOn(); // ⚙️ Abstract method
}

class SonyTV implements RemoteControl {
    public void powerOn() {
        System.out.println("Sony TV is turning on with a bright logo... ✨");
    }
}

class LGTV implements RemoteControl {
    public void powerOn() {
        System.out.println("LG TV is turning on with a smooth fade... 🎞️");
    }
}

public class Main {
    public static void main(String[] args) {
        RemoteControl myRemote = new SonyTV();
        myRemote.powerOn(); // 🛍️ Outcome: Sony behavior
    }
}

---

📊 Sample Dry Run (Comparison)

Feature	Abstract Class	Interface
Inheritance	extends	implements
Methods	Can have "Real" code	Usually only "Empty" signatures
State	Can have variables (int x)	Can only have Constants
Quantity	Only 1 parent	Multiple interfaces allowed ✅

---

📈 Technical Analysis

• Why use Interfaces?: They allow for Loose Coupling. Your main program doesn't need to depend on specific TV brands; it only depends on the RemoteControl contract. This is how professional plugins and APIs are built! 🧠

---

🎯 Practice Lab 🧪

Task: The Payment Gateway

Task: Create an interface Payment with a method pay(amount). Implement it in two classes: CreditCard and PayPal. Hint: class PayPal implements Payment { ... } 💡

---

💡 Interview Tip 👔

"Interviewers love this: 'Why can't we create an object of an abstract class?' Answer: Because it is incomplete. You can't build a house from a blueprint that is missing the roof!"

---

💡 Pro Tip: "Abstraction is the art of simplifying the complex so you can focus on what really matters." - Anonymous

---

← Back: Polymorphism | Next: Inner Classes →