A Consumer Journey: Samsung Gear Neo

by Eugenio Santiago

KLIcustomerJourney copy

The Apple Watch, released this past Spring, has caused companies to pay close attention to the quickly evolving wearable space. Consumers are looking to see if there is a tipping point for widespread adoption in the near future and they’re interested in staying ahead of it; preparing apps that are especially suited for Apple Store or Android Wear.

About a month ago I unpacked a lime green Apple Watch, paired it with my iPhone and wore it around town. In true researcher form, I found myself paying close attention to every new feature and announcing to my colleagues which features impressed me, and which failed me.

Last week I kicked-off a client project that required me to familiarize myself with the Samsung Gear Neo. I looked at my Apple Watch and silently said to myself: “It’s on.”

I should mention, I’m not an original member of the Apple Fanclub. I stuck to my Samsung Android mobile device for many years as the Apple products evolved. Eventually, I moved to Apple, mostly so that I could keep up on the current offering as much of my project work at KLI demands this. I looked at the Samsung Gear Neo with a wide open mind. I was excited to learn more.

The abridged version of my consumer journey is detailed here, including these typical phases of a consumer journey:
– Awareness
– Consideration
– Purchase
– Retention/Usage
– Advocacy

Awareness:
Last week I kicked-off a client project that required me to familiarize myself with the Samsung Gear Neo. I looked at my Apple Watch and silently said to myself: “It’s on.”

Consideration: Product Research & Purchase
+ 2 Feeling uplifted. The researcher / gadget geek in me likes that I have a fun new project to explore.
+ 1 I took a look on online, CNET.com, the Samsung website, confirmed that particular apps were available and I mapped out the nearest location where these are sold and I was on my way.

Purchase:
– 1 Travel to the store, beautiful outside but quite hot, I hopped on the subway, happy. I walked into the store and the AC wasn’t working, It was stuffy and uncomfortable, overall it sucked. Someone helped me out, got me what I wanted and I was done and on my way.

Back to the Office with a New Toy
+2 Excited to try it out! Excited to compare!

Retention/Usage:
– 1 I open it up and the instructions are clunky. I struggled with the Tizen OS, the pairing options were not straight forward. After re-reading the instructions I recognized that I needed a specific URL to download a companion for blue tooth communication. When I arrived at the Samsung App store, an unfamiliar place for me, I felt I had to fend for myself. No one was waiting to welcome me and show me around, per se.

+ 2 Navigation: Typically, on the mobile experience, you swipe from left to right to move ahead in a variety of different scenarios. On the Samsung Gear, this is consistent. It was intuitive and clear. Utilitarian and gave me confidence in navigating through. The Apple Watch, by comparison, demands that you click to return to the home screen and access app icons in a rhombus shaped cloud, they’re tiny, and I feel clumsy. I liked what I was seeing on the Neo.

Usage:
– 1 Utility: I first took a look at messaging as our first example. Apple executes this well. They have pre-canned text responses that seem to make sense and fit my standard vernacular. They were smart responses to the incoming message. Samsung had this too, but in my anecdotal experience the responses were basic and the associated logic to populate them felt more primitive. Further, I could only respond via precanned text.
– 1 A voice-to-text option was not readily available for me. I eventually found it, after going to my phone to set this up, check through T&C’s, and activating it for use on my watch.
+ 1 I was thankful for that. It was clunky, but it did the job.

-2 Then it got a bit weird. On my Apple Watch I was able to speak my text, review it, and push a button to send the message. On the Samsung I realized that once I was in a scenario where I was using voice-to-text, this was my only option. I’d speak my message, then the system would recognize that I would finish speaking my message and it would cycle through to a screen where I would be prompted to approve of the message. It verbally asks for my approval, and then responds and sends only when I verbally replied. I found it to be a bit uncomfortable that the watch was talking to me during instances when I didn’t expect that kind of two-way communication.

0 Other utility features, such as the acceptance of an incoming phone call, for example, seemed to be similar on each device.

+1 Wearing it for a longer period: Tethering to my phone: I will say that without running a full technical analysis, it seemed to me that the Samsung watch seemed to have better range, so that was a positive.

-1: However, the status notification that indicated that you were tethered or out of range was flawed. Samsung notified me that I was no longer connected, but after that point in time identified no icon or indicator that I was disconnected. If I missed the notification prompt I may not have known that I needed to reconnect or get closer until I actively attempted an activity. Apple has a standing icon.

-2: The Samsung Gear was released in spring 2014. Shortly after the Android Wear release was made for select hardware devices, not including the Neo, it continued to run on the Tizen OS. I think I need to return this product and opt for a choice that is more Google-Centric. I’d liked to have explored a more seamless experience, the “cue card”, full integration with my mail, and more.

Advocacy:
I’m writing this piece because I want to share my experience and improve the product. Ultimately it was a letdown, but I haven’t given up on wearables and I’m still excited to try an Android Wear device. Hopeful ending. Optimistic. Wasn’t the greatest, but there’s something more ahead.

Mobile Payment Compatibility at Festivals – Round 1

By: Kathleen Henning and Phil McGuinness

After a challenging experience with mobile payments at a New York music festival, our researchers decided to get together and assess two of the leading mobile payment options currently on the market.  In Part One of this two-part series, we field test PayPal and Google Wallet apps on both iPhone and Android smartphones. Next month, we’ll review the mobile payment landscape and share some interesting new developments.

Let’s see where Kathleen Henning and Phil McGuinness stand on these mobile giants.

Kathleen: As I was preparing to attend the Governor’s Ball festival this summer, I was super psyched. Not only did they have an amazing lineup, but the food & drink section asked for my credit card information so I could make mobile payments. Since I hate carrying cash (and really anything), this was a dream come true for me. Unfortunately, it was a little too good to be true. I entered all of my information only to find that no one was accepting the GovBall app as payment. Instead, there was the PayPal app…

Most festivals, for better or worse, are known for having notoriously awful cell service. GovBall was no exception. Using the PayPal app required downloading it, logging in, taking a picture of yourself, and saving your account information. All of those steps required far more Internet speed than was available. Day 1 I had no luck. Day 2 I was able to purchase free Brooklyn Soda Works. Day 3 the vendors I tried weren’t accepting it anymore because of technical failure.

This experience got me thinking, does this app work any better with a stronger signal? Was my experience simply based on the context of the festival? I opened up the PayPal app, looked through the local businesses available, and took a trip to Van Leeuwen’s for a (mostly free) scoop of ice cream with ridiculously delicious fudge. The app worked! And then it crashed my iPhone. However I was able to pay and get the $5 coupon discount and, more importantly, enjoy a little piece of ice cream heaven.

Phil: After Kathleen and I discussed her experience, I went ahead and tested the take out ordering for the PayPal app on Android.  I found that it works like any food ordering app. All mobile ordering relies squarely on the structure and capabilities of the Eat24Hours service. My experience with setup was fairly easy, although you have to enter a lot of basic information, including a picture, which might deter some people.

After set up, I found that the app was slowing down the ordering process with numerous errors. At first the PayPal app was stuck on the “delivery” setting for food, and even when I toggled the setting to “takeout” the delivery fee and minimum order remained on screen. The app’s ordering function also repeatedly timed out with a plain text screen reporting an unspecified error. On top of all this, the ordering process was generally very slow to load. Feeling discouraged, I shut down the app for the day and ordered through other means.

 One error encountered with PayPal: Despite selecting “Pickup” the app still thought I was ordering “Delivery”.

The next day I opened the app again to order some lunch, and thankfully the process went smoothly. I was able to pick up my food without any hiccups. I hope that the errors Kathleen and I experienced will be worked out over time, so the app can become a more reliable source of ordering.

Google Wallet doesn’t provide a method to find local stores where payment is accepted, limiting its effectiveness as a wallet or credit card replacement

I also reviewed Google Wallet on Android, a mobile payment app whose main point of differentiation is the use of Near Field Communication (NFC) for point-of-sale payments. Since I had already used Google Payments in the past, the setup was quick and easy. The trouble started when I tried to find a location to use the payment method. Google’s site doesn’t provide any list of merchants where Google Wallet payments are accepted. This may be due to vendors being slow to adopt NFC, which is necessary for this type of payment to spread. Unfortunately this leaves the user to find locations themselves, making this convenient method of payment not so convenient. I spent a week in Silicon Valley and a week traveling and I didn’t find a single location to make a payment with Google Wallet. With limited adoption and no means for finding out where this type of mobile payment is accepted, Google Wallet is far from replacing my trusted standard leather wallet.

Kathleen: In this day and age, there’s a lot of potential for mobile payment systems to streamline a manual process. I was at a concert recently where the luxury box seats were offered a paper menu to select menu items and have them brought to your seat. This section was organized by Live Nation, the international promoter. A setting like this one would be perfect for mobile payments. If I could log into my Live Nation app, select what I want from the menu, hit submit, and have it delivered to my seat, I would be so happy!

In conclusion: There are definitely still some usability issues in this area, but we here at Key Lime Interactive are super excited about the future of mobile payments, especially at concerts and music festivals! Next month, we’ll review the current mobile payment landscape, including some novel new approaches to address problems like those Kathleen and Phil encountered above. Until next month…