So far I'm an MVP guy, but would like to try AAC

@dave I would say Workmanager and lifecycle awareness are the better investments. While other things like Room have tons of valid alternatives and approaches, Workmanager's main competitors "are" Jobscheduler/FirebaseJobdispatcher, but turns out workmanager uses those two under the hood dependening on the scenario. Evernote's android-job does the same. Dealing with the lifecycle is one of the main tasks you'll have, so having a single way to do it across the app helps (again, we'd been doing it for years with no problem in several ways, but there isn't a "main" solution).

Regarding patterns, Google's Architecture components are oriented towards MVVM, although of course you can use them with your preferred pattern.

Your activity/fragment is a view binder. Don't use it for anything more such as retain state, business logic etc and 99% of your Android lifecycle issues and related issue such as memory leaks will go away