Live data from Hacker News

Basecamp Next: UI Preview

37signals.com

21–30 of 85 posts

Re: Basecamp Next: UI Preview

#21

Earlier quoted context omitted.

When you use it you'll see why breadcrumbs are inferior. Breadcrumbs don't give you a sense of place. Breadcrumbs aren't natural. It sounds like a subtle thing, but once you use it you'll see the difference. Also, sheets have a much larger click target which makes them a lot easier and faster to use.

The only purpose of breadcrumbs is to provide a sense of place. It literally tells you where you are and how you got there. And where you can easily navigate back to. In terms of being natural, they definitely don't map to a physical analogy like your sheets do. But that's a good thing to me. edit: I agree with the click target benefit. Although I think you could do some useful things design wise with breadcrumbs to…

If you want to get semantic, breadcrumbs don't really give you a "sense" of place, they just tell you where you've come from. These sheets actually make you feel how many levels deep you are—without having to parse a string.

Re: Basecamp Next: UI Preview

#22
I love the concept (and the speed, my God!) but one thing that really bugs me is the to-do list area -- it seems as though it could use a similar treatment as the discussion area. The long line lengths plus the inconsistent comment badge locations make it look really tough to scan.

Re: Basecamp Next: UI Preview

#23
As JF said, you can't really fully judge the sheet UI idea until you see it in action for yourself. I'm one of those people who opens a new tab while using Basecamp for each item of interest. To me, these sheets could either solve that for me, or create an entirely new problem where it becomes jarring if I still prefer my old habits.

The one thing that stands out for me is how this effects the developers who work with the Basecamp API to bring the same experience to mobile, or other devices. I feel like developers who make a Basecamp app for iPhone, for example, are going to struggle trying to find a way to make these UI elements work the way they have been intended. And yes, developers will try to emulate it.

I'm reserving judgement, but for those working to bring an experience like the web-based version, I think there will be some long-game challenges. We'll see.

Re: Basecamp Next: UI Preview

#26
Nice, I like it. It's a bit like 'dependency injection', but as an interface.

Because you know that every link will open a new sheet. And it won't bring you to somewhere completely different. Clicking a link can only show you information that was inherited somehow from the sheet you're watching.

Re: Basecamp Next: UI Preview

#27
post #5

Nicely done. Very fast as well, never seen a webapp load that quick. Anyone with a bit of explanation on how this is done?

Basecamp Next's speed comes from the combination of an aggressively cacheable design and HTML 5 pushState.

Can you expand on what sort of caching you are talking about? Client side caching in the JS layer, varnish or some other http level caching, some sort of server side in the Rails app itself, etc ?

Re: Basecamp Next: UI Preview

#28

This looks like a great redesign overall. I'm still not entirely sold on how sheets are any better than breadcrumbs, other than being a different UX implementation of the same concept. But I'll adopt a wait-and-see attitude. Playing around with it is definitely needed for something like this. The one thing I will say though: every link better be "openable" in a new tab. While I love that you're helping me focus on on…

Rest assured, you can cmd-click everything!

I'm not using a Mac, you insensitive clod. :(

Re: Basecamp Next: UI Preview

#30
post #5

Nicely done. Very fast as well, never seen a webapp load that quick. Anyone with a bit of explanation on how this is done?

Basecamp Next's speed comes from the combination of an aggressively cacheable design and HTML 5 pushState.

Are you pre-caching or just caching after the first hit?
Post reply on HN