शैडोइंग अभ्यास: Why 95% of Android Developers Get Use Cases Wrong - वीडियो के साथ अंग्रेजी बोलना सीखें

Hey guys and welcome back to a new video.

95% of Android developers use use cases wrong.

It's a catchy title, but I really mean that number.

I will tell you why.

Because use cases on Android and in software development in general are so often misunderstood.

I also myself misunderstood them when initially getting into these.

I'm pretty sure you can still find some super old videos on my channel where I'm also making the mistake

that I talk about in this video.

If your use case looks like this to get some user information, then you are doing it wrong.

Why is that?

In order to understand what use cases should contain and what kinds of use cases you should create, if you decide to stick to use cases,

we need to understand what a use case is originally meant to be in the context of software engineering.

And if we actually just Google for that, use cases software development, and we just click on a random picture here, then we have, for example, a library information system.

And then we have some use cases.

This is what we call a use case diagram.

Maybe you remember that from university or so.

to browse books, checkout books, return books, update the catalog, clicking here, view items, make purchase, checkout, client register.

If we carefully think about these use cases here, how they are named, view items, browse books, checkout books, what do all these have in common?

They all have in common that the user is actively aware about these things happening

because it is a real use case of your app.

And if you have a use case, then you can use it as a user.

Now, when we talk about email validation, is that a use case?

Is this something where a user would go to your app and now say, ah, now I'm going to validate my email, or now I'm going to clear my session.

Or hey, now I will retrieve a user by its ID.

No, they actually have no idea that these things happen.

These are rather just side effects of a real use case.

The user definitely knows that they are currently registering an account.

And email validation is just a side effect, something that happens as part of registering an account, but it's not something that the user actively has in their mind when they go through registration.

So if we take a look at some real use cases, the way it's really intended here on the correct, then we, for example, have this register use case.

And you can see suddenly it starts to contain real logic.

It's not just a single line of code that calls a repository or some kind of validation class, but it's a real use case that combines multiple pieces of business logic into a use case,

into something the user can do with your app that they are aware about.

So this would be a good example for a use case because the user knows that they are registering an account.

Of course, what's part of the use case is actually validating the email.

It's validating the password.

It is actually making the call to our remote API, for example.

It is then handling the errors and actually forwarding these to whatever class calls this use case.

That is a good example of a use case.

Well, let's take a look at this logout use case a user certainly knows that they are logging out.

But what internally happens as part of logging out, like actually making the network call, clearing the session, clearing their shopping cart, that's something they don't know and they don't have to know.

So the use case actually just bundles these function calls and makes sure that they are executed in the right order.

So we have a reusable kind of package for logging out and we just need to invoke the logout use case.

So other parts of our app also don't need to know what internally happens when we log out.

And all these other classes that act as utility for our use cases, like validating an email, this is of course still business logic.

This still lives in your domain layer, but it's not a use case.

So you really just make this a plain class, call it whatever it's responsible for, email validator, password validator, and then suddenly use cases make a lot more sense.

As you know, I'm usually not for using use cases a lot

because you will still often have these pretty much empty use cases, even when doing it the correct way.

So for example, if you say you want to fetch your nodes, so you actually want to see the nodes as a list, and then there's usually just a call to a REST API.

So you just forward this to your repository.

There's no error handling or so.

Maybe the repository already handles that, but no real business logic error handling in the use case itself.

But there are certainly use cases that make a lot of sense.

Like here, bundling these different calls here into a logout use case makes a lot of sense

because you will never again have to memorize what logging out really does in your app.

Instead, you just call this use case.

You never have to memorize what registration actually means and does in your app, unless you're, of course, responsible for working on that part.

But you can really just invoke the use case

and you know the use case involves the business logic to take care of that.

And if you stick to use cases in your app and you actually stick to them like this the right way, then I don't have a big problem with that.

Still, I personally lean more towards not using them at all

and just also bundling such business logic either in the view model or the repository, at least for small to medium-sized projects.

But for larger projects, this can make a lot of sense and I would also really consider having use cases there.

Now, if you feel like, okay, there is still a lot to learn about Android architecture, about Kotlin multi-platform architecture, then I can help you with exactly that

because we have our senior app developer mentoring where you get to build a real production project over multiple months

and have all your code reviewed by your personal mentors, including me.

This way we can spot issues in your app's architecture.

You actually have no idea about that these even exist.

If you're making mistakes you don't know of, then you obviously can learn from these mistakes.

So this is really a fast lane program here for you to grow to a senior developer level.

Link is below.

You can apply to this program.

We can have a chat if this could be a fit.

You can't just buy it on that website like a course, but we really first of all have to talk if we can help, how we can help, how it makes sense for you in order to also craft an individual learning plan for you.

So take a look at that.

Thanks for watching and I will see you back in the next video.

Have an amazing rest of your week.

Bye bye.

📺 उसी चैनल से

Wild times we live in

Business EnglishUniversity StudentsWorking Adults

We will all be generalists.

Business EnglishUniversity StudentsWorking Adults

✨ अनुशंसित वीडियो

126 वाक्य

How I use AI as a senior software engineer and 5 principles of AI explained in 10 minutes

Business EnglishUniversity StudentsWorking Adults

119 वाक्य

New Skills! v1.1 brings /wayfinder, /research, /implement, /to-spec, /to-tickets

Business EnglishUniversity StudentsWorking Adults

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।

शैडोइंग तकनीक: पूरी चरण-दर-चरण गाइड पढ़ें →

शैडोइंग अभ्यास: Why 95% of Android Developers Get Use Cases Wrong - वीडियो के साथ अंग्रेजी बोलना सीखें

Wild times we live in

We will all be generalists.

How I use AI as a senior software engineer and 5 principles of AI explained in 10 minutes

How to Write Test Cases for Manual Testing?

The future unfolds! How to optimize Android apps for adaptive layouts

How I Made $30,000 Hacking Broken Access Control

My UX Design Case Study Presentation that Got Me Hired | Case Study Walkthrough

DRY Often Makes Your Code Worse

System Design Mock Interview: Design Facebook Messenger

Video

My 4.9-Star iOS App Is Actually a Website: Here’s How I Built It

Introduction To Marketing | Marketing 101

JTBD Framework in UX w/ Examples | UXtweak

New Skills! v1.1 brings /wayfinder, /research, /implement, /to-spec, /to-tickets

आप क्या सीखेंगे

इन ध्वनियों पर ध्यान दें

जैसे एक मूल निवासी कहें

शैडोइंग तकनीक क्या है?