How we ship code, delight customers, and build a team where engineers flourish. The Overflow blog covers all the latest work and learnings from Buffer’s engineering team.
Since iOS 8, we’ve been able to ship our Composer as an extension which allows users to share from their favorite apps that make use of UIActivityViewController. We were super excited to be able to ship the share extension to replace the old Bookmarklet code we had in prior versions of the app for a similar effect. Installing extensions on an iOS device isn’t so easy for the end user. We’ve been through a couple of iterations of guides to walk users through the process of adding the Buffer butt
Ever since Pull Down to Refresh was introduced on iOS we’ve had it implemented as the main way to keep data fresh in our iOS app. With updates going out from your queue throughout the day, the update collection view within Buffer can change pretty often. These update collection views are used for our Pending, Sent, Contributions and Content Inbox, which makes up quite a portion of the app. Since v6.0 we’ve been using AsyncDisplayKit to do all of our
As a globally distributed team at Buffer, our company retreats are a key part of our identity. We’re meeting coworkers for the first time in person, putting our heads together to shape the future of Buffer and making sure we put aside time to laugh and hang out with one another. There’s a lot going on with these retreats, and they’ve only become bigger in both scale and attendance with each one. As we recognized last year, we needed a solution to help us coordinate. That’s when we created the B
We recently shared about our transition from legacy code to clean architecture, where we’ve also begun to introduce testing to our project in the form of both Unit and Instrumentation tests. The introduction of these tests will help us to build a more stable product, boosting our confidence in the features that we ship. But why are we talking about coverage? Well, not only does this help us to measure how thoroughly tested our code is, but it’s also helping to act as a way to track our pro
The composer is the heart of our app — it enables our users to craft social media updates and schedule them to post to the social networks at custom times. It’s been part of the Buffer Android app since the very beginning. And it had reached the point where we needed to rebuild what we had in place. So grab a cup of coffee (or your beverage of choice) and let us take you on a journey through our learnings of going from legacy code to clean architecture. ☕️ A brief history of Buffer on Android
On the surface the Buffer link counting service is pretty simple. Its job is to keep track of the number of times someone has created a Buffer post with a given url embedded into it. An Example Link { "url": "https://buffer.com", "created_at": "1480431305", "update_id": "123456", "profile_id": "654321" } Behind the scenes this is what powers the Buffer Button counts. As we’ve recently shared, Buffer is moving towards a Service Oriented Architecture [https:/
As Buffer is well into its sixth year of existence, we’ve evolved a lot as an engineering team. When I joined the team in early 2014, we were six engineers, four of whom worked on our main web application and API specifically. We’re now a larger team of 27 engineers, many of us still pushing more code into a single large repo every day. Over time our workflows have evolved to try to keep the development and deployment
Each year after Apple’s World Wide Developer Conference we switch most of our focus onto a bigger update to our Buffer iOS app to build out support for the newest iOS features and changes. This year was no different, but this time we also focused a bunch of time on performance and future proofing. New version of iOS = new changes to Buffer iOS app During the time after WWDC, we typically will run through the app and adjust our minimum target to the previous iOS release. In this case, it
For the past five years, our Android project has maintained a similar package structure from when it was first created in 2012. There have been a few changes here and there, but the general structure has remained the same. When most applications are created, the class count is small. However, as the app grows and features get added, it can be easy for packages to become bloated, potentially to the point where it makes a workspace feel unorganized and difficult to navigate. This was starting to
Whenever you’re working solo on a project, chances are you’re writing in ‘your’ style – which often makes it easy to make all your code look and feel the same (but not necessarily clean). And when there’s more than one team member contributing to a project, it can be difficult to ensure that code is kept both clean and readable. Chances are that everyone has their own way of doing something, even when it comes down to things such as the way variables are named or the ordering of methods within a
Over the last year and a half, the Buffer team has tripled in size, from 25 teammates to 80. And our technology stack has ballooned as well, from a simple setup with just the basic AWS components to a much more fully utilized set of AWS and other external services. There are now so many pieces that make up the whole of the application: from how we store our data in mongo using compose, to how we run the application in an Elastic Beanstalk, to how we manage our data warehousing using Redshift. T
When AWS Lambda came out last year I was amazed. The thought never occurred to me that web development doesn’t need to be complex, instead it can be about purely accomplishing the task at hand. While they’re relatively early still, I think AWS Lambda and AWS API Gateway, are great examples of where web development is headed. If you haven’t experimented with AWS Lambda yet, I’d definitely recommend doing so. Essentially it’s a model of web development in which
At Buffer we really value transparency. Defaulting to transparency is one of our core values , and we’ve been fortunate to have been involved in some incredible discussions about transparent company cultures as a direct result. For a quick sampler, you can check out our salaries and revenue here, and you can read about the rewards and challenges of building a fully distribu
When Buffer first introduced video on our platform, it was quite clear that the feature would be a perfect fit for our mobile users. We know that videos can be an important part of a social media strategy, so making sure this rolled out to our whole audience was important to us. Fortunately, we were able to get things moving quite fast on mobile. Uploading videos to Buffer o
At Buffer, we’re a fully distributed team. We recently closed our office in San Francisco and now have a team in 12 different timezones . One of the frequent questions we receive is, “How do you work as a remote developer with so many timezones?” It’s such a great question and helps me reflect on some the unique aspects of working as a full-time developer at Buffer. It’s been such a fun journey working remotely for over t
A while back I read a pretty inspiring blog post, Serving Analytics the Right Way It’s a great read by Kevin Teh, a Data Scientist at OpenDoor. Like at Buffer, they also use Looker as an analytics platform. One part of the post I really liked was the idea of ‘Bringing data to the Team’. “all of the data is updated in real time without requiring an analyst to do any repetitive manual work. However, t
Solving the challenges we face at Buffer has always brought us to some unique places. From trying many different forms of management to recovering from a serious hacking incident, we are always learning valuable lessons along the way. Recently, we just wrapped up our 7th Buffer retreat. As our distributed team from corners all around the globe prepared to meet up in Hawaii, we thought one thing that we could improve would be a way of letting everyone on the team know where things are happening
This post is co-written by Julian. At Buffer, we’re trying hard to be mindful of diversity within our team, as well as doing as much as we can to improve diversity of people in our industry. In an effort to understand diversity across our team as well as people who apply to work at Buffer, we started started collecting diversity data via questions in an anonymous survey. Once we had some data trickling in, we starting graphing some of the data and eventually decided to write a dashboard to sha
In the year and a half that I’ve focused on hiring at Buffer, I’ve received more than 2,000 applications for engineering roles. Of those applicants, 70 have gone on to interviews, and we’ve grown from a team of 2 to 10 engineers. Learning how to hire great people is one of the toughest challenges I’ve ever faced. I’ve iterated on our process for hiring engineers and I’m glad to have the opportunity to share my lessons. Here’s my first post on our hiring process and why we no longer have the tra
Up until recently at Buffer, we had a big problem: we were drowning in data. Buffer is a data-driven company. So many of the decisions we make hinge on data that we collect and analyze. We track and measure analytics data for all kinds of things – user behavior, how our A/B experiments are running, as well as system-generated data such as API logs. As outlined in this post by Sunil, we have built a pretty robust platform for tracking and measuring data, all powered by Amazon’s SQS and MongoDB.
As our CTO Sunil has explained previously , we make all our product decisions based on metrics, meaning that we try to launch features early and measure how they impact all our metrics in order to decide which path to follow. We had the intuition that our current analysis tab in the Buffer for Business area could be tweaked a bit to make the user experience better. And last week Niel, one of our awe
It’s always a pleasure to see something grow. Especially when it starts out small. Content Suggestions at Buffer has enjoyed this interesting journey from small to growing, and in the span of eight months, it has quickly become one of our core services. We love helping people share to social media, and content suggestions started out with this idea in mind. How can we help users share? The Experiment One idea was to help people find fresh content. The first implementation started in the mid
At Buffer , every product decision we make is driven by quantitative metrics. We have always sought to be lean in our decision making, and one of the core tenants of being lean is launching experimental features early and measuring their impact. Buffer is a social media tool to help you schedule and space out your posts on social media networks like Twitter, Facebook, Google+ and Linkedin. We started in late 2010 and thanks to a keen focus on analytical data, we have now
Daily by Buffer is Buffer’s new content suggestion app available for iPhone, allowing you to add content suggestions to your Buffer each day through a simple interface. This is how it was built. While updating Buffer for iPhone for iOS 7 we launched content suggestions within our web app, which give users a variety of posts each day that can be added to their Buffer queue to help it stay topped up. Towards the end of developing the iOS 7 update a few of us developed the idea of building a simil