Adding informative HELP pages (inside app)

[E3V3A]

I propose to add a few pages or one long page (?) of HELP information on the most important items and features. In particular:

• on all "Menu" items
• on all the DataBase (DB) tables + items
• on all the Settings items

The help-page should be categorized something like:

• Status Icons
• Menu / Shortcut (items)
• Database (tables and items)
• Open Cell ID API KEY addition
• AT Command Injector

The text should not be longer than 1-4 lines, and very easy to understand. If needed we can link to more detailed descriptions in a fully documented, and several pages long help section, at a later stage.

[SecUpwN]

@E3V3A, thanks for opening this Issue. I support your idea and would like to expand upon it: I am proposing that we add a question mark ("?") to each part of tour App. When pressed, this question mark opens up the corresponding section on the HELP-Page. To make it short and uncluttered:

1. One HELP Page, accessible via the menu on the left side, or via the "?" within each App item
2. When pressing "?", the App takes the user to the right part of the HELP-Page
3. Each section on the HELP-Page shall have the right link to the long explanation on our WIKI

Yeah, I know we're rough on your mad coding skillz, @xLaMbChOpSx. ^^

[E3V3A]

I usually prefer to have in "info" icon like "(i)"...instead of a "(?)"...

[SecUpwN]

Perfectionism at its best. I like that, @E3V3A. So let there be a an info icon! 😺

[E3V3A]

We can use ℹ️ (information_source).

[tobykurien]

Errgh, that icon looks like an iOS icon :-( I have another suggestion (sorry for adding noise). The idea is to basically use up unused space until there is data to show. From a UX point-of-view, this solves a few issues as well:

• "Tracking" should be a single drawer item that goes to a page with buttons for monitor and start/stop tracking. On that page, we can add information about what tracking and monitor does (and the difference). It is horrible UX when a click on a drawer item immediately starts an operation without opening up a new page.
• Device details and Cell information don't really need explanation, although that could be added to the top of those pages
• "AT command injector" should have a description, and that could be where the "Response" currently is. Once you execute a command, the output can replace the description.
• "Database viewer", as with above, show a description until "Load data" is clicked, then the results replace the description.
• "Map viewer" - I think here we will need an info item on the menu to explain what the pins are and what you can do here.

These are just suggestions, feel free to knock them down. They are suggestions I can help implement.

[SecUpwN]

@tobykurien, you are absolutely right. Feel free to make a mockup version to be shared for internal review. Since you're already itching to work on drawers, maybe you can also solve #116 in one run?

[E3V3A]

@tobykurien He he, yes, that was the GitHub emoji... I don't really like it either. I'd rater see a circle. As for all your other suggestions, they're excellent and I agree on all. Only comment is on the AT command interface, which is supposed to be hidden in a public beta.

We're testing it here to try to understand on what devices we can use the AT if. We will use that as a third option (as we discussed in chat) to obtain more relevant network parameters, like correct signal strength on dysfunctional API's (like those of Samsung) and to change certain type of network behaviors, like SMS handling, dropped calls, network lock-ins etc. We can also use it to change channels etc. So in the end it should be hidden from user and replaced by various settings and buttons...

[SecUpwN]

@E3V3A, we now have the requested [ i ] buttons in our Navigation Drawer.
Can this Issue be closed or is there anything else that we have to add as well?

[E3V3A]

Yeah, I think that pretty much covers it, if there's something else, we can re-open later.