How florent37/movie_android_flutter works
Project type and purpose
• This is a cross-platform mobile sample:
• A native Android (Kotlin + MVVM) version under android/
• A Flutter version (Dart + Provider/MVVM-style) with Android and iOS targets under flutter/
• Its sole purpose is to let users search movies via the external OMDB API and display results.
File structure
• Two parallel modules:
• android/app/src/main/java/com/github/florent37/mvvmsample/
– search/ contains UI (Fragment, Adapter), ViewModel, ViewState
– omdb/ contains Movie models, OMDBApi interface, Repository
• flutter/lib/ mirrors the same layering:
– search/: SearchPage, ViewModel, ViewState
– omdb/: Repository, models
• Build and config files: build.gradle, pubspec.yaml, Gradle and Xcode project files.
• No backend hosted here; it’s a pure client calling an external REST service.
README
• Confirms two implementations, used in a Medium article.
Detailed breakdown suggestion
• Inside:
– UI Layer: MainActivity/Fragment → MoviesAdapter
– VM Layer: SearchViewModel
– Repo Layer: OmdbRepository + OMDBApi (Retrofit interface)
• Inside:
– UI Layer: SearchPage (StatefulWidget)
– VM Layer: SearchViewModel (ChangeNotifier)
– Repo Layer: OmdbRepository + HTTP client
• Cloud: OMDB REST API (with base URL and endpoints)