On Thursday, August 22, 2013 8:02:19 PM UTC-7, TreKing wrote:
On Thu, Aug 22, 2013 at 5:26 PM, Nathan nathan@gmail.comjavascript:
wrote:
On Thursday, August 22, 2013 12:57:08 PM UTC-7, TreKing wrote:
Nothing fancy at all. It's there if the user wants it but does take
On Wed, Aug 21, 2013 at 6:09 PM, Nathan nathan.d.mel...@gmail.com wrote:
What have you done and how well has it worked?
I have a help section on my site, with subpages corresponding to each major
feature in the app. Each activity also has its own page. In the app, I have
a utility class that
On Thursday, August 22, 2013 12:57:08 PM UTC-7, TreKing wrote:
On Wed, Aug 21, 2013 at 6:09 PM, Nathan nathan@gmail.comjavascript:
wrote:
What have you done and how well has it worked?
I have a help section on my site, with subpages corresponding to each
major feature in the app.
I was going to say . .
By wanting to do some of this, I realize I am a bit at odds with the
Android Design Guideline.
Don't show unsolicited help, except in very limited casesMaybe I'm just
liberal with the definition of limited cases. But it is probably
consistent with Section 5.5 of Android
On Thu, Aug 22, 2013 at 5:26 PM, Nathan nathan.d.mel...@gmail.com wrote:
On Thursday, August 22, 2013 12:57:08 PM UTC-7, TreKing wrote:
On Wed, Aug 21, 2013 at 6:09 PM, Nathan nathan@gmail.com wrote:
What have you done and how well has it worked?
I have a help section on my site,
I've been thinking about ways to integrate help into an app.
I wanted to see what other people have done.
http://developer.android.com/design/patterns/help.html
Context sensitive, at a minimum, per screen, and possibly point to certain
buttons using a PopupWindow to point out something like
6 matches
Mail list logo
