How broscr/iptv-player works
Project type and purpose
• This is an Android mobile application (“IPTV Player”) whose sole purpose is to load and play IPTV streams from M3U playlist files. It’s built in a single Gradle “app” module with standard Android project conventions (Activities, Fragments, resources, tests).
File structure
• Top-level: build scripts, Gradle wrapper, settings.gradle, LICENSE, README, images
• “app/” module:
• src/main/java/com/broscr/iptvplayer – application code organized into packages: adapters, database, filereader, models, ui (activities & fragments), utils
• src/main/res – layouts, drawables, menus, values (themes, strings)
• src/androidTest & src/test – instrumentation and unit tests
• Dependencies declared in app/build.gradle include Realm (local DB), ExoPlayer (media playback), EasyPermissions, Timber.
Key insights from the README
• Reads only M3U files (local or remote)
• Screenshots show screens: File select → Home (categories) → Channel list → Player → Favorites → About
• Uses Realm to store favorites/metadata, ExoPlayer to stream, EasyPermissions for runtime storage/Internet permissions, Timber for logging
Main components
a. Presentation Layer
• Activities & Fragments: FileSelectActivity, MainActivity (home/categories), ChannelActivity (list), PlayerActivity, AboutFragment, FavoriteFragment
• Adapters & ViewModels: CategoryAdapter, ChannelListAdapter, SearchAdapter, ChannelViewModel, AboutViewModel, etc.
b. Domain / ViewModel Layer
• ViewModels mediate between UI and Data Layer
• ChannelViewFactory builds channel entry views
c. Data Layer
• FileReader: parses M3U files and extracts categories + channel URLs
• IPTvRealm: manages Realm database for favorites and caching metadata
d. Playback Engine
• ExoPlayer component invoked by PlayerActivity for video/audio streaming
e. Utilities & Services
• EasyPermissions: requesting READ_EXTERNAL_STORAGE or network permission
• Timber: centralized logging
• Helper classes for click callbacks (CategoryOnClick, ChannelOnClick)
f. External Systems
• Local file system (M3U file selected by user)
• Network endpoints for live streams encoded in M3U
• Third-party libraries (Realm, ExoPlayer, etc.)
Relationships and flows
• User taps “Select File” → FileSelectActivity → EasyPermissions → FileReader reads/parses M3U → populates Model objects (Category, Channel) → stored or cached via IPTvRealm → ViewModel exposes LiveData to MainActivity/Fragments → Adapters render lists
• User selects a channel → ChannelViewModel provides channel URL → PlayerActivity initializes ExoPlayer with URL → ExoPlayer streams content → video view in UI
• Favorite toggle → ViewModel updates Realm database → FavoriteFragment reads from Realm
• Logging events flow from all layers through Timber to the Android log.
Architectural patterns & design principles
• MVVM (Model-View-ViewModel) in UI packages
• Repository-style Data Layer (FileReader + Realm as data sources)
• Clear separation of concerns: UI, business logic, data storage, playback engine
• Dependency on open-source libraries kept modular