u/jaroos_

A screen can have ui updated from both network/backround tasks as well as non network operations. E.g. in the orders screen of food ordering app there can be tabs for status wise list e.g New, Accepted, Ready, Out for Delivery, Delivered, Cancelled. When we select a tab we have to update the variable which holds the active tab status name or index which is local ui update, when a tab is selected or by default we call api to list orders which is network operation. State hoisting & data class which holds ui state & values in view model is recommended pattern right? My question will there be a small delay when updating local UI updates through state flow which makes app feel slow (docs suggest not to use flow for things like input field)? If we use mutabletstateof for local ui states in main composable & pass in child composable it will be too much variables if there are more things like date filter, search etc). So what's the correct way? Or the performance difference is negligible?

I was using redmi note 9 pro as my main phone, my mother has Poco M6 Pro whose display broke once after dropping, as she upgraded to another phone I am now using poco M6 pro as my main phone after replacing display which is not original (using Redmi as secondary) but typing in Gboard feels slower compared to my Redmi, but only typing not the whole touch response

In Amazon it is showing not deliverable to Nagercoil

In XML views, we can easily get an idea of how ui looks, we just need to set the values, style, spacing etc in appropriate ui elements even for recycler view we can do with listitem & itemcount & layout preview easily updates, but in compose for each composable function we have to manually write a preview function wrap the composable in the theme & create the dummy data manually. And when we change the values the preview sometimes disappears & refresh this make me difficult to quickly compare how it looked previously. How do you manage this.

The biggest limitation is app won't connect to internet if it is background. The problem here is for real time apps like chat app can't receive message to update the UI or insert to database as the socket gets closed when app goes to background even if it is not killed.