qtguru:


See to get the best performance just use a test phone so you can spare your computer ram.

Iambro:
Are you leaning from Android documentation?

tmanis:
ViewModel and LiveData
Ahmean, i get the general gist, but not the full intricacies

God-u abeg ooo
who go epp ooo

qtguru:


Pls I am curious by what you mean here

tmanis:


I dont Know if youre familiar with android app lifecycle from onCreate() to ondestroy(). So what I mean is that sometimes when the system calls onPause() function on your app while it is running _{(by maybe rotating the screen, or call comes in, or you navigate to the homepage)} , by the time it calls onResume() if the user is working with som data that has not been sent to storage, that data will be lost. The broad gist now is that ViewModel helps you to store that data, so its not lost, and LiveData helps you to keep updating the UI, such as changing the values of a TextView in real time from the LiveData without needing to manually write code to do that outside of the ViewModel class

I dont know if i explained it well, but thats how i understand it

islamics:
@ tmanis, you did well with the explanation to our Oga.

@ Telegon, savedInstance is still there but the modern way of designing android app prefer you to use ViewModel/LiveData and it is use in the MVVM pattern of design.

Telegon:


And op should keep up the good work of updating the thread, also with his sources of learning

tmanis:


I dont Know if youre familiar with android app lifecycle from onCreate() to ondestroy(). So what I mean is that sometimes when the system calls onPause() function on your app while it is running _{(by maybe rotating the screen, or call comes in, or you navigate to the homepage)} , by the time it calls onResume() if the user is working with som data that has not been sent to storage, that data will be lost. The broad gist now is that ViewModel helps you to store that data, so its not lost, and LiveData helps you to keep updating the UI, such as changing the values of a TextView in real time from the LiveData without needing to manually write code to do that outside of the ViewModel class

I dont know if i explained it well, but thats how i understand it

tmanis:


I dont Know if youre familiar with android app lifecycle from onCreate() to ondestroy(). So what I mean is that sometimes when the system calls onPause() function on your app while it is running _{(by maybe rotating the screen, or call comes in, or you navigate to the homepage)} , by the time it calls onResume() if the user is working with som data that has not been sent to storage, that data will be lost. The broad gist now is that ViewModel helps you to store that data, so its not lost, and LiveData helps you to keep updating the UI, such as changing the values of a TextView in real time from the LiveData without needing to manually write code to do that outside of the ViewModel class

I dont know if i explained it well, but thats how i understand it

qtguru:
An ex colleague is looking for Native Android Kotlin for POS, it's Interswitch reach out to me if interested.

tmanis:
The last UI layout i created.. will work on further refinements as time goes on

qtguru:
Someone should open a Flutter update thread for us

DrLevi:

Make the usual suspects con derail am?

qtguru:
Someone should open a Flutter update thread for us

Runningwater:


I'm curious do you plan on working for Google or it's branches? Cause employers of labour would mostly prefer java except you got convincing words to tell employers why to choose kotlin.

If I were you, I would go for java first then kotlin second.

teewhydope:


Lol stop trolling, except for companies that doesn't want to migrate their legacy codes to kotlin yet (mostly sdks), you have no reason developing new android apps with java. There's more to learn with kotlin... jetpack compose, kotlin multiplatform mobile etc.

qtguru:


Agreed too, because the new focus is on Kotlin, I still feel legacy codes are still in Android, but Kotlin has more advantage, is the build time really that slow compared to Java ?

teewhydope:

Yes for a clean build, but 15-20 seconds gain is not something you can live with. I use a 32gb ram mac so i hardly have to worry about compilation time except for very large projects which takes close to 10mins

qtguru:


Yeah thanks I have basic Java SE Knowledge and Thread, appreciate for the response and also damn 32GB RAM. M1 ?