In the latest edition of the EE Podcast, Lea and Emily talk to EllisLab CCO James Mathias. They spent about 30 minutes talking to James about various things related to ExpressionEngine and his work at EllisLab.
James talked about how the user voting for features works and how they solicit and listen to community feedback. He even talked about some features that will be coming in the future (but you’ll have to listen to the podcast to find out). All in all, it was good insight into the work that he’s doing in his first month as the Chief Creative Officer at EllisLab.
About 15 minutes into the podcast they talked about the built-in file manger and the Assets module from Pixel & Tonic. As is fairly well-known, Assets was released to much acclaim and the native file manager in EE was (justly or unjustly, depending on your viewpoint) heavily criticized online, especially on Twitter. Some of the criticism, I think, went too far. People forgot what it is like to be civilized and constructive.
With that in mind, it was interesting to hear James talk about how EllisLab views Assets (they think it’s really nice) and their approach to the file manager now that the expectations for it have been raised by the release of Assets (this isn’t just my conjecture, James says as much in the podcast).
Here are a couple of choice quotes from James during the podcast (these happen between 15 and 18 minutes into the episode). In reference to their work on the file manager for EE 2.2, James bluntly said:
Brandon Kelly’s Assets set us back a little bit.
James acknowleged that the bar has been raised but then softened that stance a little by lobbing some criticism about the user experience (UX) of Assets:
I think the way that Assets was approached is a good UX. I think there are some inherently wrong things about it, like mimicking Finder. Finder is a great tool and great UX but it’s unfamiliar to a large portion of computer users. So it’s not necessarily the best solution.
In a response to the podcast, add-on developer Lodewijk (“Low”) Schutte very eloquently described why unfamiliar doesn’t mean bad:
Lack of familiarity does not mean bad UX. It just means unfamiliar. If you take the two extreme positions, you could make a file interface either like Windows Explorer or Mac OS X Finder. Choosing either of the two will exclude the other, so no good choice could be made, according to that stance. Trying to come up with something entirely new is very difficult indeed and will very certainly be unfamiliar to all of your users. And this idea is true for any kind of interface, not just a file manager.
Low is correct here and I would agree with him that “it’s wrong to dismiss an interface/design/UX, just because it’s unfamiliar to a certain portion of your users.”
While I did describe it as “Finder-like” in my Assets First Look video, I think the calling it flawed because it mimics parts of the Mac OS X Finder is misleading and generally incorrect. There are indeed elements of the Assets “window” that do look “Finder-ish,” but the general interaction with the folders on the left and the files on the right isn’t anything specific to OS X (just take a look at this screenshot of Windows 7 ).
I would argue (and, yes, I realize I’m being pedantic) that there’s not even a lack of familiarity with the UX in Assets. The general function of a list of folders or groupings in a left pane and a detail list of files in the right pane is a common UI and UX across both Windows and Mac (and even some flavors of GUIs on Linux).
All that being said, this is only a small part of what they discussed on the show. James had a lot more to talk about new features, some things to expect and what his job entails. Please go listen to the entire EE Podcast episode over at the podcast website.
Disclosure: We are an Official Community Partner of EllisLab and Pixel & Tonic is an advertiser on EE Insider.