3 ms·
I agree with the conclusion, but I don't think the argument is presented all that well: This advice might be good for user-facing web applications. But if you’
by dasil003 16y ago
I agree with the conclusion, but I don't think the argument is presented all that well:
This advice might be good for user-facing web applications. But if you’re building XaaS, marginal features are awesome. That’s because when you’re a service, what’s marginal to one user might be core to another.
I don't think this is any less true in user-facing applications than it is in APIs. It seems to me that the main difference is that user-facing apps tend to be solving higher-level problems (eg. project management vs encoding video).
Our job is to provide powerful tools and let our users decide what options matter.
37signals also listens to users, but the total number of users per revenue dollar is higher, the scope of the usage is wider, and the cost profile (development, maintenance and cognitive overhead) tends to be different. In either case any new feature requires a cost-benefit analysis.
But APIs are different. An API with 60 options makes for longer documentation, certainly. But if the options are well-chosen and well-documented, an API with 60 options is barely more complex than an API with 20 options.
This is certainly true for options that are simply wrapping command-line options of open source components. However if you're implementing code on the back-end, these options can easily add complexity to the whole system.
It's true that a checkbox in a GUI is a much higher burden on the user than an option in service API documentation, but then again a service already starts with an order of magnitude higher usability burden than a GUI. This is of course because APIs are designed to be coded against, so the amount of user effort expended is amortized over hundreds or thousands of compute hours.
I'm sure the author understands all this, but it just didn't quite come out of the article.
- jasonjei 16y agoI think the author has a valid point. 37signals's Highrise is a CRM that we are using--and after using it for several years, we still don't have pagination. We wait for 5000+ deals to load, including lost and won deals, yet something as simple as pagination (or even an archiving feature), which have sent feature requests, still won't be implemented. So instead, we continue to wait 5-6 seconds for our deals page to load. If anything, Highrise hasn't grown in years. It's now feeling the plateau effect, and we are looking for alternatives to Highrise because it hasn't grown with us. I agree that "Less is More," but when something as simple as paginating the deals can't be implemented, it makes me wonder why we pay 37signals every month. If it's not going to improving the software and improving workflow, customers will leave to a business that understands its customers. Even Apple, while they don't exactly ask for their customers' input, know what problems their customers face every day. 37signals looks as if they are becoming out of touch with their users.
- tptacek 16y agoHighrise has been less and less valuable to me (though I'll note that just by calling it a "CRM", you're already suggesting that you're asking it to do tricks; it's not a full-featured CRM). But Basecamp has gotten more useful to me over the past year or so.
- jasonfried 16y agoThanks for using Highrise. Sorry you're having a bad experience with deals. We agree that the deals page needs pagination, but most people don't have 5000 deals. So while you're scenario is very real to you, it's not a common case. That's not to take anything away from your experience - we agree it's bad and we want to make it better - it's all just a matter of priority. We're currently working on optimizing for the common cases so we can improve the product(s) in areas everyone can enjoy. Our development log is public, if your curious about the improvements we're making every day: http://highrisehq.com/changes http://highrisehq.com/changes
- jasonjei 16y agoThanks, Jason. Appreciate the response and understanding of our frustration. We have heavily integrated our business app with Highrise, including our Quote to Invoice app with the REST API. We've built reports around the Highrise data. And we love Highrise, for the most part, since it simplifies the sales process. And it's great to track where our sales are at. But what made us love Highrise was that it was fast. And when we lose that speed, we are reminded of our experience with Salesforce. The loss in productivity with Salesforce was why we came to 37s in the first place, because you offered us real value in simplifying our sales flow. But right now, we are fiddling with speed, and we understand while you have different priorities, going through our deals nimbly is important to us.
- dinkumthinkum 16y agoYeah, I mean pagination is so basic and should have been there in the beginning. It makes everyone feel nice to be glad-handed but ... come-on, pagination?