I'm thrilled to announce my latest book focused on designing web applications. After the success of my last book, The App Design Handbook, I had a lot of people asking me to write something specific to web applications. I actually started writing the outline for this book back in 2009, but it wasn't until a few months ago that I actually started writing.
First, good job! I hope to add "authored a book" to my resume some day.
Question, though: if this book is specifically geared towards web apps, why did you give it such an ambiguous name that mentions nothing at all about web apps?
Is your book about architecting applications (on a code level), or is the "design" relating more to the artistic definition of design? Judging by the sample content, it looks to have little-to-nothing to do with actual code, and mostly focused on UI/UX.
As-is, the title just seems really inaccurate; "software design", at least for me, is a very specific area which deals exclusively with UML and other code-level architectural concerns.
I guess we are using the same words to mean different things. I'll see if I can come up with a title that is more clear.
The book is focused on designing software from a user's perspective. That includes how the application flow works, making sure it is intuitive, and adding a layer of polish with colors, textures, and animations.
Software design has a very specific meaning to us programmers which is about the background architecture. It's a very confusing title.
Looks to be an excellent and interesting book though, I'm just doing the Human Computer Interaction course on coursera and I can see it being a nice addition to fleshing out some of the topics.
This is specifically about web application design, which I see as being quite different from web design. Many concepts are the same, but web applications require a different style of design.
So mentioning applications or software is important.
Cool, then it's not too late. I think with the current title you would miss much of your intended audience, while at the same time there would probably be complaints from CS-types.
Hi Nathan, perhaps this book isn't for me as a designer as much as it is for developers to ensure everything that needs to be there is there, but the modal popup having the action buttons before the messaging doesn't seem to make any sense from a UX perspective.
It looks really cool. Sorry to nitpick, but I think you should say "DESIGNING WEB SOFTWARE IS DIFFERENT from DESIGNING WEBSITES" (it might at least help with the British crowd)
Happy to answer any questions about it!