has been in regards to security of data on the device * encryption, remote wipe, etc. * Not as much on entry into the device & Conversation has changed with TouchID
• Windows (resetting is too complex) • http://windows.microsoft.com/en-us/windows-8/picture-passwords • http://forums.sqlmag.com/forums/aft/98454 Android - lack of flexibility in gesture. strict pattern Windows - you still have to have alphanumeric password. Theirs is just an option
utilizing multi- touch • Provide a self contained way of resetting password without external system or libraries * Why I choose to create a software solution * Felt others did it wrong & I love a challenge * Even if Apple did release their it would be system wide and private framework (Siri)
Cards • Apple already includes API’s for: • Facial recognition • Smiling • Blinking Times are changing and how we approach security on devices What’s next?
language as a communication tool it beholds such beauty and elegance. It is the calligraphy of gesture communication. The potential for this, as an example, is develop a new gesture “language”. Much like we have spoken and computer languages, but with consistency. The power of this would be unlimited and easy to use and interpret. With the current usage of multi-gesture it is always a singular expression, but when examining sign language a single gesture has to the ability to express an emotion or entire concept. It is multi-dimensional. Unlike, the computational and processing dependencies listed above that come with using voice interaction, all legacy and future multi-touch hardware have the ability to implement a new era of gestures. * http://blog.corywiles.com/the-sign-language-of-the-times * Evolution of gestures * Sign language will be inspiration * I give you * http://www.cmu.edu/homepage/computing/2012/spring/touche.shtml
“xpc exploit” • Static lib or framework • Persistent to any backing store (Memory, CoreData, NSUserDefaults, sqlite or file system, keychain or iCloud)* • Reminder images are saved even if you delete them from device In progress of implementing* ! *just objects. that is why you can
UIGestureRecognzier • Standard objects • would love to access to write to CPU like TouchID • Wasn’t concerned about actual point accuracy. • Import note about UIGestureRecognizers. • By default once the gesture is recognized touches* methods are cancelled. Result is that you can’t add “extra” processing in the standard method. • normally this isn’t a problem b/c all you care about it knowing what “type” of gesture occurred, but I need to “draw” the gesture on the screen. • cancelsTouchesInView = NO; * Need to add in feature that allows to register “storage class”. By default would use NSUserDefaults. * too hard to have accurate variance for point, plus finger sizes are different. you could tell someone your password and it would fail