Hi! Im doing Clean Architecture pattern in my app. Let’s say I have a

Product

item. Now, that

Product

must contain

category

and

subcategory

. Currently, the API only returns the

guid

of the category and subcategory. Now the question is. Should the mapping of getting the

category

and

subcategory

from the API and putting them inside the

Product

class be inside the

data

module? OR I can put it inside my

GetProductUseCase

? If I choose the latter. So my usecase would look something like this:

getProducts()
    .zip(repo.getCategory(), repo.getSubCategory())
    .flatMap { 
        product.category = category
        product.subcategory = subcategory
     }

What’s the best practice for this?

using AACs Viewmodel, Is it ok to pass an Application Context within the viewmodel. I need to access a color from resources.

Hi there. I have a question about clean architecture. Which module (

data

,

domain

,

presentation

) is responsible for handling API errors, for example if I have API method

/login

and it returns error

Email is incorrect

where should I handle it? I guess in repository inside

data

module/layer, but maybe I missed smth.

from a structured concurrency standpoint, does it make sense for each

CorotuineScope

job be descended from the job in a fragment (and maybe the fragment is descended from the activity)? I'm thinking something like this.

Passing Data from Fragment to Activity senario ——- from fragment i have a string call helloworld viewmodel.sentMsg("Hello World") then from activity viewmodel.receiveMsg() —- is returning kotlin.Unit

I'm trying to unit test my use cases coroutines using mockk but I don't know how to do the verification of a lambda. I have the gists of the test and the base class. Anyone has experience with this kind of testing? https://gist.github.com/leodeleon22/e22e7954f70ce77f2fdfdbbb854293a6 https://gist.github.com/leodeleon22/640c42ecd86ccde8986bd0541bc4b45d

Would you remind me please, what hack is being suggested by Google nowadays instead of

SingleLiveData

? I remember they've created it and were discouraging its usage after.

any update on how to navigate to dialog fragments in navigation architecture

and also what is next after the deprecation of dialog fragments

Hello , is there a good tutorial for Inversion of Control ,Dependency Injection?

How do you suffix models from the data layer?

UserData

,

UserEntity

,

UserDto

,

UserApi

...? 🙂

Someone know why android navigation component when i press back button reload the actual fragment? Thanks

How do you guys scale MVI?

could be the NavHostFragment be a normal fragment that has logic at the same time

How strict you are with Clean Architecture when it comes to SharePreferencies? Do you go full clean mode, and create usecases for every flag, like

SetShowTutorial

,

IsShowTutorial

, that lead to

Repository

, that knows how to read/write flags from SP?

Did anybody try deep link navigation library from airbnb? Anything to be aware of? https://github.com/airbnb/DeepLinkDispatch

Hi there! Is it okay to have one

GeneralViewModel

, that contains another one (or two no matter)

Specific1ViewModel

? Setting as field we can provide the

Specific1ViewModel

to

GeneralViewModel

Does anyone here feel that using DataBinding is heavy (apk Size) and slow to build?

Hello anyone of you have a "boilerplate" or a "skeleton" to use with a new project? that are divided by modules like

app

core

core-testing

features

(inside different features as a modules)? I'm about to start a new project and I want to have a "guide". Thank you guys 🙂

Surely it was discussed many times, how does your error handling look like? Assuming Retrofit+coroutines setup. Do you go: a) old-fashioned exceptions: return pure type, use try/catch, separate stream of errors in rx, etc. or b) trendy FP style: return wrappers like

Either/Try/Result

If you go

b)

, since you can't use kotlin

Result

type, do you bring Arrow for that? Do you create your custom

Either/Try/Result

? How does it look like?

easiest setup is to have :core for common stuff, features that depends on :core, and top level :app which depends on all features

does anyone have a good resource/udemy class/book that touches on the subject of good practices for library/SDK design

Hello to all. I have a question regarding external services and domain layer. I am developing an application where I am using Google Places SDK and the Autocompletetion Fragment where the user can call the API to get a Place. The Place contains among other properties an

ID

and

Name

. I am also storing a Place Entity with Room in SQLite. After that a user of the App can select a Place from a list and display some details about it. To do that I call Google Places API again to fetch Places Detail with the

ID

of the Place selected. I have build the app around the clean architecture approach but I did not find yet a way to handle external ( Google Place) IDs. I don't want to put them in my domain model but I cannot figure out a way to skip that. How do you handle such cases?

Hey guys! I'm using Flow to emit data from Repositories all the way up to Viewmodels. I've watched some talks at Dev Summit and now it's suggested to switch to LiveData to expose data to activities views. My question is: is it really necessary and what are the differences between exposing as LiveData or collecting values directly from Flow in view's lifecycleScope?

Hi guys. Does anyone know if we have anything new in Navigation Component to send data back to previous Fragment? If not then can someone please suggest me a solution for this. I am not big fan of SharedViewModel for this purpose. One solution i have in mind to observe room in previous screen and update this table from the closing screen. But this seems extra work.

How would you guys test FCM integration? I have my part of the pipe and server unit tested, yet people still complain that notifications dont arrive to which I shrug

tldr; how to do end-to-end push notif. test / something that involved 3rd party service

Hello people, do you use a Result type wrapper in the return types of your components? What if you use Clean Architecture. Would you use a Result type in Repositories, UseCases and ViewModels?

How would you handle inheritance and MVI, output State model in particular? Nesting of parent state?

State(.. my vals, val parentState : ParentState)

? Im not a huge fan of this as concept of ParentState being exposed outside.. maybe flatten it via interface + by delegation?

Have a short question here. The usage of Courotines inside UseCase is bad practice?