June 05, 2008

Future Photoshop UI changes

So, what's Adobe up to interface-wise in the next versions of Creative Suite applications?

 

We've been working hard to make the interfaces of the various apps more consistent.  Because the Adobe Fireworks and Dreamweaver betas are available on Adobe Labs, you can now see some of the interface changes that will appear in the next version of Photoshop as well.  I'd like to address some of the concerns and questions I hear bubbling up.  In particular, I hope to put Mac users' minds at ease about a few things.

 

First, I want to lay my Mac bona fides on the table.  I've been using the platform since Sept. 1984, and I really sweat the little details and conventions.  (That's one reason I've raved about NetNewsWire, Panic's Transmit, and other great Mac apps.)  I use Safari instead of Firefox in part because FF's use of Windows-style buttons & form elements feels alien on my system.  So yeah, I care deeply about this stuff.

 

As the CS3 product cycle was wrapping up, Adobe's user interface designers started showing their ideas for subsequent releases.  Lots of things (tabbed documents, improved panel management, more usable workspaces, etc.) seemed like slam dunks.  On the other hand, the designs all featured a prominent "application frame"--a window containing both UI elements & documents--on both Mac and Windows.

 

I think my initial reaction can be boiled down to three letters: "WTF?"

 

"Are you telling me," I asked, "that we're going to put a huge, battleship-gray box into the background on the Mac, as it is on Windows?  Why would we do that?"

 

The designers pointed out that the app frame has a number of advantages:

 

  • It facilitates N-up (2-up, 3-up, etc.) document layouts that adapt as you adjust the interface.  Think "live window tiling"--great for comparing, compositing, etc.
  • It makes it easier to move the entire application and its contents, including from one monitor to another.
  • It prevents documents from getting obscured by panels (palettes).
  • It blocks out the contents of the desktop, minimizing visual clutter.  (A number of Mac users have requested this option for many years.  I've known quite a few people who open a small blank document, hit F to put it into full-screen mode, and then put it into the background to hide the desktop.  Willingness to live with that kind of hack demonstrates some genuine desire for a real fix.)

 

On the Mac (unlike on Windows, where an app frame has always been present), using the app frame is optional.  It's a one-click enable/disable via Window->Application Frame.  On either platform you can also float documents above the app frame, mixing them with docked windows if you'd like.  Whether on Mac or Windows, you can resize application windows by dragging any side, not just the lower-right corner.

 

I've recorded a quick demo that shows the app frame enabled & disabled; documents in & out of tabs; and some of the N-up layout options available with or without the app frame enabled:

 

After I'd used the app frame for a little while--well, what do you know?  I like it, and not because they pay me to say so.  It's easy to flip the frame on and off, but I find that I like the way it reduces distractions.  Your mileage may vary, and that's why we made using it an option.

 

The app frame has brought to light the questions of what is & is not considered "Mac-like."  This inspired me to do a little investigation into the state of Mac software.

 

It's interesting to note that showpiece Mac apps like Scrivener and NetNewsWire feature the ability to run in full-screen mode, blocking out the desktop and other distractions.  Panic's Coda Web development tool is among those combining interface and content into a single window.

 

What about Apple's own applications, as they would be presumably be the definition of Mac-like, right?  I noticed a couple of things:

 

  • The pro video apps (Final Cut Pro, Motion, Color, DVD Studio Pro) configure their windows/panels to take over one's screen completely.
  • Aperture and iPhoto put all the UI into a window & optionally take over the screen in a dedicated full-screen mode.
  • The iLife and iWork apps (Keynote, Pages, iWeb) all feature a UI approach that marries together content & interface in a single window.  (For reference, here's a little gallery of all these apps.)

 

And so, I'd argue, putting UI + content into a single, manageable window (as the CS4 app frame does) isn't "un-Mac-like" at all.  Despite my initial freak-out (the one being echoed by others when seeing an application frame in Fireworks), you could argue that the application frame makes Adobe tools more Mac-like--if "Mac-like" means "Apple application-like."

 

I've also heard comments about the new Adobe apps' custom interface elements and their ability to resize windows by dragging them from any side, not just from the lower-right corner (as required in most Mac apps).  On Daring Fireball John Gruber characterized this capability as "just like in Windows."  Digging a bit more, I fired up Final Cut Pro 6.0 and made some discoveries:

 

  • You can drag-resize panels and document windows from any side, not just from the lower-right corner.
  • The close/minimize/zoom buttons are extremely small; they always appear monochrome (instead of respecting the OS appearance preference of Blue vs. Graphite); and they don't show a dot in the close box of files with unsaved changes.
  • The UI is full of unique elements that don't appear elsewhere in the OS--e.g., custom scrollbars sitting next to OS-standard ones.

 

I then took a look at Motion.  Again scrollbars are custom (though different from Final Cut's), remaining monochrome regardless of OS appearance preference.  Application windows can be resized individually and together from any side, though with more apparent limitations than in FCP.  Things are similar in DVD Studio Pro, where you can resize what amounts to an app frame from any side.

 

Instead of "just like in Windows," "just like in Apple's own apps" might be a better way to put it.  In any case, whether the convention exists elsewhere is beside the point.  The point is, Is it useful?

 

As I wrote earlier, I believe Adobe teams need to work hard to make their products feel like polished, native citizens on each OS.  Deviation from the norm for its own sake is unhelpful.  Having said that, OS conventions should support innovation, not stifle it.  If we can improve functionality (e.g. enabling more flexible document resizing) without imposing any burden (extra UI chrome, etc.), why shouldn't we?

 

Our job is about functionality, not ideology.  Whatever works best, wins.  Obviously the Apple development teams feel free to depart from strict adherence to the baseline OS when they feel that doing so would benefit their customers.  I'd argue that Adobe teams should have similar latitude.


Now, at the end of the day, will we ship with the application frame visible by default on the Mac?  I don't know; maybe not.  We want people to feel invited--not forced--to use the new functionality.  No matter how much I write here--and thanks for reading this far--some Mac users are going to have the "WTF" reaction to the application frame.  Hopefully they, and you, will keep an open mind until you've gotten to try it out.  I think you'll find--as I did--that there's a lot to like.

Posted by John Nack at 04:42 PM on June 05, 2008

Comments

John Nack — 04:43 PM on June 05, 2008

Addendum: Specific concerns I've heard about the new UI:


  • The design is too gray!  Where's the color?  Well, do you want to look at Adobe's design or at yours?  Seriously.  There's a saying attributed to Alan Cooper: "No matter how cool your interface, it would be better if there were less of it."  Not polluting users' color perception is a serious issue, and if I'm not mistaken, the "Graphite" (monochrome) option for OS X came about in large part due to pressure from Adobe UI designers concerned about gratuitous and persistent use of color in the UI.  The close/minimize/zoom buttons turn color on rollover.

  • The application bar consumes too much space.  On Windows this seems to be less of an issue, as on wider monitors the application menus & the app bar content reflow to occupy one line if possible.  On the Mac, where menus are always at the top of the screen (as opposed to inside the document window), you can turn off the application bar if you'd like. You can also make it float, in which case it takes up less space horizontally.

  • The application frame is hard to resize.  This area has been buggy during development, so I wouldn't be surprised to hear that what's in the Fireworks beta isn't functioning as designed.


Miscellaneous other UI notes, as long as we're on the subject:
  • Panel (palette) management is improved in a number of ways.  Panels can float in minimized, iconic form (individually or in groups), offering much more flexibility than you'd get with the old Photoshop palette well.  More than one docked iconic panel can be open at once, and auto-reveal of panels is optional.

  • The number of screen modes in Photoshop has been set back to three (instead of four, as in CS3).  The application frame takes the place of the "maximized" mode introduced last time.

  • Setting the background color in screen modes will be much more discoverable.

brice — 05:06 PM on June 05, 2008

consistency,
so does that mean the various applications in the suite will behave more in the same way?

[Yes, that's the goal. It's an evolutionary process. --J.]

ie in photoshop you can click and hold the word "opacity" and adjust its value, whereas in Illustrator you have to use the the drop-down box and adjust the slider that way.

[We intend to get onto a single, best-of-breed set of widgets that enable things like the "scrubby sliders" you mention. They're on the roadmap, but not for the upcoming release. (We're peeling the onion, though.)

btw, application frame FTW, good job on the UI
Also will Mac users be able to switch the blend modes / fonts using the mouse wheel, as on Windows? (or is that a limitation of the OS)

[I'm not sure. Historically it hasn't been possible to put focus on a Mac control, then move through it via the keyboard (as you can do on Windows). In Safari and maybe other apps, however, I see that you can highlight a control, then navigate via the keyboard. I'm not sure when that support was introduced, or in what context. --J.]

Klaus Nordby — 05:17 PM on June 05, 2008

I'm on Windows, so the Mac concerns do not concern me (though I always thought the absence of an app frame on the Mac to be very much in the platform's disfavor). But I've now briefly tested the CS4 versions of DW and FW and I'D LIKE TO KNOW WHO THE HELL THOUGHT THAT ALL-CAPS PANEL NAMES WAS A GOOD UI DESIGN IDEA? Actually, I don't want to know what weird mind committed that design crime at all -- I JUST DON'T WANT ANYTHING IN ANY UI TO SHOUT AT ME. Please, please, PLEASE drop those horrid all-caps in the release versions of the CS4 apps! They're an abomination -- a LOUD abomination.

[As long as I'm being candid today, I'll admit I had a similar reaction, though I quickly got used to them. I did insist that the user research team look into whether the all caps treatment compromises readability. In user testing they found that it didn't. --J.]

meekish — 05:23 PM on June 05, 2008

I've always been annoyed by the fact that app windows in OS X can only be resized from the bottom-right corner. I think deviating from the Apple convention here is a definite win.

I also think that the larger application bar looks hot. The whole overhaul looks hot. The Adobe UI design team is doing a splendid job.

[Cool, glad to hear it. --J.]

Steven Garrity — 05:26 PM on June 05, 2008

Will documents inside the frame be considered stand-alone windows for window-management features like Expose?

[No, although we'd like to make that work. Last I heard we'd inquired with Apple & that's not something Exposé supports. (You can't use it to display/shuffle the contents of tabs in Safari, either.) If the capability becomes available, we'll work on supporting it. --J.]

Gio — 05:31 PM on June 05, 2008

Love the new UI!

emgee — 05:34 PM on June 05, 2008

Thanks for the heads up and rational.

I think someone out to create a pool, which would be wordcount of Gruber's reply to this piece. I've got $5 on 6 words, and $5 on 8,412 words.

[Heh; I think he's pretty busy with WWDC coming up, but I suppose we'll see. --J.]

Trevor Kay — 05:50 PM on June 05, 2008

Please bring back the dot in the close button for unsaved documents. Mac users are used to this behaviour and an * on a tab and the title bar isn't clear enough. Both Safari and Final Cut Pro have reasons for not using it (In Safari you aren't editing the HTML document you have loaded and in Final Cut Pro the window controls are way too small for it to be noticeable).

[We're looking into the issue for floating docs. Documents in the app frame don't have the those controls; hence the asterisk to indicate document "dirtiness." --J.]

Andre Da Costa — 05:50 PM on June 05, 2008

John, I think I get the subliminal message behind the animal and beetle sketches. ;)

[Oh yeah? You're way ahead of me, then. ;-) I just got sick of using the standard demo assets and stumbled across some of my old sketches from college. --J.]

Kristian — 05:56 PM on June 05, 2008

I believe you can tab exposé in the Shiira browser.

http://shiira.jp/screenshot/en.php#tabExpose
http://shiira.jp/English/res/mov_tabExposeL.mov


Maybe this'll help you enable tab exposé in CS4?

dd — 06:11 PM on June 05, 2008

biggest thanks for adobe and photoshop team for making all these ui changes as _options_. and please don't block or remove old-way photoshop ui functions in future versions.

i really try to be open minded and promise to stay in new paradigm at least for a first day, but somehow i'm almost sure that separate windows is much more intuitive workflow for me (i really think that macosx is far more windows OS that ms windows :) and the application bar is very alien-looking (thanks so much it's possible to hide it too).

also - i really hope it's some kind of hacked skin you're using for macosx widgets since flat-big circles for window close-minimize-maximize are horrible. please- at least make some option to be able to have default standard macosx controls. what's the point except for visual effect to change these? (ok, i admit - reinventing conventions to add features should be considered, but what's with these buttons?).

thanks!

dd — 06:18 PM on June 05, 2008

p.s. as for comparing finalcut studio window' closing widgets- i'd point it's a big difference when non standard control is used to indicate closing a panel (either in final cut or in photoshop - for panels) or when closing real window/document (which photoshop has for an open file) however neither finalcut nor motion has single separate window for currently open document like photoshop, word, textmate, etc does..

Klaus Nordby — 06:28 PM on June 05, 2008

Thanks for your candor, John. You wrote: "In user testing they found that it didn't." I don't buy that at all. Aside from the ghastly SHOUTING effect, it's been universally know for hundreds of years among typographers that capitals reduces legibility and slows down the reading pace. I'd like to know what "reasons" the UI folks have given you, in order to FOIST THIS SENSELESS SHOUTING UPON US? I find it so bad -- so offensive, so inconsiderate -- that this UI issue alone will rather make me think twice about upgrading to CS4. And I'm usually a upgrade-fiend. It's simply unbelievable that such an UI design howler can be committed by Adobe.

Jonathan — 07:02 PM on June 05, 2008

Apple-like =/= Apple

I can't think of any third party applications that have successfully pulled off an alternate "window skin" and I honestly don't feel like this interface will work well. Apple's reasoning behind these looks isn't for the way it looks, it's so that the UI isn't a distraction. That's why the buttons are smaller (note how CS4's close, minimize and resize buttons are the same size and contrast more than the Apple defaults). Your intentions are good, but the implementation is bad. Your window buttons look out of place and draw more attention to the differing UI.

The other issue is that when Apple creates their custom UI for an application, it's familiar. Final Cut Pro's UI is a blend of what we remember from Classic and an Aqua interface. Your UI does neither. Instead of trying to reinvent the UI, you should try to come up with something that's familiar to the user. It's far less distracting that way.

Anauel — 07:05 PM on June 05, 2008

It is comforting to know that there's someone that's thinking about all these details. Ps has always been a great application, just saying I didn't know about this blog until recently (thanks to Mr. Gruber).

Daniel Lizio-Katzen — 07:09 PM on June 05, 2008

My one request, is please, PLEASE, don't change the keyboard shortcuts. Just the fact that ctrl-click doesn't work the same in CS3 as it did in previous versions is frustrating, especially for someone who has been using PS since version 2.

henry Maddocks — 07:11 PM on June 05, 2008

Why don't you just admit you've run out of feature ideas and call PS finished?

Trevor Kay — 07:12 PM on June 05, 2008

While we are asking for features :P Can someone at Adobe please enable drag and drop support from anywhere to document. I'd love to be able to just drag a file from the Desktop or an image from Safari, etc into a Photoshop document and have it become a new layer.

George Wiel — 07:14 PM on June 05, 2008

I know this post is about Phtoshop but while were on sweating the little details and Mac UI conventions at Adobe: how about implementing the standard command-period key command to dismiss dialog boxes in Fireworks. Fireworks CS 3 has the excuse of being a prettied up Macromedia product. But FW CS4 has the same UI defect in the "Image Size" and "Canvas Size" dialog boxes. I use these about every 90 seconds so a key command (a la PS) for those dialog boxes would also be welcome.

Jon — 07:22 PM on June 05, 2008

I love the idea of an app frame, but always hate it when it comes time to actually get work done.

Also, if it's not too diffacult, please allow the resizing from only the lower right. I hate that when I go to move apps on windows, I end up resizing the damn windows.

Radu Dutzan — 07:23 PM on June 05, 2008

Great. You (and the video) actually made me change my mind on The Frame.

If I could only ask one thing of the visual appearance, it would be that in areas where it'd be appropiate, you add some partial (and optional) translucency, so the desktop picture can be seen. But even without that, I'm liking the new UI very much.

msr — 07:24 PM on June 05, 2008

I will never pay Adobe a dime for the sh*t that is the Photoshop interface you're planning to come out with. "Apple does it!" finger pointing is not an excuse to put out a horrible interface. First off, Apple does it because they are APPLE. Did Adobe create the Aqua interface? Nope. Apple can do what they want because they obviously know what they are doing. Adobe doesn't. And you prove that every time you try to make a custom interface. Not only do you do a terrible job code-wise (I've heard tons of complaints about Dreamweaver or Fireworks CS3) but it looks like crap. Have fun losing market share. You have more competition now than ever.

Super Nintendo Chalmers — 07:33 PM on June 05, 2008

Here's a wacky idea -- Command-, for preferences.

Bryan — 07:46 PM on June 05, 2008

Basing your design decisions on Apple's pro apps is a big mistake.

For example, Final Cut and Final Cut Pro are too stupid to order numbers correctly. Name movie clips with numbers 1-10 and then add an 11th clip. It puts it right after the first clip so that the order goes: 1, 11, 2, 3, ...

Most of these apps were bought, not originally developed by Apple. Therefore, there's lots of legacy code and decisions that's absolutely horrible.

I cast my vote for NO application frame. It's one of the absolute worst things about using Windows.

Eric — 07:47 PM on June 05, 2008

While I think it's great that the suite's UI is finally being so thoughtfully revised, your claim that the application frame will be optional worries me a bit. The LAST thing most of these apps need are more options -- the most Mac-like move of all would be to fine-tune ONE interface to relative perfection and make it the standard.

Rob Marquardt — 07:51 PM on June 05, 2008

It really seems like a solution in search of a problem on the Mac side of things. If apps in the background are a distraction, I can throw Photoshop into its own space and switch between them (and am still able to use Expose).

Most of the time, I'm comparing what I'm working on in PS with images open in those other apps (Illustrator, Preview, etc). It's fortunate that the app frame can be turned off.

Eric Price — 07:52 PM on June 05, 2008

Oh, and P.S. -- you will make the day of thousands of designers if you get your engineers to enable copying and pasting in Photoshop's hexadecimal color text field like all the other suite apps. SO basic, and it's been broken for SO long.

Charles — 07:53 PM on June 05, 2008

I once asked one of the Apple developers about the difference in UI on apps like Motion, I asked if they could "Aquafy" the standard UI pieces like OpenSave dialogs that operate separately from the full screen gray interface. They insisted that there was a second set of "advanced" UI guidelines for pro apps like Motion. I don't buy it, those apps look more like Windows-centric apps like Combustion, and of course Motion started on another platform before being ported. Sometimes a bad UI is just a bad port.

But what concerns me more about the Photoshop UI is items that are neither Mac-like nor Windows-like, but are entirely Adobe inventions. I spend an inordinate amount of tech support time explaining novel UI widgets like fly-out menus, because they're unique to Adobe apps and unfamiliar. Mac people say they're un-Maclike, Windows people say they're un-Windowslike. I wouldn't object so much if they were totally brilliant unique UI inventions (like the Maya hotbox) but these PS widgets seem unique just for the sake of uniqueness. I see that as an obstacle to use, not an enhancement.

m — 07:53 PM on June 05, 2008

I want my apps to 'fit in' to my platform of choice, not subvert it. Making your apps platform neutral doesn't enhance my user experience.

I think a big part of the concern is the idea that Adobe is trying to foist their platform on top of our platform of choice, neutralizing rather than enhancing what we feel are the advantages of our platform.

On the Mac, the fact that I can't toggle the front window in PS using cmd-` drives me nuts. The fact that I can't hide PS altogether using cmd-H drives me nuts. And so on. I feel like I am constantly fighting a company that wants to pretend they own the space their apps play in. You don't. I use several apps, not just Adobe apps, and I hate that I have to remember 'oh, I'm using and Adobe app now'. It's just a bad experience.

As a well respected UI guy once advised me, "standard is better than better".

Jin Kim — 07:59 PM on June 05, 2008

I've been eagerly testing out the Fireworks and Dreamweaver betas. Much kudos to Adobe for making them available and allowing open discussion/feedback here and on the beta forums.

I am still skeptical of one of the UI direction that you've discussed in the past post (re: integration of Flash in Photoshop UI) and will reserve my final judgement until I see the final release.

Mac applications, as you have mentioned, have generally been heading towards application frame or single window paradigm and I think that there are many advantages to the approach. The previous attempts to bring those advantages to applications by having various windows and palettes snap to each other did not quite work (including in Apple's own pro applications) and I'm glad to see that Adobe has just gone for the real thing instead.

What I don't understand though is when you've departed from established UI convention of the platform. For example, what's with putting tools into the title bar? You already have a toolbar in your applications. Why not use it instead of creating yet another toolbar inside the title bar? On Windows where it is the convention of the platform to be able to place the application/window menu bar next to tool bars it makes sense. On Mac, though?

To me the basic conventions of the platform that should be respected. I don't think the new functionalities placed in the title bar warrants a break not b/c the conventional way is "the only way to do it" but because they break user's mental model as he/she moves from one application to next AND there's a clear and conventional way to accomplish the same functionality.

Roger — 08:11 PM on June 05, 2008

Ok, a couple of things. 1) Your YouTube video shows … I guess the next version of Photoshop? So when’s the public beta? 2) All UI changes are fine as long as they are options.

As mature as Photoshop is, if it were up to me I’d make any UI changes optional for the user. I’d make any upgrades to tools optional. I would not replace a tool with a new one, I’d just add the new one.

Photoshop is like a Swiss Army knife. It amazes me how many approaches people can come up with to solve a problem with Photoshop. Changes that don’t grasp that users may be solving a problem every day based on the way the UI appears in say CS2 or how a tool functions in CS3 will aggravate many. Overall I believe Adobe has played fair with most of this (although I remember the changes to the layer palette a couple of versions ago frustrated me for weeks). So just be careful what you do with that magic wand too, there’s some guy out there using it to make Leonard De Vinci master pieces.

thicksab — 08:11 PM on June 05, 2008

Isn't a bit strange to use Coda as an example, when Coda actually uses standard controls and windows, and this bizarre frame doesn't?

Justin Bell — 08:19 PM on June 05, 2008

Here's my problem with all this apparent consistency, including the element table style icons: Not all of us use every piece of software in your suits. I know it all makes sense to you guys when you look at your big array of apps, but many of use only use one or two of your apps most of the time, so all this is lost on us and just comes across as a bit arrogant. It's like you're creating your own mini universe. As for Apple breaking there own interface guidelines -- why is that a good excuse for you guys to do the same? I don't mean to say that your new UI ideas are bad, but I think you need to keep some of these points in mind and stop letting your marketing department have such a big say in things.

jimhere — 08:25 PM on June 05, 2008

I've used the Fireworks (and Dreamweaver) beta, and I don't feel too bad about the UI (as I did for CS3). The option to release the so-called application frame is all one needs.

But what's that double row of tools under the main menu bar? In your screenshot there's the menu (File Edit etc), then some sort of new, I don't know, other bar (with n-up, I guess), then the familiar Options Bar. I suppose that's just an extra 32 pixels, but couldn't all them controls have been tucked somewhere else (there's so much unused space to it's right)? Of course, the old 'palette well' would fit nicely there so we wouldn't have to use any of the right side for panels. And I'm a little worried about what you guys consider "ESSENTIALS' at upper right. That is too stylized.

For the good stuff, the silly CS3 panel frames are now nicely re-drawn with squared tabs and groovy upper-left close buttons in palette-mode (no baffling x's). I like the gray everywhere (not sure why some want colored icons). Most important, it does not look like the over-stylized Elements and Lightroom. This still feels Pro (to me).

So the lesson to you is, release a public beta of Fireworks first so people get used to it before out precious Photoshop is changed.

Peter Witham — 08:58 PM on June 05, 2008

Personally...I really like the new interface in DW and FW CS4. And I can see the new Photoshop working for me just fine!

The one thing that really stood out for me on the DW BETA is you truly do see the document more than an interface and that's really the way anyone should be thinking in any application (just don't do anything as dire as the Vista blur it because we can transpareny window chrome crap).

I am actually looking forward to the new CS4 suite based on what I've seen and read, and to be up front I was way under impressed with CS3 so you must be doing something right as far as I'm concerned.

Regards,
Peter Witham

A. Dias — 09:04 PM on June 05, 2008

Kudos for the app frame and the ability to lay various images in the frame in many different ways. Way to go!

Tristan Carr — 09:05 PM on June 05, 2008

I have been hoping Adobe would make this change. It definitely feels more mac-like to me.

John North — 09:07 PM on June 05, 2008

I'm sorry, but most of those examples of suck. Scrivener and NetNewsWire? Please, not even remotely similar. Aperture, iPhoto? Both are library-centric, not document-centric, unlike Photoshop. Final Cut Studio? The workflow is completely and utterly different.

Just stand up for the decision instead of pretending that it is adhering to common behavior. It's new and weird to long-time users--that'd be fine if you didn't pretend it wasn't. Don't make it an issue, and for the love of God don't make it the default.

In particular, the line saying "just like Apple's own apps" is a total weasel cop-out. Adobe established the conventions of how Photoshop works, not Apple.

Steven — 09:12 PM on June 05, 2008

It would be great if you could have several groups of guides and name them.

Particularly useful for webdesign where you have more than one template per website.

A. Dias — 09:14 PM on June 05, 2008

Clearly the complainers re app frame are not photographers. Photographers want a neutral background, not the random colored/patterned desktop, populated with a myriad of icons scattered there in any day's work. The CS3 solution to set a gray background is limiting as it does not allow tiling, overlapping, etc. Again, well done!

JK — 09:37 PM on June 05, 2008

For an EXCELLENT example of application frame with complete customization...one of the best UIs I've ever used...go download a demo and check it out...

Modo.

http://www.luxology.com

[Heh--you know, I've liked modo when I've used it, but it's a great example of how it's impossible to make everyone happy: in this same thread someone else refers to their UI as "just a freak-show mess." So it goes. --J.]

Mike Howe — 09:58 PM on June 05, 2008

Thanks for caring about the Mac UI John. Its all looking good IMHO apart from the inclusion of UI elements/tools/essentials in the title bar of the app frame - WTF!

Also I see that the scroll bars are still using the aqua blue so what's the justification for the 'graying' of the red/orange/green window controls?

[I agree that the distinction there is a little funky, and we've asked the UI and engineering folks to reexamine the issue. When they started, I don't believe there was a way to ask the OS about the state of the Blue/Graphite setting (though it's possible I misheard something); hence they went with monochrome all the time. My belief is that those controls should respect the user-defined preference, provided that's something we can read. --J.]

Rohan — 10:05 PM on June 05, 2008
My one request, is please, PLEASE, don't change the keyboard shortcuts.

A recently saw a post somewhere that had a really good suggestion... When faced with old shortcuts that don't follow the platform standards, the first time the user uses a shortcut, put up a dialog and ask them if they were expecting the old shortcut, or the standard platform one.

Existing users used to old shortcuts are happy. New users who expect the software to do the right thing are happy.

Phil Brown — 10:07 PM on June 05, 2008

Wow...I mean, just wow. Of course, I'm referring to some of the responses, not to what John posted.

OPTIONAL, added functionality and people are complaining?

John didn't justify the changes by saying "we're following Apple's lead in deviating from the UI" he said that changes have been made that Adobe feels are useful, functional and improvements and then pointed out that Adobe isn't the only company to do this (because as has already been seen, anything that doesn't appear to be 100% Apple or come from Apple draws derision and criticism from some corners of the net no matter what).

Many apps, including from Apple, deviate from the UI where it's considered appropriate. That's all, and that's fine.

People don't like change - DOS is great some of the time, but how many of us want to lose the option of a GUI? Me, I enjoy being able to open a shell and use that when the GUI is in the way. So having options is great.

Far too many people run on the basis of "I don't like it, no one should!".

Mark Thomas — 10:30 PM on June 05, 2008

Let me just say that as a GUI purist — that is, someone who prefers apps to follow OS guidelines as much as possible — I actually prefer the new CS4 look to the utter weirdness that is Lightroom. Still, I'd prefer it if Adobe would focus more on improving core functionality than relatively superficial GUI changes. For instance, Photoshop should always operate in 32-bits per channel mode and auto-downsample when saving to JPEG (e.g. don't throw up an alert). I'd rather have full "high color" (or whatever you want to call it) support than a non-standard GUI. It's starting to look like Adobe is, by attempting to unify the CS4 GUIs, actually making the whole situation far more complex than it needs to be. Luxology's modo springs to mind. Rather than solving the problem of a complex GUI, Luxology increased modo's complexity ten fold by making the whole thing customizable and schizo. Now it's just a freak-show mess. So please be careful. The simplest solution tends to be the right one. In other words, the simplest, most logical thing to do would be to conform the CS4 apps to follow the GUI guidelines of each host OS. I get the feeling that this whole unified GUI approach is being done to make it so that only one GUI has to be designed and supported rather than two (or three if Linux ever figures into the game in a meaningful way). To me, that approach signals some disrespect for the OS. And maybe there's reason for that. We all know — Apple included — that the future of apps is the web, so maybe Adobe's taking the right approach by pretending the OS doesn't exist anymore, thus abstracting its GUIs from what lies beneath, in other words. I'm curious to know what the real thinking behind the new GUI is.

Andrew Knott — 10:48 PM on June 05, 2008

I care less about the look of UI elements. I care about performance. The UI performance (window resizing, refresh etc) in all the CS3 apps is awful. I'd also like to see your apps work with spaces. Please?

[Apple has fixed a bunch of issues with Spaces in 10.5.3, but there's more work to be done. --J.]

Gio — 11:00 PM on June 05, 2008

The application frame change is great. Using both platforms, I've always loathed the desktop showing through and resizing is limited to dragging the bottom right corner. Do what's right for Photoshop and its users - not what feels "Mac like". In any case, don't agonize too much - everyone knows Adobe favours the Mac and treats Windows as an afterthought.

stu — 11:08 PM on June 05, 2008

Just to let you know, the video seems to be down.

Nic Barajas — 11:18 PM on June 05, 2008

Here's one request, though: Please respect the double-click preference for minimizing of apps. I used the Fireworks CS4 beta and was unhappy when the application minimized with an errant double-click.

John_B — 11:26 PM on June 05, 2008

That Adobe doesn't "get" that ALL CAPS is the worst faux pas a design oriented company could possibly make... Wow! Too frickin' amazing!

[Ever looked at iTunes? --J.]

Honestly, before you go live with that as a "feature", you might want to check with someone on your InDesign team (or someone who used to work on PageMaker if anyone is left).

R Hunt — 11:28 PM on June 05, 2008

On the subject of PS UI... the inability to page the selection of an Adobe palette list menu with the arrow keys is an annoying behavior of the app. For a while I thought this was a standard behavior on the Mac platform, but after some short research (check Safari) realized that its not. It's ONE MORE example (many others are listed above) of Adobe breaking OS standards seemingly just for the hell of it.

[That has nothing to do with it. Rather, it's a question of focus. The arrows apply to selected objects on your document. Would you want to try to move an object up a couple of pixels, only to end up changing layers or scrolling a list? I seriously doubt it. --J.]

A lot of the rational for these decisions seems to be "at first I thought it was weird too, but then I just got used to it". Is that seriously how your design process works? Human beings are capable of "just getting used to" all sort of horrible situations... that doesn't make it good.

I am of the philosophy that standards should be upheld. Where there's no clear standard, and you have a really clever solution to the problem, then by all means, have at it, but otherwise stop mucking things up.

Tarwin Stroh-Spijer — 11:32 PM on June 05, 2008

This makes me wonderfully happy. It almost makes me comfortable enough to move over to OSX (from Windows). Thank you, thank you, thank you!

Alex Dahl — 11:36 PM on June 05, 2008

As always, thanks for the info. I do like the concept app frame, but Adobe doesn't seem to be taking the best approach. First off, pointing to lousy design in Apple's pro apps isn't justification for Adobe's lousy design.

[Just for the record, I didn't say that anything about Apple's app designs is lousy--just different (and in some ways more capable) than what is supported elsewhere in the OS. --J.]

Additionally, I found several details that reveal how the new UI hasn't been thought through.

You mention that color in the UI is distracting. True, which is why I use graphite—don't replace standard graphics that already have solved the problem. I see that CS4's drop-down menus and scroll bars still use system graphics. Does Adobe feel color window controls are a problem, but color scroll bars are not? The amazing thing is that right next to the custom gray window controls, a bright blue app icon has been added.

[There's an option to display that icon in monochrome mode, as there always has been. --J.]

There's no need for ugly custom window controls, and no need for distracting icons in the app frame.

In a document frame that does not have focus, there is no indication of what the active tab is. See http://blogs.adobe.com/jnack/images/PS_app_frame_floating.jpg — it is clear that Beetle.JPG in the front window is active. But in the app frame, is Untitled-2, hairy-coo.jpg, or Untitled-1 the active tab? There's no way to tell.

[We're still working on that area. --J.]

A tiny asterisk as the only indication of unsaved changes is incredibly poor design. You imply in a comment above that this is the only possibility for the app frame. But in your post, you cited the success of Coda's one-window workflow. How about you look at how Panic handled this issue in Coda?

[Will do. --J.]

I will not believe the argument that large UI changes like the app frame have been thoughtfully considered while smaller but important details go unaddressed.

[I know that makes intuitive sense, but it's not how the code is written. It's not a zero-sum game, where the same person who could make one change (e.g. enabling deletion of multiple selected channels--which we'll enable, btw) could make another. --J.]

I encourage Adobe to forge new UI ground, but to do so in a way that actually works. Coda is a fantastic study: it has many unique UI features, but is still well put-together and doesn't break conventions. Photoshop matches the first description, but not the second or third.

LKM — 11:44 PM on June 05, 2008

John, you will find that nobody complains about the UI for Lightroom; that's because for non-document-centric applications, single-window UIs are okay. For apps like Photoshop though, not so much. Having said that, I'm happy to have the option to run the app in a single-window UI; I'm sure it could come in handy at some point.

Still, it's ovious to me that the Windows version of Photoshop hurts the Mac version due to your perceived need to be consistent between the two. I think consistency with the OS is more important than consistency between different OS versions of the application; for a reasonably good example of this, see Microsoft Word.

James Duncan Davidson — 11:59 PM on June 05, 2008

I'll hold judgement on the fine details of the UI shown here as, after all, it's a non-released interface and as you guys get time on it, you'll dial it in as needed. But, as I was going back and forth between Lightroom and Photoshop earlier tonight, the visual shift between the single-window Lightroom and the multi-window with toolbars and other stuff interface of Photoshop was really smacking me in the face for some reason. I can't place my fingers on the fine details, but Lightroom felt modern, Photoshop felt, um, totally old school. Even though Lightroom breaks so many Apple UI conventions, it still feels a lot more modern, Mac-like, and up to date.

So, for whatever that's worth, I'm glad you guys are putting in time to modernize up. Kick the tires. Be brave.

ray — 12:04 AM on June 06, 2008

Occasionally I use Photoshop under Windows, and having everything trapped inside an "application frame" drives me bonkers. I often want to place reference images and working files and such on a second monitor, and the application frame gets in the way.

Secondly, if you insist on rolling your own UI widgetry, please, please, please tune it for performance. Apps that bypass the OS's offerings in favor of their own custom windows and controls never feel quite as snappy or responsive. (Lightroom, I'm looking at you.) On cutting edge beast machines, resizing windows should be absolutely instantaneous and fluid. There should be zero perceptible lag on basic UI interaction.

thorsten wulff — 12:06 AM on June 06, 2008

A CS4 app frame is okay with me, being your mac and usability geek as they come… I used a 50% grey background forever on my macs for exactly this reason. I even stopped using dropshadows in PS because OSX every window had one. My only gripe with the CS3 interface were the closeness of the little double triangle in the palettes upper right corner to the options expansion below, I never click the right one ;))

Philip Littlewood — 12:09 AM on June 06, 2008

I am 100% in favour of the App Frame. I hate the fact that the desktop background can be seen. Lets be honest the point is mute because Adobe are giving the option to disable it if you don't like it.

Also fantastic for enabling dragging from all sides of windows.

Bjoern — 12:21 AM on June 06, 2008

I generally like that Adobe is actively trying to develop and enhance the interface of its CS applications. I think that there are still lots of issues with Photoshops interface, most of them coupled with functions (e.g. Layer Effects - extremely useful, but could be better still if could add the same layer effect several times to the same layer, multiple borders etc., workarounds exist, though).

As a User Interface Designer I don't think using an application frame is a bad thing. Lots of good things can come of it. I generally like what I see. I definitely have proposed similar concept in my designs, too.

One thing, though, I really would like: I always, always work in the "full screen mode with menu bar". The thing I really like about that mode is that you don't have any scrollbars (actually, they appear on the next screen, which is not nice, but not too bad either - cheaters! ;)) Who uses scrollbars to pan an image anyway? I always pan using SPACE... So it would be nice, if the scrollbars could be optional.

Bjoern — 12:25 AM on June 06, 2008

one more thing: instead of wasting so much space with the window title bar for your functions I think you could easily integrate these functions into the toolbar (maybe to the right or something like that...)
That would save some space...

Guntis — 12:39 AM on June 06, 2008

1) Please use the default standard Mac OS X window controls (Close/Minimize/Zoom). These large matte gray dots look utterly ugly. I can't understand how the company who makes apps for the designers can come up with something so ugly. Apple have put at least some gloss on theirs. But Apple's video Pro apps really are not the best example to follow. Better take a look at Aperture or Logic. But remember that these apps are primarily one-window (one-document) apps. Logic prefers to work with one project at a time (always asks to close previous project), Aperture is meant to use only one image library at a time. Photoshop isn't. So better use the default OS X controls. I can always enable Graphite theme if I want gray buttons. Please don't ruin UI.
2) It's good that application bar is an option. The first thing I'll do on CS4 will be to disable it and forget that it ever existed. Photoshop CS3 had quite good interface, and I really don't like the latest development trends in CS4. Photoshop CS3 interface could be polished in some parts, but it was close to perfect. I really don't like that I'm forced on Mac to click Close button on the right side of the palette tab to close it - it's Windows style. Why not on the left using the same tab close widget as in Safari? It's about consistent UI, not mixture of Mac and Windows.
3) Why do all Adobe apps use non-standard shortcut(s) for application preferences? Please, please, please - Command+, for Preferences.

maurice — 01:00 AM on June 06, 2008

Hey,

what I would like to see: scrollable input boxes! (like in macrabbit's CSS-edit). Scrolling changes the value in the input box. Very nice way of adjusting something. That would be nice, that and Illustrator bug fixes (think Snow Illustrator ;-) )

Philip Littlewood — 01:01 AM on June 06, 2008

To John North

Why do you have to be so aggressive and confrontational. Whether you agree with the guys reasoning or not you surely must respect that he is explaining and demoing things and justifying the reasons. When was the last time you saw Apple do that.

maurice — 01:06 AM on June 06, 2008

Hey,

what I would like to see: scrollable input boxes! (like in macrabbit's CSS-edit). Scrolling changes the value in the input box. Very nice way of adjusting something. That would be nice, that and Illustrator bug fixes (think Snow Illustrator ;-) )

El Aura — 01:08 AM on June 06, 2008

To add my votes:
- Expose
- Library vs. document centric (your comparisons look like false excuses, like comparing apples and oranges)

Caspar Fairhall — 01:11 AM on June 06, 2008

You make an interesting case, John, and it's well argued. Thank you for taking the time and the effort to address the issue.

I don't agree though, because there are important differences between applications such as those in Final Cut Studio and the Adobe CS suite. A key difference, from my point of view, is that I tend to need that 'background cluuter' as you call it -- which means of course open Finder windows and windows from other apps that I'm using in tandem. These are very useful for drag and drop operations, which I for one use a great deal when working (for example) between Photoshop, Illustrator and FireWorks. The monolithic window simply gets in the way. In trying the FireWorks beta, I've found that the fact that the entire interface is restricted when shrinking a window to do this is a real pain. The idea of having to work with a number of apps constrained in this way is disturbing.

You mention users who choose to go to full screen mode when working in Photoshop by hitting 'F'. I do this too, at times, mainly to better see a large file at 100% magnification. It's not a hack: surely that's precisely why that mode was included in Photoshop in the first place. The key point is that it's easy to enter and it's easy to exit. That's the key point. With the monolithic windows, while we're not locked in, it's a real nuisance to drag the tools out of the main window and resize the document each time. (By the way, I do like the tabs: they're great.)

I find the experience so disruptive and unpleasant that despite the many improvements (especially in text handling) I probably won't be upgrading unless it's changed, or at the very least changed to simple permanent preference setting that I can disable. After all, the current suite of software is very good.

Jens Tenhaeff — 01:26 AM on June 06, 2008

Tabbed windows are a great idea for a content-reading app like a web browser. For a content-creating app like InDesign or Photoshop? Not so much. How am I supposed to drag stuff from one document into the other in this mode?

João Lúcio — 01:39 AM on June 06, 2008

Just don't compare Photoshop or other Adobe apps to Final Cut/Motion (not a frame but several windows put together) or iLife/iWork apps (short menu bars with few options and... panels for other tasks that are not contained in the applications' main window). We use Mac because we like to have our windows/panels independent. That's what enables me to put two document windows side by side or in different displays, to compare or get info from one to another. Try to do that with an app frame...
The switch on/off better work well. I don't want to have to switch it off everytime I open a document or if I do some other stuff in the app. I don't need it and don't want to be anoied by it.

Jimmi — 01:39 AM on June 06, 2008

Thank God this is only an option.

A lot of graphic designers like me are constantly moving between InDesign, Photoshop, Illustrator, Mail, the Finder and others.

I certainly wouldn't enjoy a big grey wall between me and my others apps.

Zaph — 01:50 AM on June 06, 2008

CAN WE PLEASE NOT HAVE THE UI ELEMENTS DONE IN UPPER CASE? IT IS LESS LEGIBLE AND USES *FAR* MORE SPACE, MEANING THAT WHEN MULTIPLE TABS ARE NEXT TO EACH OTHER YOU GET TO SEE JUST TWO OR THREE LETTERS OF EACH. PLUS IT'S KIND OF RUDE! WHY NOT HAVE EXCLAMATION MARKS FOR THE MOST IMPORTANT ONES!?!

Also, I don't know about you, but I've used multiple monitors for the longest time, and an app frame does not work well with that workflow.

In Dreamweaver, I'd just like to see some integration between the Files window and the Finder (putting a big box behind it so we forget about it is not a solution ).

Zaph — 01:56 AM on June 06, 2008

And will Photoshop be getting the new rows and rows of integrated interface toolbars like DW? Someone else recently said it reminded them of the screenshot that a journalist (David Pogue?) had posted of Word with ALL of the toolbars turned on. Are we really heading back down that route? Taking direction from 10 year old Microsoft UIs (that sucked 10 years ago)?

Jon Hicks — 01:56 AM on June 06, 2008

I for one much prefer this new window style - what I don't like about it are the elements left over from CS3 like the 'original/preview' bar in Fireworks - these stand out like a sore thumb in this new slick UI.

[I can't speak for the FW team, but broadly speaking the whole effort is evolutionary. That is, we're working to make all the widgets and controls consistent, but of course they grew up independently in multiple product teams/companies over many years. More and more things will fall into line, but unfortunately it's not a one-shot deal. --J.]

Oliver — 02:05 AM on June 06, 2008

One of the strengths of the Mac's document-centric model is being able to stack and mix different applications' own windows, eg. Photoshop document, text-editor-window, browser window for previewing, another Photoshop document. And if I want to see them all at the same time I just hit Exposé (Interestingly Photoshop is the only application on my Mac that has some glitches under Exposé and Spaces, take that as you will). I'm not just working with one document, like say in iTunes or iPhoto, I need to be able to mix and switch between several, different sources. How on earth could I do such a thing in an application frame? So if you say this UI is optional, please make sure the other UI-mode does not get deprecated over time and stops getting new features...

And another argument of yours is "if we can get new, useful features on top of existing features, why not?". And I agree, entirely. But some paragraphs later you say that Mac OS X's unique "changed-document" controls (the pointy close box) aren't possible inside an application frame... and THAT is exactly the point. I have nothing against good custom UIs at all. They're great as long as they serve a purpose (for example the neutral/gray controls for designers). BUT they have to behave EXACTLY as expected, and that's where Photoshop CS3 falls short: Exposé glitches, Spaces in general, those irritating close boxes on the wrong side, etc.

So why should we trust Adobe to get a better platform citizen when they are trying to introduce even more custom UI controls without fixing the existing UI glitches for so long? And as long as you're bringing up Apple as an example: they're pro-interface works as expected, even when they introduce new features and sport a new look.

Sergey Todorov — 02:10 AM on June 06, 2008

The new UI looks great. As a user of Photoshop on Windows for 7-8 years, I have recently moved to Mac, and I must say that I keep Photoshop in its own Space just so I can have a solid-color backdrop behind my documents to reduce distraction.

I dig details around the UI as well - the new palette tabs look gorgeous, minimalistic and functional. Not so crazy about the close / minimize / zoom buttons - I think they are rather large, but that's just nitpicking.

For people who are not fond of the "grayness" of the interface - I think it suits Photoshop great. It's a pro app, where distractions kept to a minimum should be a welcome feature.

As for those who criticize that you have deviated from the accepted "Mac-style" - I think your answer if very to the point. Functionality over ideology. Apple is obviously willing to break its own conventions when it comes up to pro applications and so should you.

Stuart Wilkes — 02:19 AM on June 06, 2008

I don't have a problem with the UI changes that have been revealed given that they're optional apart from the custom window open/close/minimise widgets. What on earth is up with those? The Mac standard ones are either coloured - which I prefer - or grey if you chose the graphite theme. They're one of the most pervasive UI bits in the OS and it really, really bugs me when anyone, whether that's Apple or a third party, like with Disco, uses custom ones.

It's great to see Adobe are thinking hard about how to improve the interface of Photoshop whilst considering platform differences, but this particular change feels like change for change's sake with no real benefit.

garbage — 02:21 AM on June 06, 2008

"hence the asterisk to indicate document "dirtiness.""

Thats just garbage, I want the genius OS standard way, not the SHODDY HACKED ON AFTER THOUGH windows way of telling me if a document has been edited.

Jens Tenhaeff — 02:26 AM on June 06, 2008

Tabbed windows may be a great idea for a content-reading app like a web browser. For content-creating apps like InDesign or Photoshop? Not so much. How am I supposed to drag stuff from one document into the other in this mode? Via yet another keyboard shortcut that usurps the place of an OS-key-combo?

Jonathan — 02:29 AM on June 06, 2008

I like the "new" interface. It's definitely an improvement, and I didn't expect less from Adobe. I'm a graphic designer and as much as I love my desktop backgrounds, I want as little disctraction as possible when I'm working. The application frame and the "greyish" look do exactly that.

Craig Grannell — 02:33 AM on June 06, 2008

I ran a piece on Cult of Mac recently about the UI, which had some recoil in horror and others say Adobe hasn't gone far enough. The defence of the application frame by comparing to Apple breaking its own UI conventions isn't really good enough. As it currently stands, the Fireworks beta UI is dreadful on a number of counts. It's horrendously buggy (and, yes, I know it's beta, but I'd currently say it's borderline unusable, which is rare for even early betas), and some of the conventions are simply too broken.

Even when Apple's going off on one, it doesn't shove a load of tools into the toolbar. Adobe's new UI has custom close/minimise/zoom buttons—why? And if it's doing its own UI, why aren't these custom buttons used throughout? Inconsistency with the OS is one thing, but inconsistency within the application itself is bad. Regarding the resizing, I don't have a problem with that, but Adobe should leave the standard resize drag-handle in place, because otherwise users' cognitive resources are better spent understanding how an application can help them achieve their goals, not figuring out how to do basic tasks with user-interface components.

The funny thing about this is that it's almost certain to finally push many designers away from Adobe products. A lot of Mac users I know are already looking for ways to jump ship, and even some Windows users are looking at the UI and thinking "just no". While I appreciate the intent regarding innovation, it just strikes me that Adobe's not really got a handle anymore on what makes a thoroughly successful and polished UI. Perhaps the final releases will change that, but experience proves that most Adobe products don't change a great deal from public betas to shipping.

Charlie — 02:34 AM on June 06, 2008

It looks great!

Jonny Bonny — 02:35 AM on June 06, 2008

Well...

I will reserve my judgment until I have tried it. Looks interesting though.

dc — 03:30 AM on June 06, 2008

Simple, more Mac-like compromise: Why not just add the tab bar in the current full-screen mode? That seems reasonable and useful.

Olly — 03:31 AM on June 06, 2008

I think I like that.

I'd be interested to see how this works across multiple monitors.

On Windows, I'm still using PS CS2, with my documents and main tool palette on one monitor, and all the other palettes arranged across the other.

I can't visualise how well this would work with the newer interface. It seems better suited to one large screen to me.

Simon — 03:33 AM on June 06, 2008

Looking around at Apple's apps in order to make excuses for doing things one way or the other seems self-serving. Many of the comparisons you make are moot. Take Final Cut Pro and Motion for example. These are project-based apps. You don't use these apps to edit several files at a time. Instead, you'll open a project and work on it for long periods, perhaps even for weeks at a time. Logic (the pro app I'm most familiar with) is a case in point.

Photoshop is very different. A designer might open and close dozens of documents an hour and having several open at a time is the norm. Sure, many Photoshop users will sit in front of the same document for hours at a time, may be even only working on one document for an entire week. However the the application is still very much document centric.

For this reason, the comparisons with library-based apps such as iPhoto, Aperture as well as project-based apps like Motion, Final Cut etc. are moot. The comparisons with Pages and other document-based applications are much more relevant and Adobe should take great pains to stick to Apple's and Microsoft's UI guidelines for document-based applications on both platforms.

Any arguments about Adobe wishing to streamline its development process, i.e. to unify it to make their developer's lives easier (which I suspect a lot of this may actually be about at its core) is irrelevant. Adobe should be primarily concerned with taking maximum advantage of the underlying platforms for the sake of their users, even if that means having to maintain two code bases. Anything else is doing a disservice to your customers and users.

So, the places to start would be:

- Cmd-H hides an application on Mac OS X. Many of your users actually use other applications outside of CS3 and may like to hide your applications once in a while. Co-opting Cmd-H comes across as extremely self-centered. I know the reason is historical, but as an OS X user I frankly don't care.

- Get your apps working with Spaces. Finger-pointing at Apple doesn't help your customers - your apps are still dysfunctional. Things may have now been solved with 10.5.3 (for the most part) but don't let this happen again. When Apple releases a new OS version get on it right away. Test in advance even! I bet all of your apps worked with Vista from day one. Of the dozens of apps I use, those from the two biggest vendors are the only ones that had problems with Spaces: Microsoft Office 2008 and CS3. I can't come up with any reasonable explanation for this given the huge development and test resources available other than these companies simply don't care. And given the expense of Adobe's products I certainly hope this isn't true.

Making an application Mac-like would involve re-thinking the whole UI. What annoys me in Photoshop and Illustrator most of all are the endless nested modal dialogs. Why is the color picker dialog modal? Changing a gradient's colors requires navigating through three or four levels of modal dialogs. It's so Windows, it's so 1995, and it really sucks from a usability point of view.

Being Mac-like isn't about application frames etc. If you looked at the apps you mentioned more closely you'd realize that the big differentiator of good Mac apps to their mediocre Windows brethren is that they raise very few modal dialogs and when they absolutely have to the newer apps use window-attached sheets.

Suggestion: move all commonly-used functions and parameters from the decrepit modal dialogs to context-sensitive, non-modal inspectors a la Pages, OmniGraffle etc. If any functions must remain in dialogs then make them document-specific sheets.

Any musings on making PS more usable with an application frame are irrelevant in the face of the serious usability issues posed by Photoshop's modal-dialog-based UI.

Guntis — 03:53 AM on June 06, 2008

Regarding custom scrollbars you mention in http://www.jnack.com/adobe/photoshop/ui/FCP_scrollbars.gif - I think much better example is the latest version of Logic - they look more Aqua, and those ends are for one-minesion zoom purposes. I can zoom vertically OR horizontally (independently!) by dragging scroll bar slider longer or shorter. Not for Photoshop.

Guntis — 03:59 AM on June 06, 2008

Regarding custom scrollbars you mention in http://www.jnack.com/adobe/photoshop/ui/FCP_scrollbars.gif - I think much better example is the latest version of Logic - I can see that Apple itself tries to come back to the Aqua guidelines in their latest Pro apps. They look more Aqua-style again, and those ends are for one-dimension zoom purposes. I can zoom vertically OR horizontally (independently!) by dragging scroll bar slider longer or shorter. Not for Photoshop.

Samo — 04:01 AM on June 06, 2008

Photoshop is the new Blender. ;o)

Seriously, though. Photoshop is a very specialized application, it can go WAY off the usualy OS X/Vista app design as long as it makes it more productive. The professional users should be able to adapt. It would make little sense to make everyone suffer just because some people are stuck in 1997 still.

Olly — 04:07 AM on June 06, 2008

I think I like that.

I'd be interested to see how this works across multiple monitors.

On Windows, I'm still using PS CS2, with my documents and main tool palette on one monitor, and all the other palettes arranged across the other.

I can't visualise how well this would work with the newer interface. It seems better suited to one large screen to me.

Guntis — 04:12 AM on June 06, 2008

Here are some good observations: http://cultofmac.com/adobe-fireworks-mac-os-x-beta-ui-hell/2026
100% agree.

Matthew Buchanan — 04:19 AM on June 06, 2008

Mark me down as a thumbs-down for the uppercase palette names. I prefer to turn smoothing off under 12 pixels because it aids in the rendering of fonts like Verdana in Safari, but I do like the way that Apple's apps smooth their Lucida Grande interface type no matter what the size. Please consider overriding the system setting and turn smoothing on for the interface, or make this an option.

For the commenters who want shortcut keys for Image and Canvas size, you can set these yourself in the Keyboard Shortcuts... menu option. What you can't set (and what there again appears to be no support for in the FW CS4 beta) is Command-` to cycle through the app's open windows when the app frame is enabled. Please make this configurable.

I'm so far enjoying the FW CS4 beta and have no issue with the app frame apart from the above. If you're not certain whether to ship it on or off by default, why not ask the user once on initial startup for their preference. Likewise Command-H for hide app.

Peter — 04:24 AM on June 06, 2008

I haven't had time to play with the DW/FW betas. Does the new app frame still allow panels to be docked to screen edges (as opposed to only the frame window)?

Overall, I like new concept, especially since there is an option to disable the app frame whenever it makes sense, so there is really nothing to lose. I particularly like the new tabbed groupable document windows, that's something I always liked in Microsoft's Visual Studio. However, I find the design of the new frame disputable, especially the bright blue Photoshop icon and the non-standard maximize/minimize/close widgets.

I'd love to see a function to disable the app frame window on Windows from time to time and have Photoshop behave just like on a Mac. Now that you are adding the frame to the Mac version, why not give an option to switch it off on Windows?


Here are a few issues with the CS3 panel system which I'd love to see resolved in the final version of the new UI:


  • It was impossible to dock panels to the edges of secondary monitors. They always remain floating.

  • The tool bar and the animation timeline panel cannot not be docked horizontally, only vertically. The toolbar has no horizontal mode in Photoshop, but it does in other Creative Suite application. In InDesign, the horizontal toolbar doesn't behave like a regular one and refuses to be docked horizontally, regular tool bars can't be docked vertically below the tool bar.
  • It is impossible to put regular panel icons below the tool bar, thus wasting an entire dock columng just for the tools, especially when it is in two-column mode, or very short, like in InCopy. This has led me to always working with my toolbar floating.
  • The full-screen mode main menu popup arrow in Photoshop's tool bar has become way too small in CS3. It always used to be in my opinion. A key command to pop up the menu at the mouse cursor position like a regular right-click context menu would help tremendously, not just in full screen mode.
    But generally I found the grab area of floating panels too small, I usually Alt/Option drag the tabs (or the application icon in case of the tool bars) to move the entire panel group since aming for that tiny title bar takes too long.
  • The "auto-hide panels" preference sometimes does not work when the application frame is placed on a secondary monitor (at least on Windows).
  • Panels that display actual document content (such as the timelines in Photoshop and Flash, or the measurement log) have no option that lets you turn them into regular windows that can be maximized on a secondary monitor. Such a feature would also allow having the panels open for multiple documents at once and then comparing them or doing drag & drop.

  • Hope that was useful, sorry for the lengthy post.

    Asbjørn — 04:28 AM on June 06, 2008

    On Windows Vista you should not use a custom application frame. (see http://msdn.microsoft.com/en-us/library/aa974173.aspx ) It has zero benefits, but lots of problems. You lose the window shadow, which looks distracting with other windows on screen. You also lose the glass windows frame, which makes Adobe apps look horribly out of place. Please get rid of that custom frame.

    Erik Kambestad Veland — 05:17 AM on June 06, 2008

    Just admit it, Adobe wishes they had wrote their own Operating System don't they?

    Screw this NIH mentality and conform to true and tested guidelines. I don't want to get jarred into a different alien environment from switching from one app to another. Play nice with your ecosystems and stop trying to reinvent the wheel.

    I'm not a kid Adobe, I know how to switch on Graphite in the Apperance UI. I don't need you to reinvent my buttons simply because they weren't conservative enough for you.

    I've used Photoshop since 1.0 and the Mac for even longer. This smacks of arrogance and disregards for your user base all the way!

    Shame on you for buying into their arguments and finger-pointing at Apple!

    AJ Kandy — 05:27 AM on June 06, 2008

    John, thanks for this insight into the thinking. Improving a UI always means sacrificing something people are used to, in the hopes that they grasp a new way that is hopefully better. I live in Photoshop 24/7 and things like dealing with palette clutter is my #1 annoyance; after having used single-window software like Mackie Tracktion, the new Logic 8, etc, I can definitely say I prefer that paradigm.

    What makes something Mac-like or not is really a set of behaviours (as another poster mentioned, universal drag-and-drop, a system that doesn't pop up with notifications every 3 seconds like a child that's had too much sugar, etc. etc. As long as PS CS4 respects and embraces those conventions and systemwide functions that'll be fine.

    One thing I can say, as someone who uses PS for web mockups 99% of the time, is that I would love to have more layout-based UI tools, borrowed from AI and ID; things like the ability to create tables, define partial borders on sides of a box, to have InDesign-style rounded corner boxes where the corners stay the same radius when you stretch them...(in fact having that in Illustrator would be cool, too. Nothing says amateur design like squished corner radii)

    bananaranha — 05:30 AM on June 06, 2008

    consistency, so does that mean the various applications in the suite will behave more in the same way?
    --{Yes, that's the goal. It's an evolutionary process. --J.}

    An "evolutionary process"? What's to evolve? The most common problems are very simple —different widget behavious, confliction shortcuts, etc. They should have been fixed *years* ago.

    Since you [Adobe] don't seem to mind alienating users with UI changes no one asked for anyway, there's no reason not to alienate a few of the people used to conflicting old conventions once, and be done with it. Photoshop, Illustrator and InDesign should have been streamlined a *long* time ago. By now, even Macromedia apps should have been integrated —it seems FW4 and DW4 are more or less the same mess.

    ie in photoshop you can click and hold the word "opacity" and adjust its value, whereas in Illustrator you have to use the the drop-down box and adjust the slider that way.
    --{We intend to get onto a single, best-of-breed set of widgets that enable things like the "scrubby sliders" you mention. They're on the roadmap, but not for the upcoming release. (We're peeling the onion, though.)}

    Not for the upcoming release? Well, keep peeling, then. Maybe sometime around 2040.

    Seeing the lackluster set of new PS CS3 features for example, one wonders how the development team spends its time —they even claim they follow "extreme programming".

    Will documents inside the frame be considered stand-alone windows for window-management features like Expose?
    --{No, although we'd like to make that work. Last I heard we'd inquired with Apple & that's not something Exposé supports. (You can't use it to display/shuffle the contents of tabs in Safari, either.) If the capability becomes available, we'll work on supporting it. --J.}

    Well, the Shiira browser does it for tabbed windows. Hell, even VMWare Fusion and Parallels do it for virtualized Windows windows. And you're developers can't come up with something to make it work for framed windows?

    I call "lack of interest" and/or "minimal attention to detail". Whch is insulting, considering how much we have to spend for a copy of Adobe's CS packages.

    I know that Adobe is the 1000-pound gorilla in its field today —I'm not crazy to thing there are real competitors currently—, but Quark used to be too. And there was a time when Novell Netware was king in it's field and Lotus had the spreadsheet marked by itself.

    Iwan Negro — 05:31 AM on June 06, 2008

    Apple unified with leopard their gui. The Pro Apps always had this Cool-Grey colour scheme with some obsolete GUI elements. Aperture introduced an all new Pro Apps GUI design. Which is in my opinion a more worked out, specialised GUI of the basic Leopard one. If you refer to Apples Pro Apps for any kind of GUI Look And Feel you can only take Aperture as a real reference.

    It is great that Adobe takes the basic Leopard/Aperture Look And Feel to refine their own GUI design and bring all this then to Windows instead of doing the vice-versa to the Mac. But wouldn't it be possible for Adobe and Apple to work more tightly together to create one Pro App look that suits both parties?

    I'm not worried about the application frame at all. I'm rather concerned about functionality, simplicity, accessibility and faster workflows. When adobe can promise that all those aspects will get better with the new gui then do it.

    But for now I'm not that convinced, especially when I use Fireworks CS4 and Dreamweaver CS4. I don't know what is the policy of adobe when it comes to redo a complete app layout but both apps desperately need one. Some palettes are not logic, cluttered, not understandable or just useless. Also many Main Menu items should be cleaned up and regrouped. Some of the window dialogues need also a refresh.

    I can see much more effort in this point when I look at Flash CS4. Its getting closer to After Effects that has a highly efficient, simple global layout compared to its high complexity. Also take aperture as an example of complex functionality packed into a simple GUI.

    Chris Snyder — 05:33 AM on June 06, 2008

    Now if only someone on the application packaging team would sweat the details this much. Photoshop's Mac UI is a sweet dream compared to the install process and OSX integration.

    Does the Open With... menu for images still get plastered with a million different choices? Does the installer still splooge 15 other semi-required apps onto the system? Every time I install Photoshop I feel like I've given Adobe license to completely violate my computer.

    I get the feeling that Adobe engineers don't have a clue about how OSX applications are supposed to work. Like Microsoft, they have a paradigm and a platform and who cares if the rest of the world thinks different(ly)? How many man hours were put into porting the Windows registry to OSX to that all of those components could be hooked together?

    Sorry for the rant, but the price of your app and past missteps on OSX entitle us to some anger.

    M P — 05:36 AM on June 06, 2008

    To the comments about all caps panel names, please take a look at iTunes. Go ahead, I'll wait. The "Panel" names there, like LIBRARY, STORE and PLAYLISTS are done in all-caps (or perhaps fake small caps) so there is some precedent. All caps certainly gives less visual cues and differentiation, esp. at small sizes, so not sure whether this is a good move or not.

    Iwan Negro — 05:37 AM on June 06, 2008

    Apple unified with leopard their gui. The Pro Apps always had this Cool-Grey colour scheme with some obsolete GUI elements. Aperture introduced an all new Pro Apps GUI design. Which is in my opinion a more worked out, specialised GUI of the basic Leopard one. If you refer to Apples Pro Apps for any kind of GUI Look And Feel you can only take Aperture as a real reference.

    It is great that Adobe takes the basic Leopard/Aperture Look And Feel to refine their own GUI design and bring all this then to Windows instead of doing the vice-versa to the Mac. But wouldn't it be possible for Adobe and Apple to work more tightly together to create one Pro App look that suits both parties?

    I'm not worried about the application frame at all. I'm rather concerned about functionality, simplicity, accessibility and faster workflows. When adobe can promise that all those aspects will get better with the new gui then do it.

    But for now I'm not that convinced, especially when I use Fireworks CS4 and Dreamweaver CS4. I don't know what is the policy of adobe when it comes to redo a complete app layout but both apps desperately need one. Some palettes are not logic, cluttered, not understandable or just useless. Also many Main Menu items should be cleaned up and regrouped. Some of the window dialogues need also a refresh.

    I can see much more effort in this point when I look at Flash CS4. Its getting closer to After Effects that has a highly efficient, simple global layout compared to its high complexity. Also take aperture as an example of complex functionality packed into a simple GUI.

    Tim Bedford — 06:05 AM on June 06, 2008

    The Windows style MDI interface, which you are calling an App frame is bad. The only time you see it in Apple application are those that don't deal with multiple documents at the same time. iMovie, FinalCut, iTunes, etc. Only ever have one document open at a time.

    As soon as you allow the user to open multiple documents placing them all in one window becomes less useable. Documents in the application always take up the same Z-depth in relation to other application's document windows. This makes drag and drop between applications almost useless. It also inconveniences the organising of documents from various applications so that they are visible all at the same time.

    Photoshop is not a single document application, and it has had a full screen option for a very long time if we wanted to block out distraction. This application frame thing is just insane.

    Jeroen — 06:11 AM on June 06, 2008

    closing or resizing a palette in Photoshop isn't very Mac like. I don't see spheres to click on, but a cross and a line on the opposite side.

    Matt Radel — 06:26 AM on June 06, 2008

    I'd say that I'm digging the CS4 UI thus far. I am a bit worried about performance (which I can only hope / assume is the next thing on the docket to work on). All the CS4 apps I've played with thus far have just felt sluggish, especially when you resize the application frame. But I am happy that you're ditching the concept of fading out the panels when the application loses focus - that never really worked right on the Mac.

    Also, I'd like to echo the comments about the all caps panel titles. It seems that adobe has taken great care to drive focus to the document you're working on by making the panels softer with all the grays. But the shouting caps counteracts that effect...and just annoys me. I can't scan the panel names any faster in CS4 than CS3 either. The caps just make me...uneasy.

    Otherwise, keep up the great work! I can't wait to see the rest of the lineup - especially Flash.

    Eric — 06:37 AM on June 06, 2008

    I worried about this, but once I fired up DreamWeaver CS4 I thought it was just fine. I really like that it's more Adobe-like. I'm almost ready to uninstall DreamWeaver CS3!

    I've owned every version of Photoshop back to 2.5(PC, then Mac from version 5).

    I never had any complaints about the UI change decisions Adobe made. But that's me. I'm a photographer/editor, not a font herder. :-D

    PeterK — 06:43 AM on June 06, 2008

    "I cast my vote for NO application frame. It's one of the absolute worst things about using Windows."

    I think you meant to say one of the best features, since it automatically hides all distracting desktop elements and gives you a neutral grey background behind your images, which is a crucial requirement for anyone doing colour-critical work in Photoshop.

    David M. Converse — 06:43 AM on June 06, 2008

    Change just for the sake of change is bad. I'd rather see the CS team working on system integration rather than monkeying with the UI AGAIN (64-bit CS4, anyone?)

    If you are going to do UI work, leave Photoshop alone and fix Bridge, which royally sucks and has a bunch of bugs, performance issues, misfeatures, and is overall not very Mac-like at all (and there shouldn't be an excuse for it, Bridge is fairly new.)

    Fix integration with Spaces, add better AppleScript support, beef up the layer "Blend If" options (how about instead of the split sliders, have boxes where you can type in the blend values and then pick the threshold?) And remember that many of your customers use multiple monitors, where the app frame UI is worthless.

    Brett — 06:57 AM on June 06, 2008

    Hey jon is that PS icon final? I really like the current one with the white letters.

    The black letters inside the icon looks strange and especially if arranged in the dock next to the other icons with white letters it will look out of place.

    Can you please confirm that the black Ps letters is just for the beta?

    Thanks

    [All the new icons feature dark text on colored squares. I can't really tell you why, as I have absolutely no say in these matters. --J.]

    AJ Kandy — 07:15 AM on June 06, 2008

    Oh yeah, two more wish list items:

    - Search inside the Layers palette. There are times you're looking for a hidden layer that's nested several folders deep. Being able to search for it and see the result highlighted on-screen would be useful.

    - The ability to define and apply character and paragraph styles like InDesign. This is a HUGE benefit for web mockup creation, where you can define H1, H2, body, etc. styles once and then apply it automatically. Plus, if you decide to modify a style, it will then change all instances where that style occurs automatically...as opposed to having to slog through layer after layer changing it manually.

    Frank — 07:18 AM on June 06, 2008

    Will there be any change for the Windows version which causes the Photoshop child windows to show up in the Task switcher?
    I really love the Mac version where i can find the open documents with Exposé and it would be very important to me to have the same feature on Windows as well.

    Thanks in advance for your answer.

    Matthias — 07:30 AM on June 06, 2008

    I just fell in love with the new application frame-style. Working with the CS4 betas was a great joy because the programs look more professional. I find that the new UI is a major improvement to the Adobe products and I'm just wondering some things:
    - does the "overall"-frame style affect the RAM/system power usage of CS4-applications (in comparison to CS3)?
    - will the multiple document layouts also work in my favorite fullscreen-mode in Photoshop?

    I can't hardly wait for the upcoming Creative Suite because everything I've seen is just great.

    JimHere — 07:41 AM on June 06, 2008

    LKM — John, you will find that nobody complains about the UI for Lightroom...

    I think LR is very stylized -- too stylized. THe groovy-ness of it distracts from the work. Hopefully one's photos will look as good on paper as they might in the LR world of subtle dark bevels, but I prefer a more standard UI. Look at the time they spent on the LR 'red eye'. PS has a red-eye too (I use curves actually), but much less fussy.

    Josh T. — 07:41 AM on June 06, 2008

    Been a heavy Mac user my whole life and I _loved_ the new app-frame in fireworks from day one. Keep up the great work!

    Dustin Wilson — 07:49 AM on June 06, 2008

    I really thank you, John, for providing feedback to all of us.

    The caveats of this interface will and should be beat to death. There's many problems with the interface, most notably the close, minimize, and zoom buttons on the left. I can throw everything else out, especially after hearing that the grey crap in the back can be turned off. Truthfully, you should just use the Mac's interface for that. It also provides the user with a notification that the document has been edited. No need for an asterisk. The close button contains a dot instead of an X when the document's been edited. The controls should be on the right for the Windows users, and show the typical icons they're used to for it such as the X, the underscore, and the box. Its appearance otherwise is up to you as they can't seem to figure out how they want the interface to look on that platform anyway.

    I'm unsure what the major focus is on, but if the interface has been changed and programming has been done to force the system to allow the Adobe apps to use this atrocious UI then I don't believe performance really is that much of a focus here as for things that are available from the system you've reinvented the wheel. My major problem with many Adobe applications as of late has to deal with performance, mostly in Photoshop. I find Photoshop CS3 to be mostly unusable. I tend to use CS2 more as it opens faster, runs faster, uses less memory, and doesn't bring up the beachball of death on even the most mundane of tasks such as selecting a tool. It crashes from time to time and displays at least one ram leak a day in the terminal. I'm not running this application on old hardware. I'm using a Mac Pro Quad 3Ghz with 4GB of memory. Illustrator CS3 has problems of its own, but it doesn't have the rampant problems Photoshop has. What exactly is being done to make CS4 perform better? I don't care much about 64bit. Yes it sucks that it won't be 64bit, but Apple didn't really make it that easy for you guys to drop ship with Carbon and jump to making your suite of applications out of Cocoa. People need to get over that. You've promised it in the next version. The application itself needs to be made to perform better. I can't afford to make another upgrade purchase and then find that I can't use it, especially at the prices the suite is running at these days.

    Dave — 08:03 AM on June 06, 2008

    I have to agree on the ALL CAPS thing. Comparing the screenshot in CS4 you posted with Photoshop CS3, the latter seems a lot cleaner.

    I had to do a double-take to find what I was looking for and I've been using Photoshop for years. It's especially bad in the palettes. Even though I knew where everything "was", it seemed slower to comprehend. For example, take a stopwatch, tell someone to look for Channels in both and see which they find quicker. I would be bet CS3 wins, even though they're both the same location.

    It really doesn't matter in iTunes because even if you took those headers away, you would still know what everything was because the important things you actually do click on ("Music", "Movies", "iTunes Store") aren't in capitals. I don't even notice those headers while using it. iTunes also isn't a professional application, whereas Photoshop is, and I would wager *any* potential slowdown in a professional application is bad, especially an arbitrary design decision that can easily be reversed.

    Guntis — 08:04 AM on June 06, 2008

    If I may ask just one more request for the upcoming CS4 apps - Mac OS X standard Type palette (Command+T in almost any Apple application). It's way better than those long long font lists in Adobe apps. I have created font sets based on font type or for the specific languages, I've added several fonts to the favorties, etc. I can search for some specific words in the font names and thus filter font list, etc. Nothing of that is available in Adobe font menus. They look really like taken from any Windows application. Mac OS X standard color picker also would be welcome (even as addition to Adobe standard color palettes), but Font palette is badly missing.

    Brandon Kelly — 08:06 AM on June 06, 2008

    Having the app frame enabled by default or not is definitely a pickle. Perhaps when launching Photoshop CS4 for the first time, the user should be presented a dialog asking which "mode" they'd like to use, and quick instructions on how to change it in the future.

    [Unfortunately I don't think people would be in a position to make an informed decision until after they've tried the app frame, so asking up front is likely just to bewilder them. I hate it the feeling of software (or anything) putting a gun to my head and saying, "Blabbity blabbity foo; *yes* or *no*?" --J.]

    Kyle — 08:33 AM on Jun