Popular social scheduler Buffer has added the one feature you (and they) never thought they’d add: custom scheduling. That’s right, from now on, Buffer users who don’t wish to make use of Buffer’s algorithm of automatic scheduling — or buffering — can set up their own dates and times for tweets and other updates to go out.
This is not merely a revolutionary feature for users, it’s a controversial one for Buffer itself. “We attribute our rapid growth to 850,000 users and over $1.5m in annual revenue to the fact that we didn’t build Custom Scheduling for two and a half years”, says Leo Widrich, Buffer’s co-founder, but with more users come come demands, and custom scheduling was Buffer’s most requested feature. So they’ve decided to add it.
Custom scheduling in itself is not a new idea whatsoever. In fact, it’s a pretty old one, which explains Buffer’s reluctance to go there in the first place. The new feature will let you decide when your social media posts will go out, and will work whether you’re using Buffer’s browser extension or mobile apps, and will work even with image posts and retweet scheduling.
To send image updates, you can now right click any image you find on the Web and choose to “Buffer This Image”. This will let you send that image to Facebook or Twitter, and also schedule a time for the update to go out.
If you’re already a Buffer user, you probably know all about your Buffer queue. Custom scheduled posts will appear in this queue as well, but will be differentiated from “regularly buffered” updates by a grey background around the scheduled time. If you don’t want to custom schedule your posts, you can keep on using Buffer as you always have, but next time you have an update that needs to go at just the right time, remember this option.
As mundane as this feature is out of context, this is a revolutionary feature for Buffer users, and will make it even more attractive to small businesses and advanced users. Are you happy about this new feature? Or do you think Buffer should not have caved in to the pressure?
Source: Buffer blog