NodeInfo Cards

[jamesarich]

There's been some chatter about the NodeInfo cards containing a lot of lines of information, reducing it's at-a-glance readability.
A couple of suggestions have been mentioned:

• Details screen: tapping a minimal NodeInfo card would take you to a details fragment to display more of that node's details.
• Expandable NodeInfo cards: tapping a minimal NodeInfo card would expand the card to display more of that node's details.
• Reorganizing the current card layout to display the information in less cluttered fashion.

What info is primary and secondary when it comes to viewing at-a-glance NodeInfo? What details could be hidden "below the fold" for an expandable card or details view?

For reference - NodeInfo model containing the information available that could be displayed.
https://github.com/meshtastic/Meshtastic-Android/blob/master/app/src/main/java/com/geeksville/mesh/NodeInfo.kt

[garthvh]

There is quite a bit of available info a node can have

Node List

Favorite
Short name
Long Name
Last Heard
Role
Distance
Hops Away
Is Mqtt
Is Store and Forward Router
Battery Details
Has Device metrics
Has Positions
Has Detection Sensor
Has Environment metrics
Has Trace Routes

Node Details

Short Name
Hardware Image and name
Signal Strength Meter
Battery Level Gauge

Node Number
UserId
Role
First Heard
Last Heard

Device Metrics Log
Node Map
Position Log
Environment metrics log
Trace Route Log
Detection Sensor Log

Actions :

Favorite
Hide Alerts
Exchange Positions
Trace Route
Delete

[jamesarich]

Nice - thanks @garthvh. I see a lot of iconography used in the Apple app list items. Is that standardized/documented for meshtastic somewhere? Also, do you know where the hardware images came from?

[garthvh]

Apple offers SFSymbols, I think there is an icon library being used on android. There is descriptive text next to every icon in the apple apps. I have collected the hardware images over time.

[rcarteraz]

There's been some chatter about the NodeInfo cards containing a lot of lines of information, reducing it's at-a-glance readability. A couple of suggestions have been mentioned:

• Details screen: tapping a minimal NodeInfo card would take you to a details fragment to display more of that node's details.
• Expandable NodeInfo cards: tapping a minimal NodeInfo card would expand the card to display more of that node's details.
• Reorganizing the current card layout to display the information in less cluttered fashion.

What info is primary and secondary when it comes to viewing at-a-glance NodeInfo? What details could be hidden "below the fold" for an expandable card or details view?

The card has definitely become way too busy and folks want to keep adding to it. I would definitely prefer to see a dedicated node details view and keep the card with limited information. Similar to how iOS handles it.

[jamesarich]

Yep, that's what this discussion is for - do you have an opinion on which primary vs secondary information to be shown on the list card vs detail/expanded views?

[garthvh]

It would also be great if we could make showing coordinates in the list for each node optional, we have had YouTube creators dox themselves on livestreams with screenshots.

[b8b8]

Can this be locked with expanded view visible? some of want to see all the data by just scrolling vertically instead of having to click each node.

[jamesarich]

Took a stab at expandable nodeinfo cards yesterday #1144 lmk what y'all think.

[Talie5in]

Loving the progress on this, and love the change, but I'd love there to be a "minimal" view as well, just shortname, long name and last seen/battery.. means it can be a tighter box, and list more nodes on the one screen (less scrolling)

Even the distance and hops, just seems busy/makes the box to large when using it just for messaging and seeing nodes, and when you want to delve deeper then you open up that information.

I think the standard view should remain as default, and option to toggle between minimal and expanded.

[SenorFusion]

@jamesarich - Thank you for taking the lead on this! It looks fantastic.

I know its a constant battle of "how much is too much" info to show, but I'll humbly request: What do you think about including Device Role in the expanded view?

I often would like to know if a device is a user or a router (or see if they are still running the deprecated Router_Client)

It really helps to get feel for which nodes in your area are People vs Infrastructure.

Thanks!

[jamesarich]

I'm not opposed to it if it's easily available in the node data. I can take a peek.

[jamesarich]

#1174

[SenorFusion]

Awesome, thank you!

[battlehax]

Looking great! I wish I could contribute some code, but I can contribute my suggestions at least... There's a lot of blank space on unexpanded cards and I wonder if they could be squished down to see more nodes on screen at once. Also, I see some nodes that show info like 'ch:3 Hops Away: 4' that I know are on other channels. It'd be neat if the expanded info could show a list of shared channels, maybe something like [ch:0,1,3]
Anyway, love the direction things are going, keep up the awesome work!

[jamesarich]

I think we're happy w/ the current state as of 2.6.3, and will continue to iterate from there.