Best practices for integrated (context-sensitive) help?

by Mark Murphy » Fri, 23 Apr 2010 05:14:03 GMT

Sponsored Links

This sounds lovely.

Or, just host the help online, linking to it via an ACTION_VIEW Intent
on your URL. I'm not sure if the HTML5 offline stuff works with the
Android browser, but if it does, use that to allow your help to be
usable even when there's no connection. IMHO, this will be the long-term
direction for this sort of thing, as it gives you easy publishing, easy
updates independent of the app itself, yet still isn't completely busted
when the user is offline.

Or, write your help in the form of an EPUB document and make it
available, so those with an EPUB reader (e.g., FBReaderJ) can use it.

Or, write your help in the form of a PDF document and make it available,
so those with a PDF viewer (e.g., Documents To Go) can use it. And see
if they have a referral program for sales, so you can make a bit of
money on people who buy that app to view your help.

Or, don't worry about on-device help due to form-factor issues and just
provide support via your Web site.

Worst-case scenario: create a content provider to serve your help files.

Mark Murphy (a Commons Guy)  | 

Android Consulting: 


Other Threads

1. Reusing the +/- number spinner from TimePickerDialog?


See the word "internal" in there?  That means internal.  Do not touch.  Your
code will break in the future.  In fact some platform engineer just may go
rename that class for no reason at all and break your code.

2009/2/4 solomonk <>

Dianne Hackborn
Android framework engineer

Note: please don't send private questions to me, as I don't have time to
provide private support.  All such questions should be posted on public
forums, where I and others can see and answer them.


2. native C++ SIP stack on Android

Can i port SIP stack written in C++ to android and let it running as
service in kernel ?
and the GUI will communicate with SIP stack through JNI ?

3. App source from Git not compatible with current SDK?

4. Build errors in git

5. Please Help! Service seems to sleep when phone is inactive

6. WebView responding to touch events

7. XML parsing problem (stops at non-utf characters)