So, as a current Basecamp customer with less than 10 projects on the go at once but with clients using those projects, I'd need to move from the current $20/month package to their new $79/month client package. Ouch!
I'm iffy about that font. Can’t tell if I'll end up loving it in a week, or if it'll drive me insane.
(I'll give the Basecamp crew the benefit of the doubt. They probably tried a lot of options.)
I reckon they didn't try any other options. Likely someone in upper management just liked the look of this typeface.
It's actually a myth that they really thoroughly test their stuff, and it grew out of the very public A/B testing on their homepage they did years ago. Recently, they've been mostly going on gut feeling, and have lost $$$ as a result.
We've been using Basecamp for years and have found less and less inspiring and useful over time as a company. The Basecamp story is amazing, and that will never change, but a few things seem apparent at this point in time.
They've doubled down on the playful, "anyone can do it" design pattern. It feels like a kids toy, now being built primarily with corporations (?) in mind. Which, might be true. That simple and subtle tech-focused pattern has slowly gone away over the years, and they’re really holding onto and cranking up this vibe, for better or worse.
The introduction of features like checkins, running reports, or at-reply notifications feels like something they’ve needed to have built for a while since other tools out there do it better. But those other tools, maybe, still do it better. And these maybe just feel bolted on?
The pricing is a bummer for small businesses, which could reflect the cross section of companies they work with now. It could have been an internal decision to cut the lower end out knowing what they stand to gain with the new structure. Either way, it’s a bit of a bummer that any client work is now an automatic $79/mo for small outfits.
These days we use Basecamp only for client communication, and not at all for internal processes or planning. It simply doesn’t scale, and doesn’t offer us what we need for our team (deep todos, tracking, scaleability, cleaner design).
It’ll be interesting to get into BC3 and poke around with how it feels for clients; and equally interesting to see if we keep it around.
Not sure if this is temporary, but they've gone for 'Passwordless' sign in process. One field for email, then they email you a link which signs you in.
Anyone seen this before? Quite a disruptive UX having to go to your email every time. Obvious benefit is you never need to remember a password I guess....
I believe Slack does something like this (but they still have a password): http://littlebigdetails.com/post/86569044847/slack-after-changing-your-password-slack-lets
Medium.com, login without password required: https://medium.com/the-story/signing-in-to-medium-by-email-aacc21134fcd#.phzba8mgz
There's a couple useful things, unfortunately all of which you would take for granted on a product that has been around for so long (e.g. drafts, mentions and actual text formatting that works). Separate "spaces" for internal VS client avoid having to prefix every thread title with "internal". Still disappointed by not being able to have nested conversations. That just turns every single thread into a stream of consciousness and makes it very hard to follow.