{"title":"Delight Your Users By Pre-filling Forms With JBDeviceOwner","html_url":"https://deallocatedobjects.com/posts/delight-your-users-by-pre-filling-forms-with-jbdeviceowner","source_url":"https://github.com/jakeboxer/JBDeviceOwner","markdown_content":"Filling out forms on a phone can really suck. Heck, even on the iPad's awesome screen, I often make plenty of mistakes while typing in information. \r\n\r\nWhen a user first downloads your iOS app, it's quite common for them to need to fill out some sort of \"sign up\" or some other kind of form.\r\n\r\nAll of this can add up to a terrible \"first run\" experience for new users of your app.\r\n\r\nWhat's a developer to do? \r\n\r\nEnter: `JBDeviceOwner`\r\n\r\nThis simple library, which comes to us from [Jake Boxer](http://jakeboxer.com/), uses the *name* of the user's device to look up and return commonly needed user information from their Address Book record.\r\n\r\nHere's what it looks like in action:\r\n\r\n``` objc\r\nJBDeviceOwner *owner = [UIDevice currentDevice].owner;\r\n\r\n// owner will be nil if the user's data could not be found.\r\nif (owner != nil) {\r\n self.firstNameTextField.text = owner.firstName;\r\n self.lastNameTextField.text = owner.lastName;\r\n self.emailTextField.text = owner.email;\r\n self.phoneTextField.text = owner.phone;\r\n}\r\n```\r\n\r\nJake describes how it works:\r\n\r\n> It's really simple actually.\r\n\r\n> 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.\r\n\r\n> `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.\r\n\r\n> 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.\r\n\r\nObviously this approach, while really neat, isn't going to work for absolutely every user, so you should have a sensible \"fall back\". I like to \"try grabbing\" using `JBDeviceOwner`, and if I don't find anything, try manually asking the user to enter their email, then using *that email address* to try to locate their contact record.\r\n\r\nTry not to over-do it, but I believe when done well, this sort of approach can be an awesome alternative to requiring users to type in a ton of information.\r\n\r\n*Please Note:* Try not to ask your users for a ton of information in the first place, only require what you absolutely need to make your app work.\r\n\r\nThat being said, A few big name apps are now using this technique, and their \"first run\" experiences are *much* nicer, simply prompting the user with a `UIActionSheet` with, for example: \"Would you like to use this information?\"\r\n\r\n[Check out `JBDeviceOwner` on Github](https://github.com/jakeboxer/JBDeviceOwner) and stop annoying your users today!","html_content":"

Filling out forms on a phone can really suck. Heck, even on the iPad’s awesome screen, I often make plenty of mistakes while typing in information.

\n\n

When a user first downloads your iOS app, it’s quite common for them to need to fill out some sort of “sign up” or some other kind of form.

\n\n

All of this can add up to a terrible “first run” experience for new users of your app.

\n\n

What’s a developer to do?

\n\n

Enter: JBDeviceOwner

\n\n

This simple library, which comes to us from Jake Boxer, uses the name of the user’s device to look up and return commonly needed user information from their Address Book record.

\n\n

Here’s what it looks like in action:

\n
Objective-C
JBDeviceOwner *owner = [UIDevice currentDevice].owner;\n\n// owner will be nil if the user's data could not be found.\nif (owner != nil) {\n  self.firstNameTextField.text = owner.firstName;\n  self.lastNameTextField.text  = owner.lastName;\n  self.emailTextField.text     = owner.email;\n  self.phoneTextField.text     = owner.phone;\n}
\n

Jake describes how it works:

\n\n
\n

It’s really simple actually.

\n\n

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.

\n\n

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.

\n\n

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.

\n
\n\n

Obviously this approach, while really neat, isn’t going to work for absolutely every user, so you should have a sensible “fall back”. I like to “try grabbing” using JBDeviceOwner, and if I don’t find anything, try manually asking the user to enter their email, then using that email address to try to locate their contact record.

\n\n

Try not to over-do it, but I believe when done well, this sort of approach can be an awesome alternative to requiring users to type in a ton of information.

\n\n

Please Note: Try not to ask your users for a ton of information in the first place, only require what you absolutely need to make your app work.

\n\n

That being said, A few big name apps are now using this technique, and their “first run” experiences are much nicer, simply prompting the user with a UIActionSheet with, for example: “Would you like to use this information?”

\n\n

Check out JBDeviceOwner on Github and stop annoying your users today!

","created_at":"2013-11-16T05:10:25.564Z","updated_at":"2013-11-16T05:10:25.564Z"}