Feature/authentication

[alwin-m]

No description provided.

[alwin-m]

image_picker (direct main)

You explicitly added this package.

It lets your app pick images or videos from the camera or gallery.

---

Platform-specific packages (transitive)

Automatically added by Flutter to support each platform:

• Android, iOS, Web, Windows, macOS, Linux

You don’t import these directly.

---

image_picker_platform_interface

Defines the common API that all platforms must follow.

Think of it as an interface or abstract class.

---

sha256 & url

Used by Dart to verify package security and source.

---

intl (direct main)

You explicitly added this.

Used for date, time, number, and locale-based formatting.

---

Summary

You use one Dart API, Flutter handles platform differences automatically.

[alwin-m]

image_picker (direct main)

This is the package you explicitly added in pubspec.yaml.

What it does:
image_picker provides a simple Dart API to pick images or videos from the device gallery or camera.

Why it’s “direct main”:

• You directly depend on it
• You import and use it in your Flutter code

---

Platform-specific implementations (transitive)

These are automatically pulled in by Flutter. You do not import them directly.

image_picker_android

Handles Android-specific camera and gallery access using native Android APIs.

image_picker_ios

Implements image picking for iOS using Apple’s photo picker and permission system.

image_picker_for_web

Uses browser file input when your Flutter app runs on the web.

image_picker_macos

Provides image picking support for macOS desktop apps.

image_picker_linux

Implements file selection for Linux desktop environments.

image_picker_windows

Implements file picker functionality for Windows apps.

Why they’re “transitive”:
You didn’t add them directly. image_picker depends on them to work on each platform.

---

image_picker_platform_interface

This is the shared contract between Flutter and all platform implementations.

Purpose:

• Defines the methods every platform must implement
• Ensures Android, iOS, Web, and Desktop behave consistently

Think of it like an abstract class or interface in object-oriented programming.

---

sha256 and url fields

These are used by Dart’s package manager to:

• Verify package integrity
• Ensure secure downloads from pub.dev

You never need to modify these manually.

---

intl (direct main)

This is another package you explicitly added.

What it does:
intl is used for internationalization and localization, including:

• Date and time formatting
• Number and currency formatting
• Locale-aware text handling

Why it’s “direct main”:

• You added it yourself
• It’s likely used for formatting dates, times, or localized strings

---

Big picture

This structure allows you to write one Dart API while Flutter handles platform-specific details behind the scenes. The result is clean, maintainable, and platform-independent code.

[alwin-m]

Small Explanation

This code is used to show and hide passwords in the Change Password screen.

Each bool variable controls one password field:

• Old password
• New password
• Confirm password

Passwords are hidden by default for security.

When the eye icon is tapped:

• setState() is called
• The password visibility toggles (hidden ↔ visible)
• The UI updates instantly

This improves security, usability, and user experience.

[alwin-m]

import 'package:google_fonts/google_fonts.dart';

[alwin-m]

These booleans

bool _obscureOldPassword = true;
bool _obscureNewPassword = true;
bool _obscureConfirmPassword = true;

Control whether each password field is hidden or visible

true → password is hidden (••••)

false → password text is shown

Each field has its own variable, so toggling one does not affect the others.

[alwin-m]

Explanation of the Change Password UI Logic

This section explains how the password visibility and input fields work in your Change Password screen.

---

1. Password Visibility State Variables

bool _obscureOldPassword = true;
bool _obscureNewPassword = true;
bool _obscureConfirmPassword = true;

Each boolean controls whether a password field hides (true) or shows (false) the text:

• _obscureOldPassword → Old password field
• _obscureNewPassword → New password field
• _obscureConfirmPassword → Confirm password field

Using separate variables allows each field to toggle visibility independently.

---

2. TextField with Visibility Toggle (Old Password)

TextField(
  controller: oldPasswordController,
  obscureText: _obscureOldPassword,
  decoration: InputDecoration(
    labelText: "Old password",
    suffixIcon: IconButton(
      icon: Icon(
        _obscureOldPassword
            ? Icons.visibility_off
            : Icons.visibility,
      ),
      onPressed: () {
        setState(() {
          _obscureOldPassword = !_obscureOldPassword;
        });
      },
    ),
  ),
)

How it works:

• obscureText hides the password when true
• The eye icon changes depending on visibility state
• Pressing the icon calls setState() and toggles the boolean
• Flutter rebuilds the widget and updates the UI instantly

---

3. New Password & Confirm Password Fields

These fields work exactly the same way as the old password field but use their own state variables:

• _obscureNewPassword
• _obscureConfirmPassword

This ensures toggling one field does not affect the others.

---

4. Layout Spacing

const SizedBox(height: 16);
const SizedBox(height: 32);

• SizedBox(height: 16) adds spacing between fields
• SizedBox(height: 32) adds spacing before the action button (e.g., Update Password)

This improves readability and touch comfort.

---

5. UX & Security Benefits

• Passwords are hidden by default for security
• Users can temporarily reveal passwords to avoid typing mistakes
• Independent toggles improve usability
• Clean, minimal UI consistent with modern Android & iOS standards

---

✅ Result: A secure, user-friendly password update screen that follows best UX practices.