Zoom is #1 in customer satisfaction and the best unified communication experience on mobile.
I guess this is kind of like a message thread, but encapsulating more data than just text.Stay connected wherever you go – start or join a secure meeting with flawless video and audio, instant screen sharing, and cross-platform instant messaging - for free! So basically it goes both ways - server can send to the local DB the users with updated info, and users can input data waiting for the network to sync everything. I am wanting this layer to basically go both ways - a user can input data to be sent to the 'user shared' space, and this is stored in the local DB - once a network update occurs (either through a routine async that goes off whenever an update is made OR when network stability is reached). All of this is done through sending JSON thru retrofit. I plan to basically create a network- to- client data layer for my app, that basically sends view models what it needs and then then BOTH users are served the same data upon network update (async updates). Is it a good practice, to architecture your data from networks to go INTO a local db on the client side, and this local DB gives the UI layer what it needs to present to the user?
So then comes the bigger part I have somewhat of no idea about (I know what I don't know). Users share data when one user adds another, they both get served the same data once the handshake happens - I'm still working on the view models and UI business layer, but I'm doing it all through compose to prime myself for having experience of the library (I spent two months learning views in XML, was good but here we go learning something else!) I have a project envisioned to utilize dynamic data between users. Wasn't much compsci focused in college (chemistry rather), but I like pattering along learning all this. Just slowly spending a few hours a week getting the hang of programming my own apps :).
0 kommentar(er)
