Changing the Logo

Learner uses two separate logo assets:

1. In-app logo (shown on the Sign In, Sign Up, Reset Password & Verify Account screens) is built by CommonWidgets.buildLogo() in lib/features/presentation/widgets/common_widgets.dart. It renders the icon at assets/icons/splash.svg next to the "Learner" text label. Swap in your own icon (keep the same file name, or point AppImages.splash in lib/core/constants/app_images.dart at a new file) and edit the label text directly inside buildLogo().
2. App launcher icon (the icon shown on the phone home screen) — replace assets/images/logo.png with your own square PNG (1024×1024px recommended), then regenerate the Android/iOS icons:
   flutter pub run flutter_launcher_icons
   Configured under the flutter_launcher_icons: key in pubspec.yaml.

Changing Colors & Global Theme Settings

All brand colors are centralized in one file — lib/core/constants/app_colors.dart. Update the constants there and the change applies across every screen, since widgets reference AppColors directly instead of scattering hex codes:

class AppColors {
  static const Color primary = Color(0xFF4F46E5);     // buttons, links, active states
  static const Color primaryDark = Color(0xFF4F46E5);
  static const Color primaryLight = Color(0xFFA53A3C);
  static const Color borderColor = Color(0xFFE6E6E6); // input borders, dividers
  static const Color filledColor = Color(0xFFF0F0F0); // input & card fills
  static const Color bgColor = Color(0xFFFBFBFE);     // page background
}

Note: Learner does not include a dark mode / theme-switching feature. Screens read colors straight from AppColors rather than a Flutter ThemeData/ThemeMode object — primaryDark and primaryLight above are just accent shades of the one brand color (for pressed/hover states), not a second full theme. If you want a light/dark switch, wrap GetMaterialApp in lib/main.dart with a GetX theme controller and define a second color set to swap in at runtime.

Connecting Real API Endpoints (Optional)

Learner is a UI template only. It runs completely out of the box with static/mock data and does not require an API, backend, or database of any kind — you can build and ship the UI as-is. This section is only for buyers who want to plug in their own real data.

Every screen's data currently comes from static mock values inside its GetX controller under lib/features/presentation/controllers/ (e.g. home_controller.dart, explore_controller.dart, my_courses_controller.dart). If you choose to connect your own backend, the general approach is:

1. Add Flutter's http or dio package to pubspec.yaml — either works fine for calling a REST API.
2. Create a repository/service class that calls your API and returns the same model shape the controller already expects.
3. In each controller's onInit(), replace the hardcoded list/mock assignment with a call to your new repository method, wrapped in the controller's existing observable loading state so the UI's loading/empty/error states keep working unchanged.
4. Repeat per feature you want to make dynamic — Explore, Course Detail & Curriculum, My Courses, Wishlist, Payment, Certificates, and Notifications each have their own controller.

This is entirely up to you and your project's needs — no screen requires structural or UI changes to support it, only the data source inside the controller you choose to update.