Swarm: Foursquare's ambitious plan to split its app in two
theverge.com
theverge.com
I use 4sq for two things -- keeping track of where I've been when I travel, and letting people know where I am when I travel in case we're near each other.
From this description, it sounds like I'll need two apps for that now. In which case I might as well just use a Facebook checkin and not use 4sq at all, since Facebook serves both purposes.
But now the thing I use Foursquare for, checking in and finding places nearby are in 2 apps. Before it was ok if each part was good not great because having them both together was a win. But by splitting them the places nearby app is now directly competing against Yelp and Urbanspoon and others.
I'm not installing 2 apps for this, so the check-in part will likely not be done by me anymore. I might still use Foursquare proper, but only if it is better than other similar apps.
The two apps will also work seamlessly with each other, for the moments when you are making a plan for dinner with friends in Swarm app, you can click an icon which takes you to Foursquare app for search. And many more such interfaces.
They're recognizing that the location browsing/discovery UX is fundamentally different than their social UX, and de-coupling them, while presumably using the same infrastructure under the hood. Hopefully, this will allow UI/UX development that diverges and serves each user group better.
I want a better, more usable location database on my phone, I would use it all the time. Yelp is unfortunately the default, I think because through crowd-sourcing data validation, they just have the most accurate listing of addresses, phone numbers, business hours, etc. But after that, Yelp is social features I don't care for, review writing that make me sad about humanity, and very likely bully-esque business practices (but I do like the pictures). Foursquare has the second best location DB that I've used, but historically the app has been more aggressive about pushing it's social features, which I do not want. So, I am curious and cautiously optimistic.
From the comments, it seems like what may be missing is the ability to check-in via the core foursquare app. This would be a problem if the life-tracking-but-not-social subset of users is as high as the comments suggest, but also may not be a problem if the "I was here" feature still exists in the core app and just has been messaged incorrectly.
-- Removing the check-in feature from the Foursquare app and putting into a separate app called Swarm.
-- Making Foursquare 100% about exploring and recommendations, a la Yelp.
This seems like a bizarre move. Unless I'm mistaken, all of their data comes FROM check-ins. People write tips, answer questions ("Is this place good for kids?") and generally contribute their info to the web of data that Foursquare uses to intelligently recommend venues. Couple that with the network effect of having access to friends' check-ins, which to me is probably the strongest signal of a particular venue's quality.
So all that being said, it seems like receiving a high volume of check-ins is critical to Foursquare's recommendation success. They don't have the broad review base of Yelp or an editorial team, so check-ins are all they have. By splitting this functionality into a separate app (outside of the Foursquare app itself), they are explicitly going to lower check-in volume, because SOME percentage of people simply won't download "Swarm". And then if they lose some of their user base, it decreases the utility for all Foursquare users as (a) the recommendation data won't be as solid, and (b) users will lose valuable friend check-in data.
Maybe I'm overplaying the slippery-slope angle, but when your business largely relies on a particular user action (check-ins, in this case), it seems unwise to split that functionality outside of your core product in a move that will unquestionably make taking that action more difficult.
[1]: http://www.theverge.com/2014/5/1/5666062/foursquare-swarm-ne...
We looked at the session analysis and saw that only 1 in 20 sessions had both social and discovery," says Noah Weiss, Foursquare’s vice president of product engineering. In other words, just 5 percent of Foursquare’s users were opening it to find friends and find a restaurant. "Why not actually just split those apart, because 19 out of 20 times, tapping on one icon or the other, you have satisfied your need completely," says Weiss.
"And as mobile usage has broadened and evolved you get individual experiences instead. You open an app to do a specific task and not as a gateway to a large complicated experience."
Having the check-in button as the main interface every time users opened the app created a noticeable hurdle for engagement. "Imagine if you opened up YouTube and the first thing it asked you to do was create a video. That would scare off a lot of people," says Bijan Sabet, one of Foursquare’s early investors and a current board member. "Just like you don’t need to tweet to enjoy Twitter, splitting the app in two will help make it clear to a big audience that you don’t need to check in to find value in Foursquare."
≠=================
BTW a lot of the reasoning of the unbundling of features in the mobile app world is very nicely outlined in bill gurley' 's post: http://abovethecrowd.com/2013/07/17/transitioning-to-a-mobil...
Looks like Foursquare was thinking along the same lines:
> We built Swarm because you’ve told us how often you still have to text your friends: “where are you?” and “what you up to later?” We wanted to build a quick way for you to know these two things for all of your friends.
I suspect this also has to do with internal development mechanics as well. Unbundling lets the Messenger team push app updates out more quickly, without having to worry if their changes broke the main Facebook mobile app.
Not sure what's up with Paper, but I'd guess it's about letting the Paper team experiment with new UX ideas without fear of upsetting the majority of users still using the current app.
Back to synced plaintext files, maybe?
It doesn't look like any functionality is being lost from the standalone 4sq app as it is now, just separated because people aren't using them together anyway.
Those of you arguing for a thread-merging feature on HN will find this a juicy example for your cause. (Edit: which I'm also slowly becoming convinced of.)
1. http://blog.foursquare.com/post/84422758243/a-look-into-the-...
What doesn't make sense to me: at the core, users that (still) use Foursquare use it to check in. From there we vary, but we check in. More importantly, that's the perception around the app. Changing perceptions with an existing brand is difficult. Why move the existing user base to a new app built around checkins (Swarm) and try to rebrand the checkin app (Foursquare) to attract new users and compete with Yelp?
Confused? Me too.
But it's odd that they'd create a new app around checkins and continue trying to associate the foursquare brand with discovery. Wouldn't it be easier to keep foursquare as "the checkin app" (how people already see it) and create a new brand identity for "the discovery app"?
That said, Swarm looks really smart - in fact, it's something I'm amazed FourSquare haven't done before now. I want to be able to post a status saying "Lunch?" tagged with my location and let my friends who are nearby with no lunch plans reply.
To me it seems you've just split your focus. And for a start-up that has pivoted a million times and was "featured-out" by Twitter and Facebook, I'm saying you guys have it cut out for you.
Are you a messaging service? Are you a check in yelp thing? Two different problem domains, which will make swapping resources in between apps difficult.. communication between development teams across both products will begin to break down and tenets/design philosophy/code quality will begin to diverge. There will be a "better app" and a "crappy app," which will do wonders to swiftly destroy the culture on the team that is getting less love.
Good luck to you.
Is there any app that allows one to place a digital file onto a map's geocoords - whereby you can ONLY access that file if you actually go to that geocoord and then can open/see the file?
Is it only me getting confused with them? (I dont live in US so I dont have access to most of those services thus I am not really used to their names but so many "Squares" lately).