The Right Way to Ask Users for iOS Permissions

We recently shared a bunch of information on how we ask for permissions in our iOS app. Take a look!

we’ve spent significant time at Cluster on small interactions that increase users’ comfort and trust. One area we’ve focused on in particular is how we ask iOS users for access to things on their phone.

Our biggest takeaway: don’t ask a user for access until you really need it, and make sure it’s crystal clear what they will get in return. 

New Versions of Cluster in the App and Play Store

Today we’re happy to release Cluster 1.5 for iPhone and Cluster 1.2 for Android. You can download both of them right now!

This iteration of Cluster comes after months of user research. And while we’d love to tell you it’s an entirely different app, most current users won’t notice much difference (this is a good thing), as the majority of the changes are in the new user experience.

We’ve made the app a bit faster and easier to use, and we added some subtle bells and whistles — but overall, your Cluster “spaces” will feature the same great experience you’ve gotten used to. We will be posting a longer explanation why that’s the case soon, but for now, here are some of improvements existing users will see with this release:

Streamlined Invitation Process
Through a lot of subtle behind-the-scenes work, we’ve made it much easier to find and invite people to Cluster. We added a much simpler way of searching and identifying your friends and family, and accepting an invite has gotten significantly faster and easier.

New Cluster Space Creation
We turned the process of creating a new space on its head. Instead of choosing photos first, the process begins with who you are going to share with — spaces are all about the people in them, after all.

New users will see:

Drastically Improved Experience Before Login
We spent a lot of time making what Cluster does much clearer for someone who’s never used the app before. As a result, the logged-out screens have been redesigned from scratch.

Simpler to Get Started
The first thing you see when you sign up is much simpler than it used to be — and we thoughtfully crafted the path to creating a meaningful space. New users should never get lost again.

Simplified Registration
We removed a bunch of steps from new user registration, getting more new users into Cluster with just a single tap!

These are just a few of the things we added, and many more will be revealed in our next version — coming soon to your local App Store this May!

How to Run Live User Testing, Part 3: Debrief

Originally posted to Medium

This is the final post of a three part series on how we run live user testing at Cluster. After months of constant iteration, we’ve paused to focus on testing before the next release of our iOS and Android apps. Follow us on Twitter at @cluster.

The first post focused on getting the test setup, which includes deciding on a specific thing to test, deciding when and where to do the user study, deciding what type of users to study, recruiting participants with Craigslist, trimming the candidates list, prioritizing and scheduling candidates, and getting the right equipment.

The second post focused on actually running the tests, which includes arranging the room, meeting the participant, introducing the study, not revealing the answers, simulating app discovery and installation, walking the user through the prototype, and wrapping up.

This post will focus on taking all that amazing feedback you just gathered and parsing it into useful, actionable intelligence.

One more time, I want to give a huge amount of thanks to Michael Margolis and the Google Ventures design team, who taught us most of these techniques.


So what next? You have a set of recordings containing incredible user feedback, and now it’s time to parse and process it so you can turn the insights into action items for your product. Here’s how to pull out the good stuff and get your team on board with next steps:

  1. Schedule viewing party
  2. Distribute materials
  3. Capture insights and ideas
  4. Combine everyone’s insights
  5. Identify patterns
  6. Bucket patterns according to app sections
  7. Address the problems & start again

Like the first two parts of the study, this takes time, but it’s very worth it in the end.

Schedule viewing party

The first step is to schedule a time for the company’s key decision makers to review the videos. Including everyone might sound like a waste, but it’s very important. I know because we didn’t always do this.

When the whole team sits around, you have a much bigger opportunity to understand what feedback is important and what is worth ignoring. You’ll pull a lot more out of the sessions.

imageReviewing the videos with the Cluster team

So, even though it seems like a lot of time, schedule time for the core team to watch all the videos in their entirety. Don’t skip this, or you’ve wasted all the time prior.

Distribute materials

While watching the videos, the goal is for the team to capture insights and ideas from what the user is saying and doing. The tools we use to do this are:

imageTools for capturing thoughts and ideas
  1. 3x5 inch post it notes
  2. Legal pad
  3. Regular pen
  4. Thick marker

Capture insights and ideas

We’ve found it helpful to instruct everyone to capture two kinds of things on paper while watching:

  1. Important insights (good and bad) learned from the user on the notepad
  2. Any specific implementation ideas on post-it notes
imageMy notes and ideas from 5 videos (slightly blurred for confidentiality)

The majority of the writing will be insights from the user and should be captured with a normal pen and paper. Examples of insights are things like

  • “Blue button really works”
  • “Really understood intro page”
  • “loves design”
  • “had no idea what to do first”

Everyone should write down everything they notice from what the user is saying / doing.

If the insights lead a team member to have a specific idea of how to fix / improve the app (ex. “Add ‘We will never post’ under the Facebook login button”), have them write each down on their post-it notes using a thick, black marker. Getting these ideas down on paper will let the team member focus on the rest of the study instead of trying to remember their idea.

Combine everyone’s insights

After watching each video, have someone stand at a white board and write down the insights everyone captured. Use a green marker insights for things that worked, a red marker for things that didn’t work, and black for general insights. Only write down things that more than one team member heard. The purpose of this step is to distill everyone’s page of notes into a common list of insights to address later.

imageThe board after one of our debriefs (slightly blurred for confidentiality)

Create one column of notes for each study participant. Then, somewhere off to the side, have everyone put up their post-it notes in no particular order.

Identify patterns

Once you’ve watched all the videos, and everyone’s insights are up on the board, it’s time to find patterns. It’s not worth fixing every small issue each person had because all users are different. The goal of the entire exercise is to figure out the reoccurring problems that might also effect users in the wild.

With a new color, circle or draw a dot near any insights that come up more than 2 times (or more than 40% of the time depending on your number of participants). Do this for green, red, and black insights.

Bucket patterns according to app

Now that you know what common insights came from testing, it’s useful to categorize what part of the app the insights affect. With Cluster, our users were testing four sections:

  1. Pre-Registration Screens (including App Store marketing)
  2. Creating & Naming Initial Cluster
  3. Inviting Friends
  4. Uploading Photos & Exploring App

On another whiteboard, we made a column for each section. Then, we went through the first whiteboard and moved each recurring pattern over to the appropriate column.

imageCommon insights and patterns (slightly blurred for confidentiality)

Suddenly, hundreds of insights were distilled and organized according to the part of our app they affected. An actionable list emerged.

We then moved the ideas that had been posted underneath the insights. What we found was that most negative insights already had some great suggested ideas for improvements.

Address the problems & start again

Now it’s time to get to work to improve the product to address the common negative insights you found during this process. Then, start over and do the whole thing again. Keep going until you’re satisfied that the problem areas aren’t too big of a deal.

You did it!

You’ve now completed the entire user testing journey! I know it’s a lot of work, but once you do it a few times, you’ll start to see problem areas disappear and users start to understand your app much faster. It’s invigorating. I’d encourage you to trust the process and see what happens. I guarantee your app will become easier and more delightful to use.

How to Run Live User Testing, Part 2: Test Day

This is the second post of a three part series on how we run live user testing at Cluster. After months of constant iteration, we’ve paused to focus on testing before the next release of our iOS and Android apps. Follow us on Twitter at @cluster.

The previous post focused on getting the tests setup, which includes deciding on a specific thing to test, deciding when and where to do the user study, deciding what type of users to study, recruiting participants with Craigslist, trimming the candidates list, prioritizing and scheduling candidates, and getting the right equipment. Please make sure to read that post before continuing below.

This post will focus on actually running the tests. The next and final post will explain how to take the information gathered and parse it with your team in a meaningful way.

Again, I want to give a huge amount of thanks to Michael Margolis and theGoogle Ventures design team, who taught us most of these techniques.

Running the Tests

The day has arrived and it’s time to actually show the participants what you’ve been building! I’m going to break this into the following sections:

  1. Arranging the room
  2. Meeting and prepping the participant
  3. Introducing what the test is about
  4. Not answering questions
  5. Simulating the discovery and installation
  6. In the prototype: Pre-registration
  7. In the prototype: Registration
  8. In the prototype: First user experience
  9. Wrapping up

It’s exciting, but will be a pretty exhausting day, so get plenty of sleep before and arrive at your testing site at least an hour in advance of your first interview to get set up.

Arranging the room

I like to arrange the seating so the participant and I are sitting by the corner of a square table, or at the 12 o’clock and 3 o’clock position of a round table. Set your computer up in front of you, and the camera facing directly down in front of the participant. It makes the conversation feel a little more natural, but they can’t see what’s going on on my computer.


With the camera plugged into my laptop and using the included software, I could see the participant’s hands and phone fullscreen on my laptop. To capture the sessions, I recorded the video of my screen and the audio from the microphone on my computer using Screenflow. If you want to record a participant’s face, you can also get a separate camera to point at them, although I don’t think it’s necessary.

Meeting and prepping the participant

When the participant arrived, I’d invite them into the room and before recording, give them a general idea of who I was and what to expect during the session.

When introducing myself, I wouldn’t be totally honest. Although I’m the CEO, I introduced myself as barely part of the team. My line was usually:

You’ll be testing an app that hasn’t been released yet. The team that designed and built it asked me to show it to users before they launch it to make sure what they’ve built is something that people will understand. Because I wasn’t a part of the creation of the app, it’s important that you know that if you say that it’s great, I won’t be flattered. If you say it’s terrible, I won’t be hurt. My goal is to get your opinion, so just be honest. Then I’ll be taking the recordings and showing the team next week.

Then I usually make sure they understand that they aren’t being tested:

When I ask questions, I’m not testing you, I’m trying to understand how well the app is designed. Please remember that the goal here is to see how well the app is explaining itself. So don’t feel like you should know all the answers. If you are confused at any point and don’t know the answer, that isn’t a sign of your intelligence. It probably means the app isn’t explained well. So hearing you say “I don’t know” is a lot more valuable than you trying to come up with an answer. There are no wrong answers, and “I don’t know” is a perfectly acceptable answer in this session if that’s what you’re feeling.

Finally, I give some structure for the session:

This will last about 45-60 minutes and be very casual. The camera there will record your hands using the app. The computer will record our voices. As you use the app, I’ll be asking a bunch of questions and will also ask that you try to think out loud as much as possible. Tell me what you’re seeing, what you’re thinking, what you understand and what’s confusing. And don’t hold back, even the smallest details are exceptionally useful for the team.

Then I position their phone in the frame and say “I’m going to start recording now”.

Introducing what the test is about

This will be different for everyone, so I’ll just talk about how I did it you can modify your own way depending on what you’re testing.

We were testing a new on-boarding flow for our iPhone app. Since the version being tested wasn’t available publicly, we installed the app onto the participant’s phone using a friend’s enterprise certificate from Apple. It was important to us for the participant to have our app on their phone because our app interacts with their photos and contacts. If you don’t need the participants to have the app on their phones, I’d recommend bringing an iPod touch in and having them use that (much easier).

Not answering questions

In the next steps, as the participant is going through your prototype, most likely they’ll ask you questions like “What does this button do?”, “Am I registered yet?”, and other basic stuff. It’s important that you don’t answer any of these questions. Remember, you don’t know. You’re just helping the team test an app you’re not that familiar with.

When asked almost anything by the subject, I responded with something like “I don’t know. How do you think it should work?”

Simulating the discovery and installation

For our simulation, I texted the participants a message saying “Hey! Check out this new app: [url]“. I told the participant “Pretend a friend sent you this message. There’s no context, just a link to the App Store.”

imageOur mock App Store page

When the participant clicked the link, it sent them to a mock App Store page we built with a title, screenshots, and a description. It wasn’t as fully functional as the real App Store, but it worked for our purposes. On this page, I’d ask them things like:

  • So what’s your initial perception of this app?
  • What do you think it’d do?
  • What part of this page made you think that?

There’s a surprising number of insights that come up at this point around how users evaluate apps in the App Store.

Once I feel like we learned all we could from this step, I asked them to install the app. They tap “Install” and it pulls the app from the App Store and puts it on their home screen.

In the prototype: Pre-registration

Exciting! The user is actually IN the prototype! This is when the really great feedback starts flowing.

The on-boarding we tested involved a scrolling intro screen and a “Get Started” button at the bottom. I would usually have the participant spend about 5 minutes looking at this screen, during which I asked them:

  • Talk about anything new you’re learning about the app
  • Is the description different than what you remember from the App Store, and how?
  • Do you have a use case for this app? What would it be?

It’s worth noting that most real users skip over these types of screens. In my opinion, that doesn’t render testing them useless because some people actually read them, and if you’re going to have one, it’s best to make sure it’s really clear.

Once I feel like we’ve exhausted the feedback coming from this screen, I tell them to move onto registration.

In the prototype: Registration

We love testing our registration page because we offer several ways of signing up (Facebook, Google, and email), and it’s great to listen to participants talk about what they are comfortable with and why. As things like:

  • How do you normally sign up for apps?
  • Why do/don’t you use Facebook?
  • Is there anything you’re concerned about?

I think this is a really valuable step, and you’ll probably learn something from it.

In the prototype: First user experience

Cluster requires the user to create something right away, and we were testing a new version of this flow. It’s hard to summarize that here because it’s so specific to what’s being tested, but essentially I watched the participant go through each step and continually asked:

  • Do you know what’s happening here?
  • What do you think the app has done with that information?

Again, hard to generalize, but what I tried to learn is how well the app was communicating what was actually happening.

In addition, you learn a lot about button placement, confusing wording, weird user flows that made a lot a sense to your team, but no sense to someone who’s never seen the app before.

Wrapping up

Even after the user created their first album on Cluster (the goal of the study), I just sat quietly to see what came out as they explored the product. In 4 out of 5 sessions the participant kept talking about stuff they liked, disliked, didn’t understand. Learnings galore.

Before ending the session, I’d ask:

  • Any other thoughts about the app?
  • Is this something you think you’d use?

After a couple minutes, I’d tell them that their feedback has been really helpful, and end the recording. Then I’d give them the Amazon certificate and reiterated how grateful I was for everything they shared.

Rinse and repeat

The first one will be rocky. That’s fine, they’ll get easier. So get ready for the next one. It’s going to be a long day.

Debrief time!

You now have a set of amazing feedback recorded from your participants. If the team wasn’t able to watch them live, the next step is a team debrief. The next post will cover how to pull the best insights out of what the participants have shared. For now, pack up and go relax. The hard part is over.

Please feel free to reach out to me at @mulligan on Twitter and ask any other questions in the meantime!

How to Run Live User Testing, Part 1: Setup


At Cluster, we’re big fans of iteration and experimentation. Since we launched publicly in February 2013, we have rapidly iterated the product on both iOS and Android. In the first 8 weeks of being live in the Apple App Store, we launched 10 updates. On Android, there was a week that we pushed out 5 releases in 5 days while we did some heavy A/B testing.

While rapid iteration is wonderful, at times we also slow down and make more deliberate decisions about larger changes. When this happens, we tend to make rapid prototypes and then test them in front of different groups. Most of these tests are fairly informal, but occasionally (admittedly not often enough) we run full-blown user testing, where we recruit and bring in potential users to walk through the app and give us feedback.

We are working on a big update, so we recently ran multiple sessions for different prototypes. When talking about it with fellow entrepreneurs, they asked us for details. Here is our ever-evolving playbook.

Because this is fairly lengthy, we will write this in three parts:

  • Setup
  • Running the Tests
  • Debriefing

Before getting started, I want to give a huge amount of thanks to Michael Margolis and the Google Ventures design team, who taught us most of these techniques.

Part 1: Setup

User tests are extremely valuable, and require a lot of work to get set up. All in all, it takes a significant amount of one person’s time over the course of a week to setup the tests and run them well. So make time to do it correctly.

The setup process is divided into the following sections:

  1. Decide on a specific thing to test
  2. Decide when and where to do the user study
  3. Decide what type of users to study
  4. Recruit users with Craigslist
  5. Trim the candidates list
  6. Prioritize and schedule
  7. Get the right equipment

Let’s get started!

Decide on a specific thing to test

We were recently lucky enough to do a sprint with the exceptionally talented design team from Google Ventures (entire post on that coming soon). Over the course of five days, we identified core opportunities with Cluster, brainstormed improvements, built several simple prototypes, and tested the prototypes with potential users. The result of this process was a clear idea of what new concepts were working and what wasn’t.

With the list of successful ideas, the team then rapidly built a single functional prototype based off our current app. With this working prototype completed, it was time to show it to users and see if all the insights gathered from the design sprint worked in the context of our actual app.

Decide when and where to do the user study

I was scheduled to be spending a week in Nashville, which gave us a great opportunity to run our test outside of the Bay Area. This is incredibly valuable because the bay area tends to be filled with tech savvy, early adopters. Nashville has its fair share of them, but technology isn’t as core to the community there, so we felt like this would give us an opportunity to meet more “real” users.

It’s also important to pick a quiet, private, and neutral place. As tempting as it might be to use your company’s conference room, I’d recommend not bringing users into the corporate office. Use a friend’s office or co-working space. All advice we’ve been given is the more neutral the location, the better.

The privacy and quietness is important because you’ll be recording the session, so you don’t want to do it in a coffee shop where there’s a lot of distraction and background noise.

Nashville Entrepreneur Center

When I was in Nashville, I rented a conference room from the Entrepreneur Center. It worked out perfectly.

Decide what type of users to study

This is a very very important part of the process. Before recruiting users, you need to decide what type of people you want to meet with. We had done this during the Google sprint, and because our app involves sharing photos, we asked these types of questions:

  • What type of phone should they have?
  • How involved with social media should they be?
  • What apps should they use (and not use)?
  • How many photos should they take per week?
  • How old are they?
  • How do they share photos currently?

With these questions in mind, we created a Google Forms survey that would help us clearly identify if the potential tester fit our target profile. It’s not worth user testing if you’re not testing the right type of user, so take some time and do this step properly.

The actual screener we used for our Nashville studyThe actual screener we used for our Nashville study

Since the user is going to have to physically be somewhere, it’s also useful to get their availability. We did that by starting with the question saying “Which of the following times are you available on Thursday February 6 to come to downtown Nashville?” with 5 options for time slots.

Recruit users with Craigslist

About a week before we planned to do the user testing, we posted a job opportunity to the jobs/et-cetera section of Craigslist. In this relatively short post, we give very little information, except we are looking for people to participate in a usability study, they’ll need to be okay signing an NDA and being filmed, and we are willing to pay them for their time (in this case, a $75 Amazon gift card for a 60 minute meeting).

Craigslist post driving people to the screenerCraigslist post driving people to the screener

The post did not let users email reply. Instead, there was a link to a Google form we built above. That made it super easy for consolidate and organize everyone’s responses.

Trim the candidates list

Usually, we’ll get between 60-200 applicants within a few days. We try to pare that down to 5. This happens over several rounds of editing.

For this study, the first big cuts happened with device type. Because of the small amount of time we had to build the prototype, we only could test with iPhone users that had iOS 7 installed, and ideally an iPhone 5 and up because we didn’t have time to optimize for all screen sizes. Although this skewed the users a bit, we were able to re-balance it by looking at the other info.

Example responses from the Nashville screener, with all personal information removedExample responses from the Nashville screener, with all personal information removed

We then eliminated anyone who didn’t take photos with their phone. Although it might be interesting to talk to these users eventually, we were looking for people who would have an immediate reason to use our app. If they didn’t take photos, it was unlikely they’d be the type of user we wanted anyway.

Prioritize and schedule

With the remaining candidates, we looked at their age, occupation, and a couple other data points and put together a prioritized list of the people we were most interested in talking to. At this point it became a scheduling exercise, slotting our top pick for each time slot and choosing a backup if that person couldn’t make it.

Each candidate was emailed saying they’d been selected for a time slot and they needed to write back within a certain time frame to confirm, or their slot would be given away. The backup list was emailed saying they were on the backup list and to let us know if they no longer could make it if picked, otherwise they would hear by a certain time if they were needed.

Moving candidates around while schedulingMoving candidates around while scheduling

As a warning, people are VERY flakey. Out of the 5 top candidates, only 3 confirmed, and one of them cancelled the day of. It wasn’t a problem because we were able to fill in the slots with our backups, but it’s a bigger pain that you’d expect. It’s even wise to have multiple backups just in case.

Get the right equipment and software

We were testing a mobile app, so it was important to record the user actually using the app. Although you can do this by plugging the app in and watching a screencast on the computer, it’s much better to actually see them touching their phone. We purchased a $100 camera for this, and it’s well worth the investment.

IPEVO Ziggi-HD High-Definition USB Document Camera

The only other thing you’ll need is a way to record the audio and video of the session to your computer. For this, I recommend an excellent app called Screenflow.

Now it’s time to test!

You’ve got the goals, the users, and the equipment. Now it’s time to show up and run the tests! The next post will cover setting up the room and running the tests with live users.

Please feel free to reach out to me at @mulligan on Twitter and ask any other questions in the meantime!

We’ve beautified albums on the web!

Today, we’re excited to refresh Cluster on the web. We’ve been quietly adding features over the past few months, but today we’re launching the new design with a couple key additions.

Grid & Feed View

You can now view your beautiful images as a feed, or as the traditional grid. We recently brought the feed to our iOS and Android apps, and it’s only appropriate that web users can get it too. 

Toggling between the views is simple. Just tap Feed / Grid in the toolbar above the photos. Enjoy!

Albums list in sidebar and activity list

We’ve made switching albums and seeing album activity extremely straightforward.

To access your other albums, just tap the list icon in the upper left to reveal the sidebar. For the activity list, just tap the bell in the upper right.

Create albums and invite members directly from the web

Since we launched, our website has let you view the albums you create on our mobile apps. Today we’re bringing some more of the functionality to the web. You can create clusters by clicking “New Album” in the sidebar (see above).

To create a new user, just tap the user+ icon next to all profile photos of the other members. Then just start typing in a name, email address, or phone number.


There are a lot of other hidden goodies, but those are the big ones. We hope you enjoy!

A better Cluster is waiting for you to upgrade

Take a look over at the App Store or Play Store, and you’ll find the latest version of Cluster. We’re really excited about it.

When building software, usually companies focus on features, features, features. And we’ve been doing that since we launched. But with this release, we spent some time polishing the design.

With the previous release of Cluster, we drastically changed the way the album page looked. The default layout changed from a grid of photos to a single feed of new photos, with likes and comments visible and accessible (and the option to switch back to the grid). Even though the design was rough, our users loved it.

So with the latest version, we spent some time making sure it looked fantastic.


In addition to the redesign, this release is loaded with some other goodies, and we have a big surprise coming soon. But for now, enjoy the new version and please send us feedback.

Download now from the App Store or Play Store.

'Tis the Season for Photos!

Is everyone in your family taking photos during the holidays this year? Cluster is the perfect place to create a private album where you and your family can contribute photos from any device.

Just follow these simple steps to make a holiday album with everyone’s photos:

1. Download the app for iPhone or Android and sign up or log in.

2. Start a new album with some of your holiday photos.

3. Invite friends and family to contribute their own photos to the album.

That’s it! You’ll all end up with an album where you can see each other’s photos and comment on you favorite ones.

Create as many albums as you like throughout the holiday season and beyond - it’s all free, and there’s no limit to how many photos you can add!

Happy holidays!

Welcome Pat Fives, Android Ace


We started by building Cluster exclusively for iOS, but have always wanted to include our friends with Android phones in our favorite albums. We never had the engineering bandwidth to build the app on a second platform until we met Pat Fives, and our expectations changed radically.

We met Pat on a video call from his former place of residence, North Carolina — and right off the bat, we realized we that were talking to someone who cared deeply about the Android user experience. His enthusiasm for building great Android apps was the perfect match for our enthusiasm for building great iPhone apps, and we needed exactly that to make Cluster for Android possible.

From start to initial launch, Pat demonstrated incredible tenacity and talent, allowing us to shift requirements under his feet while he hammered away at bringing the Android app to life in record time.

Pat joined us from Two Toasters, where he worked on great apps like Hootie and open source libraries like Hoot and AndrOAuth (as well as a handful of super awesome apps for well-known clients). In his free time, as a Pittsburgh native, he’s a maniacal Steelers and Penguins fan.

With the initial version of Cluster for Android out in the wild, we’re excited to keep iterating to bring the full Cluster experience across platforms.

Welcome Pat, and thanks for making Cluster for Android a reality!

iOS 1.2 Now Available


Cluster for iOS is new and improved! We’ve been talking to a lot of users lately and have made some significant improvements based on real feedback. Below is a full list of exciting updates that you will notice when you update to iOS version 1.2.

Always feel free to send any feedback you have about Cluster to - we listen!

New in version 1.2:

Take Photos in Real Time

You can now take photos from inside a cluster, just tap the camera icon and choose “Take Photo”. Your photo will be added to that cluster and will be saved to your phone.

Visible Progress Bar

When you upload new photos to a cluster, a progress bar will appear at the top to let you know how long you have left until all photos have been fully uploaded.

Create New Cluster Steps

We’ve removed a few steps and simplified the new cluster flow to make clusters faster than ever to create.

Streamlined Invite Flow

Once a new cluster is created, you then have the opportunity to invite friends and customize the message that we send to them.

New Users

To help new users better understand how to get the most out of Cluster, we’ve added a few tutorial screens to the sign up flow.

Activities List Icon

You’ll find the activities list icon for each cluster in bottom toolbar instead of the top center. It now looks like a newspaper icon instead of a bubble.

Low Resolution Alert

An alert will appear in an individual photo view if the person who uploaded the photo closed the app before the photo finished uploading. If you see this, you can let the person know or wait for them to open the app again and the uploading will resume automatically.

Reformatted Cluster Previews

All cluster previews under the phone icon have been reformatted to make it easier to create new clusters from photos you’ve taken recently.

Photo Loading

When opening an existing cluster, photos will load faster in the grid view.