Path, Eight Years After It Shut Down: The Interaction Design It Left Behind

Last updated: 13 October 2026 · By Xin Wang · 中文

Path was a mobile social app meant only for the people close to you. It launched in November 2010 and stopped service on 18 October 2018. It did not succeed as a business, but several things many iPhone users have seen trace back to it: the “+” button that fans out into an arc, the small clock that follows you as you scroll, and the drawers on the left and right. I went through its public record from the beginning and wrote a longer research report. This is the short version: how it worked, why it was built that way, and what it cost.

• Eight years in brief
• Why only 150 friends
• Little input, a lot of context
• The radial “+” menu
• The scrolling clock
• Side drawers, and their exit
• Feedback without a “Like”
• Sleeping and waking
• The cost of “add friends”
• What still applies today
• What I could not confirm
• FAQ
• Sources

Eight years in brief

Path 2 was the turning point. In the two and a half weeks after it launched, daily active users went from about 10,000 to 300,000 (TechCrunch). Almost everything below comes from that version.

Why only 150 friends

Nearly every design decision in Path follows from one premise: social sharing should happen among a small number of close people. The launch post for the first version cited the anthropologist Robin Dunbar and treated 50 as the outer edge of a personal network (Path blog). Path 2 raised the cap to 150, the figure usually called Dunbar's number.

Path 2 also fixed the form of the content as a journal: not only photos, but a thought, a place, who you are with, the song you are listening to, whether you are asleep or awake. Morin was blunt about the first version. He called it 70% a failure, with too many screens when people really used only one, and said the Path 2 home screen went through more than twenty iterations (VentureBeat). So Path 2 squeezed the whole app into one scrolling timeline and tucked everything else away.

It never carried ads. Revenue came from paid filters, stickers and a subscription, which also explains why the product leaned towards stickers and messaging after 2013.

Little input, a lot of context

Path called each post a Moment. The user usually supplied one thing: a photo, a sentence, or a place picked from a list. The system added the rest: capture time, coordinates, city, and the weather at that moment. The server then assembled a headline and a subheadline and sent them to the phone ready to display.

This is not guesswork. In 2012 there was an open-source, unofficial Mac client called Journey, and its test files keep real samples of what Path's interface returned. The samples show several things:

• The server decides the voice. Headlines and subheadlines arrive as finished text. Tap “awake” and the subheadline holds the local time, the weather and the temperature, followed by a playful line. Changing the copy needs no app update.
• Two timestamps. One for when the thing happened and one for when it was published. An old photo added from the camera roll is slotted into the timeline at the time it was taken. The timeline follows the order of life, not the order of posting.
• Weather is data on every record. The sample has cloud cover, temperature, dew point, wind speed and wind direction. Searching old moments by weather, added later, rests on this.
• Precise location is everywhere. Not just the moment itself; every comment carries coordinates and weather too. Few people knew that at the time.

The slogan about a journal that writes itself comes down to this structure in engineering terms: writing is light, filling in is heavy.

The radial “+” menu

Path 2 put every way of posting behind one red “+” in the bottom-left corner. Tap it and the “+” turns into an “×” while six icons fly out of the button and spread along a quarter circle: camera, people, place, music, thought and sleep. They do not leave at the same instant, and each bounces slightly as it lands. The one you choose swells and fades; the rest shrink back into the button. Morin said this one animation took about six months to get right (Forbes).

Path never published its parameters. The closest reference is the open-source library AwesomeMenu, whose source is dated 30 November 2011, the day after Path 2 launched. Its example project contains a Path-like configuration:

With these numbers the sixth icon takes off at 0.18 seconds and the whole menu is open in under half a second. One detail worth noting: the “bounce” here is three scripted straight segments, not a physical spring.

Why build it this way? My reading has three parts. First, six post types laid out as a toolbar would eat into the timeline; one button keeps the home screen clean. Second, every icon on the arc is the same distance from the “+”, which is easy on the thumb; the designer Josh Clark, defending radial menus at the time, also noted they top out at around eight items. Third, the icons come out of the “+” and go back into it, so nobody needs to be told that posting lives in that button. The price is one extra tap for every post, and an arc is harder to scan than a list.

The scrolling clock

Posts in the Path 2 timeline carry no time. Start dragging and a small dark bubble appears beside the scroll indicator on the right, with a tiny clock face and a time such as “11:49 AM”: the time of the post next to the bubble. The hands turn as you scroll, and the bubble lingers briefly after you stop before fading out.

The designer Dustin Mierau gave the reasons: without timestamps more stories fit on a screen and the feed reads more naturally, and a clock with hands adds the feeling of moving backwards and forwards through time (App Design Book interview).

This control was cloned quickly as well. The open-source TimeScroller was created five days after Path 2 launched. It fades in over 0.2 seconds, waits 1 second after scrolling stops, then fades out over 0.3 seconds; the hands turn in the direction of time rather than by the shortest route. Again, these are a clone's numbers.

Timestamps did not vanish entirely. Comments and notifications still said things like “14 mins ago”. And not everyone was convinced; some reviewers wanted the time of each post shown more clearly.

Side drawers, and their exit

Path 2 had no bottom tab bar. Tap the button at the top left, or swipe sideways on the timeline, and the whole page slides aside to reveal a drawer underneath: navigation and settings on the left, just five items; friends on the right. Facebook's iPhone app had introduced a left-side menu seven weeks earlier, and Path extended it to both sides. Several popular open-source drawer libraries then named Path 2.0 in their descriptions, among them ViewDeck and JASidePanels.

Drawers suited the Path of 2011, which had one main stream and little else anyone visited often. By 2013, messaging, the sticker shop and friend management were all frequent destinations, buried deep in a drawer. Path 4 in 2014 moved navigation back to a bottom tab bar. The whole industry was giving up the “hamburger menu” around then: one app ran a comparison and found weekly usage 55% higher with a tab bar (TechCrunch).

Feedback without a “Like”

Path never had a “Like”. It split feedback into steps, each taking a little more effort than the last:

In a circle of a few dozen relatives and friends, being seen is already a response: you post a family photo, and knowing your mother saw it is enough. People who posted little, or had few friends, still got something back.

The cost was pressure on both sides. Viewers could not look quietly, and even a profile visit sent a notification; posters could see who had looked and said nothing. In 2013 Path added the choice of who sees each moment, a control it supplied itself. The five emotions (smile, laugh, gasp, frown, love) were finer than a single like; Facebook's similar Reactions arrived in 2016.

Sleeping and waking

The most unusual of the six post types was sleep. Tap it before bed and the timeline shows that you are sleeping in a given city, and push notifications pause. Tap again on waking and notifications resume, the server works out how long you slept and adds a line to go with it.

Morin's explanation was that in the mobile era a person's state is no longer online or offline but asleep or awake (quoted by dcurt.is). People were willing to tap it daily because it was useful: no notifications at night, and the waking card showed the day's weather. One designer wrote that he tapped “awake” just to see what the weather was like (Rian van der Merwe). Two and a half weeks after Path 2 launched, more than a million people had shared going to sleep or waking up.

It was entirely manual, with no automatic detection. How the screen changed after the tap, or whether there was a night-time view, I could not find in any text or screenshot.

The cost of “add friends”

Path was built on being private by default, yet it got into trouble three times on the same path, each time at the step of adding friends.

1. February 2012: the address-book upload. The developer Arun Thampi inspected the traffic and found that Path sent the whole address book to its servers after login (his write-up). The add-friends screen offered three options, but the upload happened whichever one you chose, or if you chose none. Path apologised, changed the app to ask first and deleted the contacts it had collected. Apple said apps would need explicit permission to read contacts (AllThingsD), and iOS 6 added the permission prompts (MacRumors).
2. February 2013: the FTC settlement. Besides the address book, the complaint said personal information had been collected from about 3,000 users under 13. Path paid an $800,000 penalty and agreed to regular privacy assessments for 20 years (complaint).
3. Spring 2013: automatic text invitations. The sign-up screen pre-selected every contact. One user's entire address book received invitation texts sent in their name early in the morning (iDownloadBlog). The class action that followed was settled for $5 million (Top Class Actions).

What a small-circle product fears most is emptiness: without your people in it, it is an empty room. So all the pressure to grow landed on “add friends”, and every detail of that step became a privacy decision: whether the options were real options, whether a checkbox started ticked or empty. Next to its most polished animation, Path placed an add-friends flow that was not honest.

What still applies today

These are my own conclusions, not statements from the Path team.

• Ask the user for little and let the system add context. Any app for recording things can borrow this structure. But show users plainly what is collected automatically.
• Store “when it happened” and “when it was posted” separately. Only then can something recorded late land where it belongs.
• Animation should explain structure. Icons come out of a button and land on the timeline; one look and you understand. Animation that is only decoration slows down every action.
• Feedback can come in steps, but give people a way to be invisible. Visible attention is also pressure.
• Give a daily ritual a practical hook. Weather on the waking card is one.
• Leave room in the navigation. Drawers only suit an app with a single main stream.
• Adding friends is the riskiest step. Options must be real options, invitations must be ticked by the user's own hand, and permissions should go through the system prompt.
• Smoothness is part of design. Path open-sourced an image cache, FastImageCache, whose README starts from the fact that a frame has only 16.7 milliseconds.

It would be much simpler to build today. The bounce once faked with three straight segments can be done in SwiftUI with a spring animation and a per-item delay, and it can be interrupted at any point. The scrolling clock no longer has to reach into the system scroll indicator's internal views; you can look up the current item's time from the scroll position.

What I could not confirm

The facts here come from press coverage between 2010 and 2018, Path's own blog, FTC documents, the code of open-source clones, and the interface samples kept by that unofficial client. I used no internal Path material, and I was not able to read the historical snapshots on the Internet Archive. I found no reliable record of the following:

• The order of the six icons on the arc, and the original's rotation angle, animation duration and whether it had sound.
• What the right drawer, the emotion picker and the sleep and wake screens looked like.
• The original fonts and colour values.
• Who supplied the weather data.
• The peak number of users. Coverage of the shutdown ranges from 15 million to about 50 million, while the highest registered figure reported at the time was 23 million.

Sources also disagree in places. On daily-user growth after Path 2, reports at the time said 10,000 to 300,000 in two and a half weeks, while Morin, recalling it in 2015, said more than 500,000 in two weeks. This article uses the contemporary report.

FAQ

When did Path shut down?

Path announced the shutdown on 17 September 2018, left the app stores on 1 October and stopped service on 18 October 2018. It launched in November 2010 and was sold to Daum Kakao of South Korea in May 2015.

Are there official numbers for Path's “+” menu animation?

No. Path never published its animation parameters. The numbers that can be found come from the open-source clone AwesomeMenu: a 90-degree arc, a radius of about 100 pt, 0.3 seconds of flight per icon and 0.036 seconds between icons. They are what someone measured and rebuilt, not Path's own values.

Is Path the reason iPhone apps ask before reading contacts?

It is closely tied to it. In February 2012 Path was found uploading users' whole address books without asking. Apple then said that apps would need explicit permission to read contacts in a future release, and iOS 6 added permission prompts for contacts, calendars, reminders and photos.

Sources

Besides the links in the text, the main references were:

• Path blog: Introducing the Personal Network (2010)
• US Federal Trade Commission: complaint, consent decree
• Open-source code: Journey for Mac, AwesomeMenu, TimeScroller, Android Priority Job Queue
• Reviews from the time: Brenden Mulligan: Path 2, Brian Lovin: App Dissection – Path, Technologizer

Read next

• iPhone 18 Pro vs iPhone 17 Pro: same size outside; cooling, battery life, charging and the Main camera compared from official specs.
• All articles