Live design review: Walking through Workbook 

You should at least highlight the diffs in the version comparison.

This is great! I noticed this is already in a test environment, already in code as opposed to reviewing Figma designs. Is your process that you don't review until code exists already? Or do designers prototype in code for review? As a designer I'm often worried about making sure my designs are 'production ready' before an engineer touches it.

Can you include this interface into basecamp documents?

Personally I found the animated auto save a little distracting. Whilst typing, I want to be looking at the text, and not be distracted. I like auto save, and I like the idea of being able to tell that there are changes from when I started this edit session, but just don’t like the constant start and stop of the animation.

Exciting! This is a really great video. I love listing to quality design review.

It's just for books or are planning to build a master scenes screenplay editor?

Great video! It’s fascinating to see this process. A couple things I thought: If a document has been autosaving the whole time, I’d expect clicking the green save icon to function like a save and exit (because I’m probably only going to click it when I’m done editing). Also I’d be interested to hear why the back button, which I think navigates to the previous page, is not located at the bottom with the button which navigates to the next page 🤔

Love it. More of these behind the scene please ✨

That’s the most well thought out marketing campaign ever. Increase the number of people that host their own thing by first thing is affordable, second and third away free, the 4th will change the market. So in boxing terms this is a 2-3-2-3b. Can’t wait for the hook to the body. 🥊

I think the 'Saving' is a bit confusing. It's visually pleasing but it's auto-saved anyway. Why give editors a sense of unsaved work when it's saved already? Also, when you click 'Save', there is no feedback that the work was already saved. Editors will not learn about the saving mechanics so they'll probably repeat this unnecessary action.

Looking sharp! Excited for this project

Very cool insights on the design process. Really looking forward to see and try out the product as well - Thank you for sharing what goes on behind the scenes.

At 7:20 when prior version and current version are side by side.. I immediately want to see an “overlay” action where the two versions converge, with the new one in green and the old one in red. When they overlay and match, the text goes black. When they differ, you can immediately see red (old) versus green (new). A figure vs ground graphical indicator. Not sure if it would be as powerful with text as it is for something like a floor plan* but I want to see some kind of highlight to identify the difference between the iterations. *I use this function frequently in a software called Bluebeam PDF Revu for architectural drawings. Overlaying iterations is tremendously useful.

The interface is really minimalistic and seems for me to not require a zen mode at all, like other editors. I can easily imagine myself writing freely in it instead of using some kind of text editor in between my thoughts, my externalized output and the finalized form. There are few design problems I’ve seen while watching the video. 1. Problems with the placements of the rewind and forward buttons + bottom part of a page: Jason Zimdars has multiple times clicked the arrow left (I call it „rewind“) button to go back to the previous position of his navigation path. Nearby of the rewind button is the back button of the browser and on many PWAs the same or very similar position is occupied by a back button as well which makes the position preoccupied by existing concepts. In the same time, the arrow right (forward) button to flip forward is placed to the bottom, which looks like not associated with the rewind button at all, although they address the same category of interaction. I overlooked also first the forward button. The second issue is similar to what Jason Fried mentioned with the date: seeing the UI, I ask myself if I can write longer texts than to the position of the forward button. And when I write more, my eyes will stick more to the bottom because there is the line I am currently writing. Having the forward button positioned there might draw my attention too much to the button than on my text. The design pattern of old kindle books flipping pages with vertically positioned buttons on the left and on the right of the page side could be used here to create an association between the rewind and forward buttons. Placing the buttons vertically centered or at the bottom could make use of the familiar placement pattern, too, resulting in a more intuitive understanding. It also frees up the bottom creating a sense of a vertically infinite canvas. 2. Problem with the forward button and the last page: On the last page, the behavior of the forward button changes to „back to overview“ button. This took me by surprise since I haven’t realized that the current page watching was the last page. I assume the rewind button has the same behavior when being on the first page. There are multiple options to solve this with caveats: 1. the interface shows a page count while being on the page so I can assume that the current one is the last page. 2. the icons on the buttons for the first and last page change to indicate a change of action which I need to learn to recognize and understand once. 3. the actions could be changed to add a new page which might result to a faster creation speed but also to dead white pages. 4. the buttons are hidden on the first / last position which results to a visually uneven UI on those pages. 🥪

Was thinking exactly the same as Jason on the save button, good call.

Great job guys, this looks awesome so far

Thanks for uploading this folks!

This looks fantastic