What is recommended way to check user token expiry ? I want to check token expiry by calling server api(using retrofit) and If token expired then move to login screen from any activity or fragment.

What are :android: folks' thoughts on having a high-level representation of navigation in the domain layer? I think it's an implementation concern and should stay in the presentation layer but I want to hear your thoughts and experiences.

Has anybody by change got app links working with custom url scheme? (The feature which identifies a link as "yours" and will not show a disambiguation dialog) -- but doesnt seem to work with custom schemes

Do you keep separate settings.gradle around as not to build all the modules?

should I use

buildSrc

or convert all

.gradle

files to Kotlin dsl, preparing to refactor app to Modules?

But I presume when prefs sync to disc, they have to rewrite the whole thing even though a single value changed, right?

is it possible for a feature module to depend on another feature module?

Hey guys, I'm in doubt with Retrofit and coroutines. If I have a livedata which is returning my favourites films from and API and I observe this livedata and show the films in the screen. If I add a new film in my favourites, is the livedata going to emit this new film? Do I need to call the API again?

Hallo guys, wondering about the pros and cons of doing the following:

class Activity(val delegate = ScreenDelegate()): AppCompatActivity(), Screen by delegate {
...methods
}

I am trying to apply the following function but it doesn't work is there anyone give a hint why: • In the time I receive notification on onReceive of broadcast receiver I call a function in a viewmodel (which is injected into my broadcast receiver) to set aLiveData.value = newValue. However, nothing happened in my fragment. • Then I try to use a local broadcast receiver: in my broadcast receiver on receive I sendBroadcast after notication came in, register it in fragment but it didn't work too. • The last option can be use update database in the time I get notification then observe it in my fragment, but I need to implement the dao, use case and so on I might be an overkill? I still want to figure out why the first 2 options don't work.

btw have anyone ever used gradle flavors to swap string resources like app name? the issue is I have 3 flavor dimensions, and want to AND 1st and 3rd, and it doesnt seem to work, only if I add the 2nd inbetween, however then I multiply it by all 2nd dimension's values which is stupid, I must be missing something

We have a custom view that is used in a lot of places. We want to tie this to a viewmodel and keep all the business logic there. A coworker suggested just passing in the ViewModel and lifecycle owner to the custom view and then observe on the properties. This doesn’t feel right. What do you guys do?

Hello you all 🙋‍♂️, What do you think about this approach? On an Android project with a modularization per feature architecture, would you create a retrofit instance per each feature? Isn't this very costly? My friends and I are currently working on this kind of architecture, and we are in the stage of integrate the REST API. We are trying to isolate as much as we can every feature. But should we create a retrofit instance on each feature module that needs to call a service or should we have another module let's say "data" and handle all the retrofit thing there? What would you do?

Is this any better than having using the backing property that we usually see? This is way has one less property to instantiate so would that make this more memory efficent?

protected val titleLiveData = MutableLiveData<String>()
    
    fun getTitleLiveData(): LiveData<String> {
          return titleLivaData
    }

Hi, with dagger multibinding, is there a way to default to empty set if non are found? Now it throws an error

👋 This is where all the architecture fans and foes gather, right? Our guide to app architecture is more than 3 years old and it’s time to recommend up to date architecture best practices. But we can’t do this without input from ... well, you! If you want to help, start by filling out this survey! Then, some people that opt in to provide even more feedback will be selected to be part of small focus groups that can help us dive deeper into architecture best practices. 🙏 Thank you for helping us improve the Android app architecture! https://docs.google.com/forms/d/e/1FAIpQLSfe-rHdqRF8sznJvj0Jyq-ttoS41aGZLEoP38G0_xQVVy162Q/viewform

What do you think in a project multi-module have for instance app core(or whatever) feature1 feature2 feature3 navigation <-- I'm planning to implement navigation to a multi-module project and is it a good praxis to create a navigation module which is included on each feature and inside of it contains all of the navigation between features?

Good morning I have a question regarding architecture, I have a multi-module project and I'm wondering how can I split the network module, I mean I don't want to create a difference instance of Retrofit everytime so do you know an efficient way to use the same instance of Retrofit if possible but changing the service? And also is ok to create the network module and inside of it every service? Or every service we should create inside the feature module? Because the problem is about the models. Anyone of you have worked with something similar? Thanks.

does the logic in the observe method belong into the ViewModel?

Firebase then groups all of these ApiExceptions to one entry in the web UI, im guessing because the line that throws is the same 😔 Then I have to click through the instances of the crash where I now do see various 400 or 500's ... but im 90% sure its not all and just some "smart" agregate How can I "hack" the crashlytics to see these as separate exceptions (rows), so I can see actually all of these?

hi all! I am making some home-made application where I use a data flow like: Repository <-> UseCase <-> ViewModel <-> View So basically UseCase with MVVM I can find some basic introductions about the usecase pattern, but does anyone have some in-depth article/repo example? I am looking for information about things like this: • Things like observing data (should I first fetch data and after that observe on it, within the useCase) • when to fire a use case and for specific things (like would you fire a usecase to validate input while typing, or only while submitting?) • Should I observe fields from a usecase, or only the output from the execution? • What are the rules where to put specific logic, in the view model or usecase (or both)?

when you use

LiveData<Resource<T>>

, doesn't the fragment have to make too many decisions? I.e. what to do for each result

Should the fragment or the ViewModel decide when to show this snackbar? My LoginFragment pops itself from the backstack when the user is logged in:

mainViewModel.sessionManager.firebaseUser.observe(viewLifecycleOwner) {
            if (it != null) {
                previousSavedStateHandle.set(LOGIN_SUCCESSFUL, true)
                binding.editTextEmail.clearFocus()
                binding.editTextPassword.clearFocus()
                findNavController().popBackStack()
            }
        }

The login method in the ViewModel looks like this:

fun login(email: String, password: String) {
        if (email.isEmpty() || password.isEmpty()) {
            viewModelScope.launch {
                snackBarMessage.send("Please fill out all fields")
            }
            return
        }

        viewModelScope.launch {
            _loginLoading.value = true
            when (val result = authRepository.login(email, password)) {
                is AsyncResult.Success -> {
                    val firebaseUser = sessionManager.firebaseUser.value!!
                    snackBarMessage.send("Logged in as ${firebaseUser.displayName}")
                }
                is AsyncResult.Error -> snackBarMessage.send(
                    result.throwable.localizedMessage ?: "Something went wrong"
                )
            }
            _loginLoading.value = false
        }
    }

My question is about that confirmation snackbar (

"Logged in as ${firebaseUser.displayName}"

). Does the code that triggers the snackbar belong into the when statement inside the ViewModel (where it is right now), or can/should I put it into the

if (it != null)

block inside the fragment? I'm asking this because the latter option would get rid of the problem that the snackbar doesn't arrive early enough before the fragment is popped from the backstack. But I am not sure if showing a snackbar is considered "business logic" here and should be in the ViewModel. (The snackbar event is send via a Kotlin channel here that the fragment reacts to)

If I would like to call api when Fragment onPause. Is it the case to use

GlobalScope.launch

?

// Fragment

override fun onPause() {
    viewModel.leave()
}

// ViewModel

fun leave() {
    GlobalScope.launch {
        repository.leave() 
    }
}

What the next step architecture-wise when methods in my repository become big and complex? Should I just keep it like this in the repository?

I have this

ItemTouchHelper

in a Fragment. Is it okay to show the snackbar here directly or should the ViewModel trigger it via an event?

ItemTouchHelper(object :
                ItemTouchHelper.SimpleCallback(0, ItemTouchHelper.LEFT or ItemTouchHelper.RIGHT) {
                override fun onMove(
                    recyclerView: RecyclerView,
                    viewHolder: RecyclerView.ViewHolder,
                    target: RecyclerView.ViewHolder
                ): Boolean {
                    return false
                }

                override fun onSwiped(viewHolder: RecyclerView.ViewHolder, direction: Int) {
                    val task = taskAdapter.currentList[viewHolder.adapterPosition]
                    viewModel.deleteTask(task)

                    Snackbar.make(requireView(), "Task deleted", Snackbar.LENGTH_LONG)
                        .setAction("UNDO") {
                            viewModel.insertTask(task)
                        }
                        .show()
                }
            }).attachToRecyclerView(recyclerViewTasks)

How to hold the reference of the binding object in an activity? This is how we are handling

private lateinit var binding: FragmentGardenBinding

Sometimes when activity is resumed, I'm getting the following crash and it's unable to reproduce

lateinit property binding has not been initialized

Just published a blog post about MVI architecture with android using kotlin with a github simple repo as well, constructive feedbacks are welcome 😃 : https://rimgazzeh.medium.com/mvi-architecture-with-android-fcde123e3c4a

Does anyone here still use MVP? If so, do you use databinding or LiveData? And what are your reasons for using MVP?