How can beginners correctly understand Google's official suggested architectural principles (questions?)

Preface

Recently, I took the time to read google Of Jetpack Architecture components ,kotlin coroutines 、flow. And then google Official recommended application architecture guidelines ,compose etc. . These are The current mainstream application development technology stack . Our project has been set up , But my understanding is very shallow , The architecture recommended on the official website is not used in writing MVP Write straight . But these are the technology stacks that should be mastered in the future , Record the doubts .

1. Standard data-driven code styles , And the responsibilities of all levels , How the layers are related .

UI layer

Activity、Fragment Whether only ui Related codes ： ui Related codes refer to those codes ？

Whether the element is displayed or hidden , Add and remove . Font color value , The picture style , font size , Are you refreshing these only with View Elements that are related to their own attributes .

viewModel What code to put ？ What's the effect .

For example , In the login interface [ Conditional check logic ],EditerText Of textChange Logic , Check whether the password conforms to such judgment logic, and put it in ？viewModel You need to expose methods to the interface , Whether these methods need suspend modification .

Domain layer （xxxUserCase）

What type of code is put into the domain layer , If you need suspend modification . What style code is exposed . The domain layer can create object class Singleton class

xxxxResp The repository

Repository split , How to understand repository splitting , How to split is correct or relatively correct .

xxDataSource data source

Data sources in applications only , file , database , Memory , The Internet . If you define these earlier , That is, four data sources . Whether it should be defined in this way

NetDataSource ,DbDataSource ,FileDataSource DataStoreDataSource , So a large project only defines these four data elements , It must not be enough , How to subdivide

In general .

Tool library ,widget Custom layout , Elements , General network request logic , Remove it there ？

There is also the use of synergy , It's also a little knowledge . Nested usage of coroutines , How to control the timing between the network request initiated by the cooperation process and the ordinary network request , Then execute first and then execute another . Parallel execution , Nesting

Write the nested code of the cooperation process according to the gourd drawing , It's hard to write by yourself , The more I write, the less I know . Mainly, the nesting of network request code does not look elegant or beautiful .

How to understand business logic

Functional logic ： Explain the logic of this function in detail .
Interactive logic ： Explain the mutual jump between pages .
Visual Logic ： Right color , Requirements for icons .
Business logic ： Talk about the business corresponding to this function .

The business logic is split into functions that implement specific functions , Different functions deal with different problems （ Input data format verification , Format checking ）

1. What is business logic