Auto-fill iOS registration forms with the device owner's name, email, and other data
Typing names, email addresses, and other personal info is never fun. This is often your user's first experience with your app, and it sucks.
Fortunately, these data often already exist somewhere on your user's phone. JBDeviceOwner
presents them to iOS app developers with a simple interface.
JBDeviceOwner
can currently get you the following attributes of the device's owner:
More are coming.
JBDeviceOwner *owner = [UIDevice currentDevice].owner;
// owner will be nil if the user's data could not be found.
if (owner != nil) {
self.firstNameTextField.text = owner.firstName;
self.lastNameTextField.text = owner.lastName;
self.emailTextField.text = owner.email;
self.phoneTextField.text = owner.phone;
}
It's really simple actually.
Most iPhones are named "Jake Boxer's iPhone" (sometimes with a different person's name instead of mine). Most iPhones have their owner saved in their address book.
JBDeviceOwner
extracts the owner's name from the device name, finds the matching record in the address book, and populates the JBDeviceOwner
instance with the data from the record.
If JBDeviceOwner
can't figure out the owner's name, or if it can't find a matching record in the address book, it won't return anything.
JBDeviceOwner.framework
into your project.AddressBook.framework
to your project if it's not there already (it's an Apple framework).-ObjC
to your target's "Other Linker Flags".#import <JBDeviceOwner/JBDeviceOwner.h>
to any file where you want to use JBDeviceOwner
.This library was inspired by Square's iOS app, and by John Feminella's awesome Quora explanation of Square's magic. Fantastic idea, super clear breakdown.
Big thanks to Jeff Verkoeyen for his iOS-Framework guide. For some reason, creating static iOS frameworks is a giant hassle. Jeff made it super easy. Also, this might be the only Xcode tutorial I've ever followed where everything worked as expected.