Synap Software Blog

Making of a Web App: Interlude - Importance of a Blog

by Scott on July 16, 2007

In Startup Marketing: Big Bang vs. Darwinian Evolution, Dharmesh Shah highlights the importance of getting feedback early in a Darwinian evolution approach compared to the “stealth mode” approach with a big-bang launch. His insights are well stated and recommended reading to show the design and development of a new product should be accompanied by, or even preceded by, a regularly updated blog that reaches your intended audience. I recommend you read it, and if starting a new product, create and regularly update a blog about the product.

Making of a Web App is Synap Software’s blog about our upcoming web-based sales team collaboration app.

Posted in Sales team collaboration, Making of a web app, Make a Web App

[0] comments

 

Making of a Web App: Part 11 - Technical Interlude

by Scott on July 03, 2007

For people with an interest in the technical side of the project, here are notes on the configuration of our development, test, and production environments.

For those who couldn’t care less if PlaybookIQ is powered by mongrels or mice – don’t run away yet. Later this week, I will have the beginnings of actual product on the “production” server where anyone interested can follow along in real-time as updates are made throughout each development day. I would love ongoing feedback from the “live” site. Stay tuned because some real stuff is starting to happen.

Read more...

Posted in Sales team collaboration, Make a Web App, Making of a web app, Programming

[7] comments

 

Making of a Web App: Part 10 - UI Evolution and Screenshots on Flickr

by Scott on June 28, 2007

Making of a Web App is Synap Software’s step-by-step look at designing and developing a web app. In this article I share one iteration of an evolution of web application design layouts for PlaybookIQ.

I set up a flickr photostream to show screenshots as they evolved. Read the rest of this blog entry first, and then go check it out.

Key points of visual design for web applications stated as expectations from people using your application:
  • Proximity: items near each other are related to each other..
  • Relative size: larger elements are more important.
  • Relative position: elements to the top and left are more important. Elements to the bottom and right are subsets of ‘parent’ elements above and to the left of them.
  • Consistency: consistent fonts and colors make an application feel more reliable and well constructed.
  • Inconsistency: an occasional inconsistency should mean that something is important or needed to be called out for some reason (e.g. red text when all other is black).
  • Persistent elements like ‘home’ or ‘search’ provide confidence to roam around knowing they can always get back to familiar territory.
  • Sign posts: let people know where in the app they are.
  • Alignment: an application in which elements line up neatly vertically and horizontally feels more professional, is more trustworthy, and easier to use.
  • Whitespace is easily understood as way to separate elements that are not directly related, while a line, shading or other elements must be processed by people scanning a page.
  • Context is critical. Metaphors like tabs, sign posts, and grouping help people understand what to expect at a given point in the app and helps people focus on one thing at a time.
  • Choice is painful and slow. People simply want to get something done. People do not want to be asked to perform the work of making choices. Keep navigation and activity choices to a minimum.

Read more...

Posted in Make a Web App, Synap Software: Design Decisions, Making of a web app, Web Application Design

[6] comments

 

Making of a Web App: Part 9 - Why I Hope No One Reads My Use Cases

by Scott on June 21, 2007

Making of a Web App is Synap Software’s step-by-step look at designing and developing a web app. In this article I share why, despite best attempts by the anti-paperwork crowd, I like written use cases.

Use cases:
  • Contribute directly to the final, deployed app.
  • Expose risks to simplicity.
  • Expose the level of development work required.
  • Are the easiest way to iterate, collaborate and communicate.

Use Cases

Briefly put: a use case can be anything that documents how a person will accomplish a task with your application and how the application will respond. In this article I use the term to mean written use cases (as opposed to diagrams or sketches).

Click here for an example.

Some developers do not write use cases because doing so feels too much like writing documentation and documentation is not the purpose of building a system. So, in an effort to work only on things that directly contribute to building the app, people skip over the use case step and jump right to visual design or sketches (or even just start hacking out code). I have to say that back in my developer-only days, I was that way too. I saw anything but code as wasted time. Now, I don’t. Here are four reasons why I don’t skip the use case step.

Read more...

Posted in Making of a web app, Programming, Web Application Design, Make a Web App

[2] comments

 

Making of a Web App: Part 8 - Styleguide

by Scott on June 18, 2007

Making of a Web App is Synap Software’s step-by-step look at designing and developing a web app. In this article we get a little bit ahead of ourselves and talk about styleguides.

Early PlaybookIQ Styleguide decisions:

  • Use of the International Style
  • Tab-based navigation
  • Persistent search box

Read more...

Posted in Making of a web app, Synap Software: Design Decisions, Make a Web App | 7 trackbacks

[0] comments

 

Other posts: 1 2 3