Basecamp Next: UI Preview

Post by andrewingram » Fri, Feb 17, 2012, 10:27 AM UTC

jasonfried wrote: post #66

andrewingram wrote: post #64

I'm very pleasantly surprised by this. I've always been a bit cynical about Basecamp's success, but I think this new version is going to be a genuine game-changer. I really love the sheets idea and I'll love seeing how it works out. I'm already thinking about how I could apply the idea to e-commerce sites, hopefully the interaction isn't patented. Thinking about it now, I am wondering about a potential limitation. Sh…

Thanks Andrew. "But what if you're given a link to say an individual ticket? Do the sheets build up from that ticket as a starting point, rather than the project page, or do they reflect the hierarchy of the site? If it's the later, does that not mean that loading a deep page in the site is burdened by having to also load its parent pages?" We'll write this up in more detail later, but the basic answer is: Every link…

Post by rajuvegesna » Fri, Feb 17, 2012, 11:57 AM UTC

jasonfried wrote: post #8

bretthopper wrote: post #6

The new "sheets" UI paradigm is strange to me. Jason mentioned a few times that they wanted to provide focus by getting rid of unnecessary design elements and chrome. But with the sheets, you actually get unneeded chrome. Your main content viewport keeps getting shifted down and to the right. Why not just use breadcrumbs at the top to provide context? That way, the entire content area could be taken over whenever you…

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.

Post by hello_moto » Fri, Feb 17, 2012, 3:40 PM UTC

sstephenson wrote: post #53

hello_moto wrote: post #49

Earlier quoted context omitted.

Do you mean: 1) it's a single page app 2) you're using ERB fragments (or something) as "templates" 3) MVC fat-client Is this... more or less it?

It's not a single-page app—at least not in the traditional sense. Only in the sense that we don't need to reload assets with each page change. We are using a dash of Backbone here and there for cases where interaction speed is of utmost importance, but most of what you download over the wire is HTML.