How aayush9029/nativeyoutube works
Project Type & Purpose
• Type: Native macOS menu-bar application, built with SwiftUI & MVVM.
File Structure
Top-level:
– .github/workflows/swift.yml → CI build/test
– NativeYoutube.xcodeproj → Xcode project files
– NativeYoutube/ → source root
Under NativeYoutube/:
• API/ → network request wrappers (PlaylistsRequest.swift, SearchRequest.swift)
• Models/ → data types, constants, enums
• ViewModels/ → state containers (AppStateViewModel, SearchViewModel, etc.)
• Views/ → SwiftUI screens & shared components
• ViewModifiers/ → SwiftUI style modifiers
• Extensions/ & Helpers/ → utility functions & view bridging
• Assets, Info.plist, entitlements, App entry (NativeYoutubeApp.swift)
Pull Architecture Hints from README
• macOS 13+ menu-bar app
• Requires Google API key
• Features: search, playlists, custom playlist ID, preferences UI
Main Components & Their Relationships
a. Frontend/UI Layer
– NativeYoutubeApp (App entry) creates a MenuBarIcon → On click, presents Views.
– Views: SearchVideosView, PlayListView, PreferencesView, Shared sub-views.
b. ViewModel Layer (MVVM)
– AppStateViewModel: orchestrates which view is visible & global state.
– SearchViewModel & PlayListViewModel: handle search and playlist flows.
– YoutubePreferenceViewModel: stores & retrieves API key & custom IDs.
c. Model Layer
– VideoModel, Enums, Constants describe data structures.
d. API / Network Layer
– PlaylistsRequest & SearchRequest: Perform HTTP calls to YouTube Data API (via URLSession/async).
– Parse JSON → Model objects.
e. Persistence & Settings
– UserDefaults (via ViewModels) or Keychain for API key.
f. External Service
– YouTube Data API (requires API key, returns JSON).
Important Architectural Patterns & Principles
• MVVM: clear separation of view logic (Views) from business logic (ViewModels).
• Single source of truth: AppStateViewModel manages global UI state.
• Dependency inversion: Views depend on abstracted ViewModels, not concrete network code.
• Async/await or Combine for reactive data flows.
Finishing Touches
– Label every component clearly.
– Show arrowheads to indicate data/control flow.