Great Proposal @Rohitverma9625

I plan to reduce the no. of Activitys during the whole modularization + migration task, as we'll be writing each feature module from scratch(inspired by existing code).
We can easily replace AboutActivity, NotificationActivity, ProfileActivity with Composable screens and reduce the complexity of launching individual activities for such small screens.

Great Proposal @Mechi4895,

@Inject
@IoDispatcher
private val ioDispatcher: CoroutineDispatcher

fun loadContributions() {

viewModelScope.launch(ioDispatcher) {
    try {
        val result = repository.getContributions()
    } catch (e: Exception) {
        // Handle error
    }
}

@VoidRaven-18

The following feature modules will be prioritized:

Auth Module: Login, signup, and session management.
Welcome Module: Onboarding and initial user flow.
Profile Module: User profile, achievements, and leaderboard.
Contributions Module: User uploads and contribution tracking.
FilePicker Module: Media selection and file handling.
{F73862357}

Great Proposal,

class LoginViewModel @Inject constructor(

private val loginRepository: LoginRepository,
private val savedStateHandle: SavedStateHandle  // Survives process death

) : ViewModel() {

Thanks for the proposal.