Apps created with AppSheet is every easy to use and understand. Still, some appโs features require more explanation, shown on the โHelp pageโ. How did you do it?
Regards,
I often use a column I call โexplanationโ and put the addition information (sometimes several paragraphs worth) in there. You could also and a link to another view in the app with more information or a link to web page.
Wow, that looks fantastic !
Does the โexplanationโ column belong to a new table dedicated for it?
No. In my app itโs just an ordinary column. The table from which this view is made doesnโt have many records so having a lot of text in one cell is not a big problem. Iโm not sure if it would work in exactly the same way for you if your circumstances are different.
Thanks.
Good luck!
P.S. Sorry. I just got confused and posted something that made no sense so I deleted it.
I need to have an appโs help with separated subjects. I created a table,
help(item, subject, help_detail, photo)
, and then created a view for this table. It seems okay for me. However, I need to see other ideas like yours.
Nice, neat construction of the page @Kirk_Masden
@Swoopy, I believe you may also wish to take a look at the onboarding views, just in case you have not yet taken a look at them. They could become a part of overall โhelpโ information approach for your app.
Oh, how could I overlook this view !
I may use it in future.
Sometimes Iโll make use of an action, setting it to be inline with a column, that looks like a question mark; when people tap it, itโs just an alert action with some text in it.
You can easily create alert actions like this, where you donโt need anything to happen but show a little text, by using the Group action; if you donโt put any actions in the stack, but set the confirmation to happen, you get an action that creates a pop up.
Now if you REALLY wanna get crazy , you can create an actual in-app help system - with a table for users to submit a help request, and a followup table for the answers.
You can go EVEN further and take this help system and integrate actions (like I was describing above) onto the fields that people were asking about with deeplinks taking you to the specific help request and followup.
The final way Iโve done this is to create similar fields like what Kirk is doing:
But Iโll include a UserSetting to turn these on/off. For people like me, the dev of the system, or other power users, we can skip those - they just get in the way.
Thatโs a great trick !
I may have to use this trick in future. Thank you.
Hereโs another example of how I add explanations to pages in my app. Itโs part of a โfeature requestโ for a hide / show toggle. We donโt have that yet, but, for now, this is another example of my approach. If you think it would be nice to have a hide / show toggle, please vote for it.
โTap & Holdโ to show Tooltip message, like AppSheet already has in โChart viewโ, is good enough if available for columnโs name shown in detail views.
User | Count |
---|---|
41 | |
31 | |
29 | |
16 | |
14 |