⚠️ Fenix (Firefox for Android) moved to a new repository. It is now developed and maintained as part of: https://github.com/mozilla-mobile/firefox-android
We should decide how we want to implement our application architecture in the new Fenix browser. We have discussed using an MVI architecture as a team, but we should investigate the best options to implement this on Android and we must decide if this is the right solution.
We should examine libraries like Mosby, Reductor, and MvRx as well as just implementing our own solution to bind changing data to the view using RxJava, LiveData, or Kotlin Coroutine Channels. There may be value in developing something in-house if no existing implementation is simple or succinct enough.
bbinto
commented
5 years ago
We should decide how we want to implement our application architecture in the new Fenix browser. We have discussed using an MVI architecture as a team, but we should investigate the best options to implement this on Android and we must decide if this is the right solution.
We should examine libraries like Mosby, Reductor, and MvRx as well as just implementing our own solution to bind changing data to the view using RxJava, LiveData, or Kotlin Coroutine Channels. There may be value in developing something in-house if no existing implementation is simple or succinct enough.
┆Issue is synchronized with this Jira Task