Slicy it is.

I don't think they lose anything from having an updated wordmark — they'd definitely have more to lose by going sans-type. I'd say that this isn't a missed chance at all, but the correct move to make. By strengthening the wordmark, Instagram now has two strong identifiable elements (with an improved lockup), giving them flexibility in building their name and brand recognition.

@Nathan M. My design team and I just signed ourselves up to InVision, but the downsides listed above are making me second guess our decision. If you're saying Flinto might possibly be the solve for things like animated transitions and fixed UI elements, I'd love it if you were willing to grant me a beta so I can could take it for a spin?

@N W. Am I missing something here? Other than the allusion to the hamburger icon used on a lot of small screen experiences and having the copy and some images reflow to the size of the viewport, I don't see any other effort to make this a mobile-first experience. I loaded the site in Safari on my iPhone and what's served is the large screen experience and not optimized for small screens. And doing the simple window resize drag test results in some pretty ugly content arrangements.

And to clarify, I'm not saying we're disagreeing on the impact of desktop users, just not buying that it's was a decision based on mobile-first design.

@Radu C. This is an explanation I'd buy.

I figured the change was possibly to encourage visitors to engage with the content on the landing page. And while I'm skeptical about it, it's possible that according to their numbers, it was better to increase the ability to capture potential new users by eliminating anything that wasn't a value prop or CTA leading to conversion, and have all other types of users suffer a little bit with the hidden nav. But I'd like to challenge that it didn't have to be one or the other.

But who knows, maybe we're entering a new era with new paradigms.

"Cleaning the page up" is a misguided justification — a layout can be uncluttered without sacrificing the accessibility and functionality of the site. In no way do I think a cleaner page is reason enough to place their primary nav and their footer nav behind an icon and nowhere else. I'm sure that not an insignificant percentage of their visitors are going to be confused or irritated by the lack of clarity in the different user pattern, and the extra visual fixation leads to an otherwise unnecessary increase in mental and physical effort. It's just not good UX, and that inevitably translates to user pain and bad business.

At the very least, the removal of the footer is a huge mistake. Already there isn't a call to action at the bottom of the page to point the user to any sort of sign up flow, but now there's no way to travel back to the top, to any other pages, or even view basic information like contact or help.

I admire Squarespace as a company and think they build great products, but I just have to ask what they were trying to solve here, because I don't see how this new nav design could be helping their conversions.

Awesome, thanks for the all the responses guys.

One service that I discovered during my search which wasn't mentioned here was http://proto.io, which I haven't tried but is maybe something one of you folks might want to test out.

For iOS, I design in @2x with some considerations:

1) When in doubt, I use even numbers. For things like strokes, horizontal rules, etc. that can benefit from @2x I go 1px (0.5pt) but container sizes, iconography, spacing, etc I just go with measurements divisible by 2 (which is relatively easy because everything lives on a grid anyway). For any blending effects, I go even numbers but this can probably be finessed at non-retina.

2) Just because your iPhone 5 is Retina and you're using @2x, don't design at 1136px. I'm putting this here because I made this mistake, and had to made adjustments that could've been avoided once I realized that I was playing with bonus space that doesn't exist on non-iPhone5s

3) Know how you're going to create and deliver your assets in advance. Have a game plan. A lot of assets will benefit from recreating them at non-Retina sizes, but sometimes by planning in advance I can create @2x assets that can be resized in half and still look crisp.

Looks like the MBP or MPA with a display is the way to go. Thanks everyone.