On Thu, Jan 20, 2011 at 12:15 AM, B M <iamvirt...@gmail.com> wrote: > I am writing an application that will run on an Android device that > will be used by developmently challenged individuals. Some of the > clients function at a toddler level despite the fact they are adults. > For these clients, the application should remain running even when the > 'Home' or 'Back' button is pressed. Should the client break out of > the application, they would not understand how to get back into their > program. > > This application is the primary use for the device. There were > several inexpensive Android tablets shown at CES. The tablets are an > ideal device to run the application. The cost point of these devices > make them affordable by the families of these clients. The device > essentially becomes an embedded device until a special code/gesture/ > etc. is performed. The devices are purchased by people who *want* the > device to be normally running a single application. > > I have read about the controversy of applications like ToddlerLock > interfering with the expected UI Android provides. While I agree that > this is a really good thing in general, I believe there are times when > a 'kiosk' mode is desired. I see there are nasty hacks that subvert > the 'Home' button. > > Is there a proper way in Android that allows an application to > intercept/block the home button until a special code or gesture is > performed?
Make it the home screen app. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in London: http://bit.ly/smand1 and http://bit.ly/smand2 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
