Markus Brunetti’s Facades

Cathédrale Notre-Dame

Artist and photographer Markus Brunetti creates stunning photographs of European cathedrals from countless source images that he takes and painstakingly composites into photographic equivalents of elevation drawings. The results are intricately unreal; perspective is dramatically flattened, light is almost impossibly even, and all signs of human activity are removed—in effect, Brunetti reconstructs the original architectural ideal that motivated each structure. Brunetti discusses his technique in this video:

The output is enormous, as tall as ten feet each, as I understand it. An exhibition of them is on display through this week at Yossi Milo Gallery in New York City.

Markus Brunetti’s “Facades” at Yossi Milo Gallery

More of his work at markus-brunetti.de. Also see this article at nytimes.com. Many thanks to reader Adrian Ulrich for bringing this to my attention.

Basilica di Santa Maria di Collemaggio
Markus Brunetti
Duomo Santa Maria delle Colonne
+

Project Faces Sneak Preview

Adobe Project Faces

I realize that continually posting cool Adobe projects here can quickly come to look quite unseemly, but I can’t resist with this video, recorded at last week’s Adobe MAX conference. In it, Adobe developer evangelist Lee Brimelow demonstrates “Project Faces,” an iPad app that allows users to create bespoke typefaces on the fly just by manipulating a handful of parameter sliders. The screen grab of the app at the top of this post shows how simple the interface is to master, and in the video below you can see how quickly Brimelow is able to generate a completely new font and even export it for immediate use in Adobe Illustrator.

Professional type designers will have plenty of legitimate objections to whether this is really quality type design or not, but the sheer power on display here—the acute understanding of typeface mechanics combined with deeply informed engineering expertise—is amazing, and the democratizing spirit is thrilling, to boot. It’s another example of one of those things that, for me, fall under the heading “Only Adobe can do this.”

No more posts about my employer tomorrow, I promise.

+

The Rose Center for Earth and Space

Rose Planetarium

We were lucky enough to go to a wedding held at The American Museum of Natural History over the weekend. Here’s a shot of the museum’s glorious Hayden Planetarium, housed in The Rose Center for Earth and Space, at about 11p, with no one around.

+

Crowd-drawn Neighborhood Borders

DNAinfo: Greenwich VIllage Maps as Drawn by Residents Who Have Lived There Any Amount of Time

I’ve lived in New York seventeen years but I still don’t really know where Greenwich Village starts and ends. Neither, apparently, do most people, as you can see in the map above. That’s a composite of the Village’s neighborhood borders as drawn by visitors to DNAinfo’s neighborhood mapping project.

The site collected thousands of drawings from New Yorkers of how they define the area where they live and created fascinating visualizations of every neighborhood. What it shows is that these boundaries are very fluid, something that’s even more apparent when you compare the drawings from Village residents who have lived there more than twenty years (below) to those who have lived there any amount of time (above).

DNAinfo: Greenwich VIllage Maps as Drawn by Residents Who Have Lived There Twenty Years or More

You can see and play with the data across all of New York City’s neighborhoods at visualizations.dnainfo.com.

+

More Project Comet in This Demo Video

Project Comet User Interface

Wow, the reception for Project Comet, Adobe’s newly announced, purpose-built UX/UI design and prototyping tool, has been tremendous. Here’s another tease: a great hands-on demo of the app from Comet’s very talented lead designer Talin Wadsworth, as interviewed at this week’s Adobe MAX conference by Terry White, our design and photography evangelist.

This is a more extensive demonstration of what Comet can do than we saw in Monday’s keynote; it runs about thirty minutes long, and Wadsworth answers lots of user questions that folks have had about the product since its announcement. But if you want to see what this fantastic new app does in detail—and also get a glimpse at how Repeat Grid can materially change the design process—it’s worth it.

Learn more about Project Comet and sign up for the public beta in early 2016 at adobe.com. Also read my blog post about the announcement.

+

Job Spotlight: ProPublica

ProPublica

New York-based, independent, non-profit newsroom ProPublica is doing some of the best journalism on the Internet. That’s thanks in no small part to their design director, the very talented David Sleight, who has brought an exacting sensibility to the presentation and interactivity of the organization’s content. I first met David many years ago when I was at The New York Times, and though I don’t work in news anymore, he springs immediately to mind anytime anyone asks me for names of the very smartest news designers I know.

David is building out a small but ambitious team at ProPublica to take their news products to the next level. First on his list is an Editorial Experience Designer, a very particular type of design professional that I first wrote about in this 2011 blog post. Over email, I asked David about the position, his team, and the work that they’re doing.

How do you and ProPublica define “editorial experience design”?

For me, “editorial experience design” sits squarely at the intersection of interactive design and traditional editorial design.
It’s interactive design that conveys a narrative arc, and editorial design that recognizes content isn’t necessarily static or consumed in a singular, fixed way.

This is still such a new field; how is it changing, both at ProPublica and at large?

I think it’s becoming more common inside newsrooms, even if they’re not calling it that. I hope it’s on its way to becoming the accepted norm, because the cross-section of skills it represents feels like the natural language of the medium.

The editorial design process is evolving as a result, too. Fewer static deliverables later in the process, more discussion of design systems and pattern language, a proliferation of not-quite-fully-baked interactive comping tools. And, oh yeah, a healthy dose of code throughout.

More importantly, designers are working with reporters far earlier in the process, with skills that sometimes overlap. At ProPublica we want those folks working together right from the start, when ideas are first taking shape. As the field evolves, those roles will interweave to the point of maybe even becoming a little indistinguishable from one another, a little fuzzy around the edges. I think the result will be some truly amazing work.

Can you share some examples of the editorial experience design work that your team is proud of?

State of Emergency,” our recent photo/audio essay on Baltimore in the wake of Freddie Gray’s death, is a great example of our maturing photo work. “Killing the Colorado” is another.

Our worker’s comp series (“The Demolition of Workers’ Comp,” “Fallout of Reforms,” and Patrick Fallon’s accompanying photo essay) showcases our growing ability to incorporate illustration, photography, and data elements into more cohesive presentations.

I also have a soft spot for “Firestone and the Warlord,” and how we met the challenge of presenting a novella-length story online. The tools we incorporated into the layout, like the simple “Save Your Spot” email feature, stay out of the way and try to be coincident with user behavior instead of imposing themselves on top of it.

This is a rich area for development, and we’ll be pushing further and further into this territory. There’s a lot here yet to explore.

What does the team look like now, and where will this person fit in?

We’re a small team of nimble generalists. We started about a year and a half ago with me coming aboard as ProPublica’s first design director.

Since then we’ve added a dedicated Producer as well as a Design Fellow, and strengthened the roster of outside collaborators we bring in on special projects. That’s all in addition to the folks from ProPublica’s editorial, data, and engagement teams who we collaborate closely with on a daily basis.

What does the day-to-day look like for this role?

The team is responsible for three broad areas, ranging from the very tactical to the very strategic.

On the tactical side, we keep an eye on regular story production and any visual assets that are needed to support it, like photography, illustration, etc. In the middle is what we call “enterprise editorial”: the 10-20 major stories we publish every year that really rise to the level of genuinely custom design work. And then on the more strategic end is the platform itself, propublica.org.

We’ve made a lot of progress in the first two areas in a short amount of time, and are just starting to turn our attention to that last section.

This role will play in all three areas, but it will focus mainly on the custom editorial and the web site.

Is this a newsroom job, a tech job, both, other?

All of the above! Honestly, we’re all one newsroom and don’t really distinguish strongly between “tech jobs” and “editorial jobs.” To us, they’re all “journalism jobs.”

I know lots of places might say something like that as a marketing point, but we truly mean it at ProPublica. When I was first talking about coming aboard my future boss, managing editor Robin Fields, told me it’s the kind of place where, “Everyone is expected to participate in the journalism.” That really struck a chord with me, and helped seal the deal. It’s really proven to be the case, and something I take to heart as we continue to develop our design and UX practice.

If you’re interested in this opportunity, read more at Authentic Jobs.

This is the latest in my occasional series spotlighting interesting job openings for designers. Also see my interviews with Hyperakt, Carbon 3D, ESPN, The Coral Project, Digg and Toca Boca.

+

Startup Compensation for Designers

Designer Fund posted this very helpful article full of compensation advice for designers who are considering joining startups. It goes into detail on these five areas that you should understand comprehensively…

  1. Your worth as an employee
  2. The total compensation offered
  3. The potential value of your equity
  4. Your personal priorities
  5. How future compensation will be determined

Salaries and compensation are difficult subjects for anyone, and when you’re entering the world of startups, negotiating for fair compensation in what is by definition a volatile situation can be challenging. This is especially true for designers, whose inherent value can often be underestimated or at least misunderstood by organizations that are often more attuned to the needs of engineers and businesspeople. This one article isn’t a silver bullet, but it’s a good start.

Read the full article at designerfund.com.

+

Project Comet

Project Comet

There were two big highlights from the keynote for Adobe’s annual MAX Conference this morning that I’m unabashedly excited about. The first was the fact that, twelve months after I debuted an early beta version of Comp CC at last year’s conference, that layout app played a major role onstage today in a demo of Adobe’s powerful, cloud-based workflow infrastructure for iOS. (Also, it’s now available on iPhone!)

If you play back the keynote at max.adobe.com starting at about 19 minutes in, you’ll see how Comp CC has blossomed into a powerful creativity tool that’s beautifully attuned to iOS’s touch interface, and also how Adobe has done truly impressive work breaking down the barriers between apps that have previously made productivity on iPad so difficult.

I’ll talk more about those things in another post, but I want to direct your attention to the keynote’s other major announcement: the debut of Adobe’s new user experience and user interface design application (for desktop), currently being developed under the code name Project Comet. Here is the promotional video:

One of the things that I’ve been doing since I joined Adobe in August is spending some time with the brilliant and dedicated team that’s been pouring tons of energy into turning Project Comet into a real product. I’ve been so impressed not just with the design and engineering talent that they’ve brought to bear for it, but also in their approach, which is both highly ambitious and wonderfully pragmatic.

On the one hand, they’ve shown terrific ingenuity in tackling problems that UX and UI designers encounter every day with clever, unexpected solutions. Project Comet’s Repeat Grid feature, which makes it practically effortless to create interfaces for structured data, is just the most prominent example. If you’ve ever designed an app or a web site, chances are good that you’ve had to make rows and columns of similarly constructed but still varied labels, images, avatars, text fields etc.

Historically this is a problem that has been solved—imperfectly—through smart objects or symbols, and also tedious manual spacing and image placement on the part of the designer. Instead of merely following the prior art, the team asked itself if there was a better answer—what if they could make almost everything automatic? What if they could compress what can literally take dozens of steps down to just two or three? With Repeat Grid, you just need to create one set of elements; the app practically does the rest, including duplicating items, placing images and importing real data. The gumption alone is impressive, but what really counts is that they then had the drive to invent that alternative from the ground up.

Here’s a quick and dirty screencast that I recorded to show Repeat Grid in action:

https://youtu.be/04Y4v_8EsEg

The whole app is riddled with brilliant touches like this.

At the same time, that ambition is tempered by a refreshing pragmatism. Though it would be disingenuous to try to claim underdog status for Adobe, from what I’ve seen the Project Comet team is well aware that the market for purpose-built UX/UI design tools has exploded largely without Adobe’s participation. This has translated into a determined focus on the fundamentals, a very disciplined approach to feature development that you’ll see throughout the app, but that will probably be most notable in Project Comet’s almost shocking speed and stability—the app can handle hundreds of art boards and thousands of objects with very little effort. The whole engine was built from scratch to be truly native to OS X, an approach that hasn’t traditionally been associated with Adobe, and it really shows.

Another dose of pragmatism: today’s announcement was just an announcement. The public beta arrives in early 2016, and version 1.0 is due later in the year. That’s a long road, and there’s still a tremendous amount of work to be done to deliver on today’s promises. From what I’ve seen, though, this team is firing on all cylinders and, what’s more, they’re committed to doing this in an open, humble way. Nothing is a foregone conclusion, but that’s what makes it exciting. Project Comet is one of the things that convinced me to join Adobe, and while I’m not working on it directly, I’m proud to be playing a bit part in it.

Learn more about Project Comet and sign up to be a beta tester at adobe.com.

+