Everyone loves being invited to a friend’s birthday party on Facebook. Recently, I was invited to my friend Jane’s birthday party. Here’s what the email looked like in my inbox:
What was really effective at getting me engaged was that my friend’s name Jane Smith was in the from field of the email. This way, it appeared that she, personally, had sent me the email.
Shortly thereafter, I saw another email arrive in my inbox. My friend had updated the original invitation:
Now, instead of being from my friend, the email was from Facebook. So when I first glanced at the email in my inbox, I had less urgency to see what it was about because it didn’t appear to be arriving directly from my friend. My guess is that Facebook has AB tested the original event creation email subject and found that replacing Facebook with the event creator’s name in the From field leads to greater engagement. As a next step, they can either AB test the same change for the event update email or simply implement the change.
Noticed something strange when someone confirmed my Facebook friend request. In the email that Facebook sent notifying me of the friend confirmation, Facebook suggests some people who are connected to this new friend who I may also be friends with.
This feature is useful and definitely makes sense given the context. However, when I click on the link of each user’s name, I am surprisingly not taken to that user’s profile page. However, I’m taken to a more generic page that has three modules: (1) open friend requests, (2) people I may know, and (3) a Search for Friends module.
This is really strange and an unexpected user experience. Ideally, I’d be taken to the user’s profile which I clicked on — and there I can decide if I know that person and follow up with a friend request.
Noticed a bug while looking through my friend Joseph’s list of friends on Facebook.
Here’s what I’m shown first when I go to browse his friends. As expected, I see his list of friends sorted alphabetically and I’m shown the friends at the top of that list.
After scrolling through the list, I encounter one of my other good friends Tom:
…and I click through to view his timeline:
When I’m done viewing his timeline, I touched the “friends of Joseph” menu item in the top left section of the page. As a user, my expectation was to be taken back to Joseph’s friend list at the exat spot where I originally selected – namely the T’s where Tom’s name exist. However, I am taken back to the top of the list:
Seems like everywhere you look these days, users are given an opportunity to share something via Facebook, Twitter, Google+, LinkedIn, Digg, StumbleUpon, and the list goes on an on. While it may be a bit overboard to offer sharing via so many different channels, offering sharing across Facebook and Twitter can be quite beneficial to a product.
One area where sharing would be a logical fit would be across content sites such as espn.com. On their mobile site, they have a video module that typically had 3 videos that can be selected to be viewed.
After clicking through, you are usually shown an ad and then the video.
When the video concludes, you are taken to a video center page that shows you what video you just watched and asks you if you want to watch any more videos.
At this point, this would be a GREAT opportunity for ESPN to offer the user the ability to share the video via Facebook or Twitter. This is no different than ESPN asking users to share articles via social channels. Except such a medium (video) may even have a more effective conversion rate of bringing new users back to the site.
Recently, I noticed an interesting text message alert from Facebook. The primary purpose of the text was to inform me that I had a pending friend request. In addition, the text issued a warning that since I hadn’t responded via text to Facebook recently, then I will stop getting text alerts.
Fair enough. It’s a reasonable explanation to turn off text alerts if the user is not interacting with the feature. But what was interesting for me was just how long would Facebook be willing to keep sending such text warnings before pulling the plug.
A couple of weeks came and went with no text alerts from Facebook. Amazingly, 25 days after the text above, I received another text from Facebook! This time, the warning was that since it had been 111 days since receiving my last text, Facebook may stop sending me text alerts.
So to make a long story short, Facebook is willing to wait at least 111 days before ceasing text messages. I find this to be an extremely long time. Especially since Facebook already gave me a warning at the 86 day point. Ideally, the algorithm that determines how long to continue sending texts to the user should not only be based on how many days it has been since last interaction, but also how many warnings the user decided to ignore.
Noticed a strange bug when searching for a business page on the Facebook iPhone App. Even thought I had previously liked the business, the search results still displayed a hollowed out thumbs-up icon that indicates I have not yet liked the business. Here’s how to reproduce the bug.
1. Start with a Facebook Page you’ve already visited and liked. Search for this Page in the iPhone app:
2. Just in case you haven’t liked it yet, double check, and press down on the empty thumbs-up icon to like the page again:
3. Visit the page and confirm that you have liked the page:
4. Touch the top level menu to search again. Here you will see your previous search query correctly displayed in the liked state:
5. Then, clear out the search box:
6. Finally, search for the same page again. Now, you will see the page displayed again, but it is displayed incorrectly as if it is not in the liked state.
Noticed a recent change in the latest FB iPhone App which was presumably done for the purpose of increasing user engagement with stories in the news feed. Before the change, here is how a sample story would look like:
As shown above, the Like, Comment, and Share calls to action are displayed as simple word links. In addition, the number of likes and comments for the story are shown in a similar treatment with the same amount of prominence and with the same color.
With the most recent iOS FB app update, here is how this component looks like:
So what changed?
– The biggest change is the change of word links as the primary CTAs (call to action) to using buttons with icons as the primary CTAs. This is a very huge and radical change. One well-accepted best-practise of conversion for site/app flows is the usage of buttons instead of text links and another best-practise is the usage of icons instead of just words. Here, Facebook is adding two very important components: both the conversion of the word to a button, and the addition of the corresponding CTA icon.
– In terms of overall screen real estate, the primary CTAs are taking up more space. Also, the component that conveys the amount of likes and comments has increased in size. Instead of showing the amount of likes and comments next to their corresponding icons, they are now shown next to the words Likes and Comments.
Is this a good idea? Will this feature succeed?
On the surface level, this is certainly not one of those cases where one design is obviously better than the other. Rather, FB will just simply A/B test this feature and see which design yields a higher level of engagement. What’s interesting about this before and after is that the before had a more prominent display of how previous users had engaged with this story (i.e. the amount of likes and comments) and thus this would increase the probability of the current user wanting to get involved and like or comment. And in contrast, the new design is leaning more toward making the primary CTAs more prominent and more appealing-to-be-clicked instead of relying on the social pressure of the statistics of the story.