Lately, I’ve been working with students who are learning to communicate using different Apps on iPads and while we’ve had some great successes, we’ve encountered one particular difficulty: the lure of the “Home” button! Too often, students press the “Home” button and close the App they were using and are unable to navigate back. An adult is then required to relaunch the App to return the student to the program. When iPads are used in an educational setting, it can be really time-consuming for the teacher to go around and make sure all the kids are using the right App (and not checking out their pictures in iPhoto or surfing the internet!)
Although there are several Apps available that claim to lock you out of specific Apps on your iPad through the use of a password, I’ve read lots of negative reviews provided by disgruntled customers who report that these Apps only request a password for a couple of Apps or don’t do what they claim at all. Another issue with password-protected Apps is that once a password is required (i.e. when the person using the iPad attempts to open another App), the person requires someone to type in the password and then relaunch the required App.
One option for preventing access to a number of tempting Apps on the iPad is to set some restrictions via the iPad’s “Settings” menu. Open “Settings”, select “General” and then go to “Restrictions”. From there you can restrict access to “Safari” (the Internet), YouTube and a number of other Apps. This only works for a few Apps though and doesn’t allow you to block access to all the Apps you have downloaded, like specific games.
The best option I’ve found is to physically prevent access to the “Home” button through the use of a product called the Bubcap. “Bubcaps” are little adhesive covers of varying levels of rigidity that stick over the “Home” button and make it difficult for children to press. Adults can still access the “Home” button with a firm press and retain a little more control over the use of the iPad. I like this idea because once a “Bubcap” has been attached, the person can then use the iPad independently.
In my last post I wrote about how it would be great if you could program recorded speech onto buttons in Proloquo2Go. Well…Happy New Year everyone because it’s going to happen! On the 31st of December, 2011, the Proloquo2GoFacebook page announced that “the ability to record and play back audio” will be added in 2012! It will be available as a free update and “will be added after [version] 2.0, probably in 2.1 or 2.2”. This will be a fantastic addition to the Proloquo2Go app!
I’ve previously outlined a few ideas for using audio in Proloquo2Go and I have some more to add to the list:
– recording cheers to use when watching sports
– singing a song (depending upon whether there is a time limit on the recording)
– people who are able to produce clear speech at the start of the day but fatigue as time passes might like to record their own voice into Proloquo2Go
I recently emailed AssistiveWare (the company that created Proloquo2Go) with some suggestions for inclusion in a future software update. Wouldn’t it be great if you could program recorded speech or a sound file onto buttons in Proloquo2Go? The possibilities would be endless! You could record or add:
– laughter (instead of relying on a vocabulary item that says” ha ha ha” – which can sound a little sarcastic!)
– drama lines (for all the performers out there)
– whistles (e.g. to get a friend’s attention)
– gasps (great to convey surprise in a conversation)
I’d love to read your suggestions too. Please feel free to leave a reply via the link below.
I’ve just been reading about the new update for Proloquo2Go, a great app that allows you to communicate using symbols and text via your iPhone, iPad touch or iPad. The app is relatively easy to use and can be customised to include all the vocabulary items you need for specific activities, which can be arranged within categories.
I’ve been doing lots of Proloquo2Go programming lately and am really happy that the bug that makes buttons move around within categories has been fixed!