When a requirement to be able to sms/text users in the address book of the user of an app is necessary there are different implementation methods that we see in various apps.
Here we consider how the user chooses the addresses to include in the sms/text message. We also consider the pros and cons of each option as well as look at a list of the most popular apps that have this ability and see which option they chose for their implementation.
I now realize that the only apps that implement an address book for sharing are those that need the contacts for other purposes.
In implementation A ayou allow the user to see a complete list of their contacts and select which ones they want to send a text to. Once the user has selected the list they proceed to the next step which shows them their text message to send.
- You can see all possible recipients
- Requires 2x the amount of steps to complete
- Scrolling entire list of contacts can cause user to put it off to another time
- Some users (wrongly) assume this means app is storing this information
In this implementation you skip right to showing the user the familiar sms/text message screen where they have to enter the names of those they want to share with. The text message can (and generally should) be seeded with some sort of message.
- Familiar (comfort) to normal texting interface
- 1 step process
- Easy to invite known groups (such as close friends)
- You may miss potential recipients.
I don't think there is a clear winner here. The pros and cons of each implementation option make them very even. It comes down to what you want.
The most interesting piece of information is that a couple users don't use implementation A because it looks like it is saving your contact information. Although this is not the case sometimes the perception of the user is all that matters.
Since there is no clear winner I think it's worth looking at other apps that have some form of sms/text sharing implemented and see what they do. The idea being that these big companies have done the research into this and have decided on the optimal implementation (of course this is based on a set of assumptions that may not apply to your app).
If you don't want to spend the time looking at each you'll find that most of the apps implement option B for whatever reason.
Side Note: It's amazing how many apps don't even implement this feature
Uber: Option B Implementation
Tinder: Option B Implementation
Whatsapp: Option A Implementation
Spotify: Option B Implementation
Waze: Option B Implementation (Approx.)
Evernote: Option B Implementation (Approx.)
Venmo: Option A Implementation
HotelsTonight: Option B Implementation
Shazam: Option B Implementation
NodeJS, iOS, Swift, MeteorJS, D3, 3D printing, salsa dancing, programming, and being critical of apps. Constantly learning by doing, developing apps on apps on apps.