How himanshi-gupta/movieshow works
Project type and purpose
• This is a native Android mobile application (MovieShow) written in Kotlin.
• Purpose: fetches movie data (popular, upcoming, trending, top-rated) from an external API, displays lists in tabs, supports detailed views, and maintains a local watchlist with offline support.
File structure
• Top level: build files (build.gradle, settings.gradle), Gradle wrapper.
• app/: main Android module.
• src/main/java/com/example/movieshow/ contains:
– ui/ & ui/theme/: presentation layer (Compose or XML-based UI + theming).
– viewModels/: ViewModel classes (MVVM).
– repository/: MovieRepo (handles data coordination).
– network/: MovieApi (Retrofit interface).
– database/: Room entities (MovieItem), Dao, MovieDatabase.
– paging/: MoviePagingSource (Jetpack Paging).
– Observer/: network connectivity observers.
– models/: data models mapping API responses.
– factory/: ViewModelFactory classes.
– utils/: constants for configuration.
• Test folders for unit and instrumentation tests.
• AndroidManifest.xml, res/ for resources (drawables, layouts, strings, themes).
• Gradle/proguard rules, .gitignore.
Extract architecture from README
• Uses remote API calls to fetch multiple movie categories.
• Local persistence of watchlist via Room.
• Offline navigation to watchlist.
• Retry logic on network failures.
Relationships and data flow
• UI → ViewModel: UI events (tab selection, add/remove watchlist, retry).
• ViewModel → Repository: request data streams or write operations.
• Repository → Remote Data Source: fetch paged lists via Retrofit + PagingSource.
• Repository → Local Data Source: read/write watchlist entities.
• Repository → ViewModel: returns LiveData/Flow of data.
• ViewModel → UI: exposes UI state (paged lists, network status, watchlist).
• ConnectivityObserver broadcasts to ViewModel to react to offline/online changes.
Architectural patterns & technologies
• MVVM (Model-View-ViewModel).
• Repository as single data orchestrator.
• Room for local persistence.
• Retrofit + OkHttp for networking.
• Jetpack Paging for infinite scrolling.
• LiveData or Kotlin Flow for state propagation.
• Dependency injection via manual factories.
Detail
• Every folder in src/main/java is represented by a component or subcomponent.
• Watchlist flow: UI (Watchlist Screen) → ViewModel → Repo → Room → UI restoration on app launch.
• Offline navigation: ConnectivityObserver → ViewModel → Navigation to Watchlist.