I came up with a proof-of-concept alternative loading strategy that didn’t block rendering, instead opting to load the assets asynchronously in exchange for a flash of fallback text (FOFT), akin to implementing font-display: swap;, I was told Customers overwhelmingly prefer to not have their pages load sans-fonts and then “pop” into place with the correct fonts… which, of course, I, every async font loading strategy, and the entire font-display/Font Loading spec disagree with.

THIS is the crux of the problem right here and something NOBODY has been able to solve yet. I'm one of the people who prefer to wait for the font to load and not have the content jump around on the page. I absolutely loathe reading a page's content when it loads only to have the FOUT change the location of words on the page. syfy.com does this and it's maddening.

If this were an XD update, the tone here would be a lot different for such a simple feature like this.

Duh. Shiny new tools and hipster "designers" can't be caught using the same thing as everyone else. How could they sound special at their conference sand meet-ups otherwise?

Abstract enables you to track the who, what, why, and when of every design decision...IF you're using Sketch. It even says on the website, "One place to version, manage, and collaborate on your Sketch files." If you're using Adobe XD, Affinity Designer or anything else really, you're on your own.

I really wish more developers would create these plug-ins for other browsers as well. Not everyone uses Chrome. I use Safari (excellent cross-device support with my iPhone and iPad) and I know a handful of other people who prefer to use Firefox.

Not everyone uses Chrome and is not thrilled about the prospect of handing over our data to Google willingly. There is no reason why the hero video shouldn't work in Safari and it's a sign of sloppy development when things like this fail to work correctly. At a minimum, if the video fails to load a static image should load in its place.

I want to upvote this by infinity. I love my iPad Pro but I HATE having to charge the pencil. I really want to upgrade to the new iPad Pro just to charge my pencil like a normal person.

UPDATE: I should note that I only plug the Pencil into the lightning port when it very rarely decides to not sync. I use an inverter plug to charge it on the end of a lightning cable.

Some of this could due to unfamiliarity to Publisher but if it's not intuitive, to begin with, that's a knock against it in my opinion. I liked the direction table styling was headed but tables, in general, were not well implemented. One feature I use in InDesign ALL THE TIME is spanning tables across multiple frames. I've had documents where a single table takes up 5 or 6 pages. In InDesign, the table head repeats when it breaks across the page and the content continues to flow. Publisher appears to require a table on each page which means when you need to make updates you will need to move a lot of copy around as the table rebreaks.

InDesign allows you to mix multiple page sizes n a single document. This is handy if you want to layout something a gatefold or barrel fold brochure where successive pages are trimmed ~.125" smaller as the page folds in. This lets you set columns and margins consistently across all master pages easily. I didn't see a way to do this in Publisher.

Binding along the top edge was a nice feature that I'd like to see officially supported in InDesign. I've been able to hack a solution together but PDFs don't export the file properly.

Paragraph styles were a mess in Publisher. I loathe Word and implementing paragraph styles, in the same way, was a huge mistake. InDesign has limitations and I've developed methods to work around only allowing a single character style applied a text at a time but I'll take their approach any day. I realize you can create custom styles but let me start with a clean slate and decide how I want to structure and name thngs.

A lot of other issues really stemmed from nearly two decades of experience with InDesign and all the other Adobe Creative Suite apps. There's a lot of muscle memory with keyboard shortcuts, app preferences, and general workflow that just made working in Publisher a chore. I don't love InDesign like I once did but I didn't see anything in Publisher that would make me want to ditch the Creative Suite.

I found it to be a mixed bag. There were things I definitely liked and things I despised. Too many of the latter and not enough of the former to make me want to switch.

I really do hope they come back and answer your question. I've always wondered why Adobe never started developing a common codebase for their developers to handle common functionality across apps.