Stable UI state / separation of database -> UI layer

[jsoberg]

Hey all!

I've begun using Meshtastic recently and am enjoying using it. I'm a full-time Android engineer with experience in P2P networking, and would love to contribute to the project in some regular capacity.

As a first point of discussion, I'd like to talk about introducing separating the layers of the app a bit. Currently, it appears that we use our data-level models as UI state. When using Compose, this introduces a few issues to stability; This is a more in-depth overview, but a TLDR is that it's important to create a stable/immutable UI state for efficiency/recomposition's sake. It's also generally a good idea to have layer separation of data/domain/UI, working toward the principles of a clean architecture.

I put up a PR that introduces this concept a bit here: meshtastic/Meshtastic-Android#1575. Let me know if you're interested in this type of contribution and others - I'd love to discuss further!

[jamesarich]

Hi glad to have you! 👋
Feel free to join us on the meshtastic discord as well. The #android channel (and other dev channels) are a pretty good way to stay in the loop on the overall project.

Cheers

[jsoberg]

Thanks James! I'll jump in, I'm MyHeartPills on Discord