Thanks for including the test part. That's always missing in dev videos!

Hi Phil, Thank you for this great content. Just a quick revision when you do the following: if(hasError) { state = state.copy( emailError = emailResult.errorMessage, passwordError = passwordResult.errorMessage, repeatedPasswordError = repeatedPasswordResult.errorMessage, termsError = termsResult.errorMessage ) return } The state should be modified regardless of an error here. While I was watching the video at the end you get the toast and the emailError is still not null because of hasError being false. So the state modification should get extracted out of that block and placed before the hasError check: state = state.copy( emailError = emailResult.errorMessage, passwordError = passwordResult.errorMessage, repeatedPasswordError = repeatedPasswordResult.errorMessage, termsError = termsResult.errorMessage ) if(hasError) { return }

Another quality tutorial from Phillip! Thank you man!

You speak calmly and you remind me of Bob Ross, but showing expertise in Android development. What a great video 😁

Great video. Regarding unit testing, isn't it better to use interface impl pair for the use cases? Also, when asserting values, when you use assertEquals, the first parameter should be the value you expect, and the second value should be the value that you test. Regardless, when you test booleans, you can use assertTrue and assertFalse.

I prefer to create an after text changed listener on the edit texts that saves all the edit texts each time any text is changed. All the text is then tested in the use case and the returned messages are reviewed within the UI with a "when" bracket that will only show one message at a time. When there are no messages to show, the last option in the "when" bracket will enable the button to be clickable.

Nice video bro 👌 I like the use of Channels, they seem quite good in a combination with Compose.

Thanks a lot. Very interesting and useful video 👍

One of my favorites about kotlin is, its Sealed Class. And I think it suits best for this kind of case. I created sealed class with children of every possible outcome, make domain layer don't care about wording and let presentation layer map it.

Great content again. Thanks for making such wonderful video. Complete this video by making network call handling success and failure case. How to propagate error to UI .

Excellent as always. We could add on the TextFields a maxLines = 1 and singleLine = true otherwise we could have many lines or an ' '

very helpful, Thank you!

Duuuuuuude! This is supper cool example! Respect!!!

Hello there, great and pretty complete video! Thank you for your hard work Philipp I have a question: how do you End-to-End test it? I explicitly followed this video and the one with testing (linked to your Note app) and whenever I ask the test to click on the Submit button and check if I have a new Text() displayed (with the explicit error), my test fails since it doesn't seem to reload the layout. Did it already happen to somebody?

I've mix this video and the "This Is My FAVORITE Error Handling Class" one to valid custom user input and it work greats !

Amazing quality content!

Super PRO Champions League content Phillipp! Thanks!!

I have a weird question. Is there any chance that when using a state hosted in the viewmodel or in a data class as we did in this tutorial, the UI is rendered slower? For example, when I am creating a Switch, if I create the state in the same file of the Switch composable, the switch toggles fast. But whenever I host the state in the viewmodel as you described here, looks like it has a minor delay when I click the Switch. Do you know anything that can affect that? By the way, awesome tutorial!

Hi Philipp, does this way of using state recomposes everything whenever you type a character on the textfields? Is there a more optimized way?

Very cool video Thank you Bro You are the best 👍👍👍🔥🔥🔥

Hi, can you tell me an exact case when should we use SharedFlow (I watched some previous videos and you use them only for 1 observer(UI)), you mentioned it must have multiple observers. I just want to have a more accurate overview because there is another video where you compare LiveData vs Flows but also falls into the 1 observer category. Thanks.

Hi @Phil, Any way can we improve recomposition, Here for any one of field value change all other fields also effecting .

Setting error messages in the use case is definitely not clean architecture, interactor response should only contains litterals like boolean error flags, the presenter is responsible for error strings, and it's not in application layer.

really really good video one gently critic the error message should disappear when the user is editing the input field. Thanks a lot for the video!! :))

We should step into DDD with a solid Use Case in MVVM, then convert to vertical slice architecture with a few independently buildable and testable modules...then we are styling Phil.

How do you handle a 'loading' state? When the submit button is pressed, I would like to show a spinner and disable all input fields

Philipp this is a very nice tutorial that... Thanks

Thanks Philipp

Hi Phillip, How could you handle multiple fields for example 5 swipeable pages with 10 fields on each page?

What is the way to make the error messages support translation? Context can not be passed in use cases since these are designed to be independent of the platform.

Hii phil, thanks for the tutorial iam facing the issue like after succesful validation it is showing toast message pls provide me the solution.thanks

Hey great Video, how can I reset the Flow so I can validate the next inputs after

Is it a good idea to expose mutable state from the ViewModel? Perhaps use "private set"?

unable to import mutableStateOf in my xml android project any alternative

Do you have this but without Jetpack?

Thank you for the great content 🌻 But if we need to access the string resources what the use case will looks like?

Great 👌

Your example shows that you are using strings in usecase. I think what you missed is that we need to map useCase to presenter object. Beacuse in standard compay project you would like to have strings in string resources.

Hi I hope you can Answer my question. I am following your steps but at the last part I get lost because I have an layout xml and I dont know how to connect it and use the validations. I hope you can help me thank you. New subscriber

Super cool 😎

I think it is supposed to be assertEquals(false, result.successful)? Since the second param is `actual`

Hi Phillip, which theme you are using for android studio

thanks

Bro can you teach about how to use socket io using mvvm clean architecture pattern as there was no videos about socket io. It may help ful for my career as I came to android development by seeing your videos and I am be an good android developer because of you bro. If you don't mind can you teach us about socket io?

I wish Jetpack Compose could have a Form widget just like Flutter which could remove the amount of boilerplate code to create such.

very nice!!!

22:00 What should I do if I have a large number of textfields? Should I repeat the proccess for each one still?

Could you guide full test course for android?

Hello! Why are you using JUnit4 over 5? Thanks for your videos!

Hey, I'm from Brazil and I love your videos, but I always miss something. unit test A suggestion, whenever possible add unit tests

Hi nice thks. Didn't understand your comment on "abstracting the test on valid Email to avoid using Patterns in the validation class". What do you mean by that ?

Why did you choose channel instead of LiveData? Great video, by the way!

You were right, I was doing it wrong lol

Great work! it is better to call it EmailValidator instead of ValidateEmail

ok bro

Thanks for a great video and great content, can you make a video on how to implement firebase auth and firebase with clean architecture and jetpack compose

Btw your instagram links are broken everywhere on youtube (video desc and on channel social media buttons)

where is the link from 11:52? also your insta link is dead 😸 luv ur videos btw!

⭐⭐⭐⭐⭐

Thanks but I’m never gonna use this 😂😂😂 it is actually way too overkill just to validate Authentication fields and if the forma is very big then the number of files gonna overkill just for a single form submission.

bloc architecture...

What a nasty manner of not putting a space between if and the parenthesis.

when programming , show me the best practices, u not doing that , don't like that attitude sheesh

channel shouldn't' be use here right ?? its bug prone.

on UseCase you could use "operator fun invoke()", than call on ViewModel like function: validateEmail(email)

I think this would be more readable way for MVVM when click button and Submit is success, then action. Instead handle the next action on top and hard to read. ex: Button(onClick = { viewModel.onEvent(Event.Submit) { gotoNextFragment() } }) but I don't know, I try it but not very clean in VM. WDYT? waiting for you video if you like this way. :D thank youu

Return me ❤️❤️❤️