The Top 5 Practices That Make My Android Architecture More Scalable 

1. Dependincy Injection 2. Testing 3. Modular Design 4. Avoiding In-Memory Global State 5. Packge Structure Consistency

That feeling when you said you should avoid global state and 10 seconds ago you showed that you had a private mutable var connectedNode that had a race with other coroutines.

Hi philip, could you show how to make one feature? it showed in 3D the real position of the phone in space, not only rotation, but in full from height to tilt, please, I am subscribed to you

Global state is dangerous, I had to rewrite my code to use local preference instead. Because process death caused app crash. I was tempted to use savedInstanceState to update global state, but I just decided in the end local preference aproach.

hi Philip, I recently saw a program like crypto steps there to sell sneakers and pay for steps there they asked me for money to start and I deleted it now I can’t find a similar application, could you show me how to make one feature from there? it showed in 3D the real position of the phone in space, not only rotation, but in full from height to tilt, please, I am subscribed to you

Amazing like always, ty ❤

One Question though about "Consistent Package Structure" -- As we have structured packages based on features, then my question is, if my "admin_override" feature has a couple of very small features that open up different screens as follows: 1. setting "printers" config through a screen, 2. showing "system_logs" through a screen, 3. "admin_override" screen itself for setting a couple of values/settings for the app to use; then inside "admin_override" package, should I create sub-packages called "system_logs" & "printers" which will further contain the usual "data", "domain", "presentation", "di" packages; as well as "data", "domain", "presentation", "di" packages in "admin_override" package as well ??? admin_override |__data |__domain |__presentation |__di |__system_logs |__data |__domain |__presentation |__di |__printers |__data |__domain |__presentation |__di 👆 For Consistency ??

Philip, very nice video. Quick question, does it make sense to have a folder/package with only one file inside? for example, the mappers folder has only one file "DeviceNodeMapper".

Just read job offers and learn that . Testing , solid principle , kotlin , jet pack compose and so on.

In case you need global state for contacts Would you use state flow like in your example, or save that into room/datastore?

Phillip, do you know Timo Boll?

Thanks!

What if the globol state should not persist only live until the app closes?

Hey philipp or anybody know. In Android essential bundle course. I need some clarification which is lifetime access and which is limited time access?

Guten tag

Ich bin ein Berliner

Third