First of all, thanks for everyone’s thoughts on our pricing and communication strategies. We’ve been listening to everyone’s input—both here on the community and from users we hear from directly—and are collecting it to help drive the direction of the product and platform going forward. Rest assured, your feedback isn’t falling on deaf ears.
We also understand that our community has grown and we’ll need to explore better ways of tracking and following up on issues and feature requests. Our approach thus far has been “best effort” at notifying users who reported bugs of released fixes, usually through messaging directly in Intercom. That being said, we release a new update to Coda every day with tons of changes (we iterate a lot faster than most tech companies), so it wouldn’t be feasible for us to post giant changelogs with all the bugs we’ve fixed and little improvements we’ve made: no one would be able to keep up! As for sharing a roadmap, that gets to be quite tricky beyond a certain scale so it’s not something we can generally promise. (There’s a reason large product companies like Apple and Google try to keep releases to themselves until launch.)
With respect to timing, I’m sure there would always be a better time to launch pricing as we make more improvements. We get it – it’s always a shock to start paying for something you didn’t have to before, and we tried to ease that with ~1.5 month’s notice and Founder’s Credit for existing users. While we would love to have Coda completely free (and without resorting to selling user data as many companies do), as a startup with paid employees and investors who’ve entrusted us with funds, we’ve obligated to start supporting ourselves too to stay afloat. In fact, we’ve been very fortunate to be able to run Coda at no cost to our users for the past few years. And, if you’ve used Coda for 1, 2, 3, or more years, you’d see that we’ve made immense progress in the quality of the product, including addressing performance issues and bugs. Now that we’ve launched a slew of new features, we’re also taking a step back to address the backlog of these minor issues as well.
@Benn_Bennett: With regard to cross-doc, it’s currently a Team feature (again, we’re in discussion on this), but you can still build a sync using the API or Zapier integration. One thing to consider is when you’re paying $30 for Team, you get 5 free editors for free, instead of just 2 for Pro, so you’re really only paying $5/user, which we think is a competitive price.