OK, fair enough, it was only a suggestion. I just though it was useful to point out.
Sure, I get that; I was just offering my thoughts on it
I guess it depends on the situation. I've worked on some kiosk-type apps for the heritage sector and it seemed to work well enough.
I see where you're coming from but I suppose it just depends on the circumstances - if you want something that's absolutely tried and tested then you may just need to forego some of the latest tech until the security has been proven.
Of course, everything is circumstantial. I always assume security is needed in a discussion rather than to assume it isn't; at least if you highlight the potential issue, the person on the other end can make an informed decision as to whether it's important to them.
We've only used one app at a time (on a kiosk) so this hasn't really been much of an issue for us.
I'm not sure how that relates to the issue. It doesn't matter if you are only using one app at a time on the kiosk.
I'll preface this by saying, I haven't looked at every facet of iOS 6 in detail yet and have only really glanced at guided access, so I may be missing something here.
But as far as I am aware, you have to tap the home button three times and then tap "begin" to start guided access; and there is no persistent on-screen notification to tell you that it's active.
So assuming I've not overlooked anything, my point was something akin to this:
You have a kiosk in the reception, it's Jane the receptionists task to start the kiosk every morning.
She turns the iPad on, opens the kiosk app and then locks it down by pressing the home button three times and tapping begin (maybe setting screen areas too).
That last step, will be forgotten or maybe considered unimportant by the receptionist, thus ignored. She will start the app and then wander off to do the billion other things she has to do this morning.
As not to upset any receptionists called Jane, replace reception area, receptionist and Jane with whatever location and employee you like; the scenario will always be the same. Nothing against receptionists who's name happens to be Jane.
That was where the problem lies; human error, complacency or forgetfulness.
If it's not important whether users can get to the dashboard and play with the device normally, then of course it doesn't matter. However if it does matter and you do not want them to be able to exit out of the app, then it is a problem.
So the issue is simply that the lockdown has to be administered when the app has been opened. It's a bit like having a firewall that has to be turned on manually after you have started the computer, limited usefulness in the real world as the employee will forget because to be frank, they have far more important things to do. Or as can be the case, the employee see's that task as trivial or "stupid"; so just doesn't bother.
Was your main point that iPads aren't waterproof/durable? On their own, yes, but there iPad kiosk options on the market; admittedly, they can often be pretty expensive and a little over-engineered though.
My main point was that I don't see an iPad as a cost effective way to deliver a kiosk; you can get the same end result with spending less money (both upfront and long term).
The iPad isn't as durable as a kiosk which is built for purpose, a decent iPad app will be more expensive to develop than a kiosk app (in say Flash)... well that's not entirely true as you can create native iPad apps using Adobe AIR; but you get the point.
I've seen a few tablet kiosk stands and I don't think they are all that, not without spending some money; and at that point you are really looking at being trendy rather than just providing utility.
Of course, for some, being trendy is important and if that's the case, then fine; but if it's not and utility and cost is what's important, then use a kiosk.
