How khushnu/portfolio-waleed works
Project type and purpose
• This is a cross-platform Flutter application (mobile, web, desktop) that serves as a personal portfolio, showcasing data (education, skills, projects), interactive UI components, responsive layouts, and an Android RTMP streaming service.
File structure
• Top-level “android”, “ios”, “web”, “linux”, “macos”, “windows” directories each contain the platform-specific boilerplate and native code.
• The “lib” directory contains:
• Data models in lib/Data (education.dart, exp.dart, skill.dart, etc.)
• UI pages in lib/Waleed Portfolio (ToResponsivePage subfolder, pages subfolders for “about”, “contact”, “projects”)
• Reusable functions/services in lib/functions (Alert_Box.dart, GoogleMap_Integration.dart, Rtmp overlay code in ios_livestream.dart & overlaysteam.dart)
• Styles in lib/styles/styles.dart
• Main entry point in lib/main.dart
• Android’s MainActivity.kt and RtmpService.kt implement the RTMP streaming service via a foreground service.
• Build scripts and configuration files: pubspec.yaml, Gradle files, Xcode project files, CMakeLists for desktop.
Insights from README
• It is a starter Flutter project extended into a full-blown portfolio.
• No external backend; all data is local or loaded from assets.
• Uses standard Flutter plugin architecture to register native services.
Elements
• Clear labels: “UI Layer”, “Service Layer”, “Data Layer”, “Platform Channel”, “Android Native Service”, etc.
• UI → Services → Data / Assets
• Services ↔ Platform Channels → Native Layer
• Flutter Engine between Dart VM and Native Embedder
• Blue rectangles for Dart layers (UI, Services, Data)
• Green for Platform Channels
• Orange for Native code per platform