Live data from Hacker News

Show HN: Easel, web design in the browser

alpha.easel.io

41–50 of 125 posts

Re: Show HN: Easel, web design in the browser

#42
post #35

Looks a lot like getmarquee.com, only not as impressive.

Marquee is _really_ cool. But they are aimed at a different audience: non technical users. Our goal is to help streamline the design -> development process. The people making apps need a lot more flexibility than marquee provides.

Re: Show HN: Easel, web design in the browser

#44
This is cool. I like the concept. I'm hoping that someone can create a web app that reduces the need for Photoshop. You guys are off to an auspicious start. Great work!

My only comment is that the UI was confusing for me. After 60 seconds of playing around, here are a few ideas to consider (if you wish):

1) The "inspector" window on the right seemed to change a lot. I know contextual "inspectors" are standard UI practice, but as an Easel noob something about your implementation was confusing to me. (For example, why when I click one of the rounded buttons does the inspector say "Rectangle" and when I click another one it says "Element?")

2) There were a lot of icons that I couldn't understand at first glance. Icons are okay, but too many unfamiliar ones makes me confused. (i.e., What does the "lightning bolt" mean?)

3) At one point I had the menu bar at the top, the tools bar on the left (a la photoshop), the contextual inspector on the right, and another floating window open on the bottom left. It just felt overwhelming having so many controls open. (That was when I instinctually closed the Easel window.) Maybe you could anchor all of the floating inspectors into 1 group on the right, like Photoshop does.

4) The circles for the 2 colors is confusing to me. (What does the number inside of the second circle mean? Why do many other graphics app use 2 squares instead of 2 circles?)

5) Fields in the inspector weren't labeled. For example, when I select the "easel.io" logo at the top of the page, one of the fields in the inspector says "Lobster." As a font nerd I know that must the "font" field, but do you expect every user to know this? Some labels, or icons like Photoshop's font inspector, would help me understand what each field does. (http://i.imgur.com/CAY88.png)

Overall the UI just felt overwhelming. There was too much "unfamiliar" stuff and not enough "familiar stuff."

A good article is "Interfaces for Staying in the Flow" by Bederson/UMD HCI. On the first page there's Figure 1 (http://hcil2.cs.umd.edu/trs/2003-37/2003-37.pdf), which shows how flow is derived from a balance of skills and challenges revealed over time. My feedback is there were too many challenges in Easel at first. In terms of Figure 1, that would be a low x-axis value and a high y-axis value. This would indicate the UI may create "anxious" users.

If I may, I'd also recommend a little bit of "convention over configuration" for the UI. Although DHH talks about this in re: a codebase, I think the rule applies equally well for the UI. If there's a standard way that apps do something, try and stick with it. For example, canvas size isn't something you usually find directly embedded into a menu.

In short: I would suggest making the "basic features" more "familiar" looking at first; this way, people can get started making sites right away. Then, bury the "detail features" further in the UI so that if you want to do more complex tasks you have to spend more time learning the program. Benderson's article does a great job explaining all of this.

On a totally separate note, "Easel" is an excellent name for this product... and in this business, the name matters a lot.

Re: Show HN: Easel, web design in the browser

#45
You should take a look at Unbounce. While they're targeting landing pages, their page editor does this the right way IMO.

What I'd personally like to see is a JS in-browser page editor that is (a) built on top of Twitter Bootstrap (b) open source and (c) integrate-able with other sites much like rich-text editors are.

I think you could still tack on a paid service to it, but starting with the above would be gold, Jerry, gold!

Re: Show HN: Easel, web design in the browser

#46
post #38

Just a drawing tool in the browser. This doesn't do anything different than Photoshop or Omnigraffle, if the web designer is smart enough to reuse layers / components. It could be a really useful though if it had support for more than absolute-positioned, fixed-sized elements, and used the browser's layout engine instead. Today's biggest problem is that web designers use Photoshop for coming up with mockups and then…

The hard part about using the browser's layout engine is that it is limiting to the designer. We'd have to snap things into say, floating position, etc. And we'd have to know exactly what the designer was thinking when they're dragging some element around. Or they would have to know about floats, and how to use them. We think (right now) that the best way around this is some kind of constraint system, like CAD apps h…

I think what you have is great and I think you should run with what people are seeing this as "awesome" for, design prototyping. I think making this into anything that generates layout or uses the browser engine is going to be either: much harder than you think, or: will lose much of the functionality that you can allow for now via "do whatever, drag/drop, absolute positioning".

Re: Show HN: Easel, web design in the browser

#47
post #37

I'm more interested in the infinite canvas feel. How did they do that?

If you're interested in a library for that effect, there's this: http://ianli.com/infinitedrag/ I've been using it to make an infinite-canvas notetaking app and it works quite well.

Re: Show HN: Easel, web design in the browser

#49
post #36

Just a drawing tool in the browser. This doesn't do anything different than Photoshop or Omnigraffle, if the web designer is smart enough to reuse layers / components. It could be a really useful though if it had support for more than absolute-positioned, fixed-sized elements, and used the browser's layout engine instead. Today's biggest problem is that web designers use Photoshop for coming up with mockups and then…

I think this is great for prototyping ideas. Using Photoshop for web design is an approximation at best.

True, but this is just a different sort of approximation, too. Layouts where all the elements are absolutely positioned don't work in the real world, so the markup and css will have to be 60%+ rewritten and will likely not look exactly as it's laid out here.
Post reply on HN