mobile-native-platforms

Use unidirectional data flow with state hoisting: a single immutable UI-state data class exposed as StateFlow from a ViewModel, collected via collectAsStateWithLifecycle(). MVVM is Google's baseline, while MVI adds a stricter reducer pattern with one-off effects via Channel or SharedFlow.

The Composable Architecture (TCA 1.0+) provides Redux-style unidirectional flow with Reducer, State, Action, and @Dependency, integrating Swift Concurrency through .run effects. MVVM or Apple's lighter MV pattern suits simpler apps with less need for testable, composable state.

Yes, Jetpack Security Crypto is deprecated at 1.1.0-alpha07, including EncryptedSharedPreferences and EncryptedFile. Migrate to direct Android Keystore usage or community forks such as Ackee Guardian or dev.spght:encryptedprefs.

Go native when you need deep OS integration such as widgets, complex background work, AR, or peak performance. The Intune App SDK also mandates native, since it officially supports Android, iOS, and .NET/MAUI but not React Native.

Use @HiltViewModel with constructor @Inject, choosing scopes by lifetime: @Singleton for app-wide, @ActivityRetainedScoped to survive configuration changes, and @ViewModelScoped per ViewModel. Dependencies shared across ViewModels should be @ActivityRetainedScoped or @Singleton.

No, there is no encrypted DataStore variant yet. DataStore 1.1.7 offers Preferences and Proto options as an async Flow-based SharedPreferences replacement, but sensitive values require Android Keystore-based encryption handled separately.