Maybe - perhaps it's important to differentiate between branding/marketing-type work and product work. For the former, seeing early directional options has always been helpful. I've just been in too many situations where the designer/design team used some very specific style without clearing it all before the first check-in, and it doesn't work for me. If I did a poor job explaining what I wanted in these situations, I'd expect the design team to help me articulate the goal, and even then I'd want to see what options were considered.

For the latter, as a product lead it would indeed fall on me if I couldn't articulate the problem such that the solution was clearly correct or incorrect, though even then, there are almost always many ways to solve a problem, not all of which are clearly "correct'.

So maybe the takeaway should be "know your client/stakeholder" - if they have no design sense and showing them options is going to be a shit show, then by all means avoid that. :)

I've been a stakeholder in many a design review, and often seeing only one option can be quite frustrating. It makes feedback more difficult if it isn't matching my expectations. Often times I've seen a design and I'm like...eh, this isn't on target. At these times, seeing alternative approaches can help drive a constructive conversation.

That said, if you are confident in the approach and can defend it, then yes, by all means make the decision.

It requires a change in your workflow, but I would argue the current workflow is broken. It's akin to a development workflow sans version control, which is a mess.

Congrats Josh and team! So stoked on this.

Slack ripoff or not, my wife is a doctor, and I can't tell you how much they need this. Getting actual adoption is going to be tricky (they should have started on mobile, honestly).

Sweet, I'm a fan. :)

We definitely plan on engaging with the community a lot more often with tutorials and blog posts, but unfortunately we can't really offer any insights into upcoming releases.

Thanks for posting this. We were definitely watching the thread about Pixate being dead, but wanted to just get the release out rather than post another "coming soon" response. :)

In addition to spending a lot of time rewriting the data layer in Studio so it's way faster, we've also been spending a lot of time integrating into Google policies and systems. These aren't updates we would send to the community, so the silence can be understandingly frustrating, but all of the work we did is very worthwhile and of huge benefit to user's security and privacy.

We hope you like the release!

Wouldn't it also offer a nearly invisible level of protection? :)

Definitely compelling, but would you really push very specific pixels around on an iPad? Seems like Adobe Comp CC is a good target for an iPad - low-fidelity wireframing and ideating.