3 ms·

Wow, I like your app a lot. Its beautiful and the idea is very good. I am co-founding a startup and much of the design work will be done by me. Would you be wi

by csmeder 17y ago

Wow, I like your app a lot. Its beautiful and the idea is very good. I am co-founding a startup and much of the design work will be done by me. Would you be willing to share any tips? What I would really like to know is how are those 160 hours spent? (160hours*$75=$12000) The software life cycle is well documented in a number of methodologies: XP, iterative, water fall etc. But when it comes to the design phase of a web app I feel left in the dark. What I am wondering is what techniques are you using during those 160 hours, in what order and what percentage is spent on each? ---------------------------------- For example: (a quick guess) it would be something like this: - gather requirements - 10 hours - draw mock ups on paper - 20 hours - draw prototypes in illustrator - 20 hours - make designs in illustrator - 50 hours - review with customer (self)- 10 hours - iterate on designs in illustrator - 50 hours ----------------------------------- Do you have any tricks of the trade (http://www.themorningnews.org/archives/how_to/tricks_of_the_trade.php http://www.themorningnews.org/archives/how_to/tricks_of_the_...)?

oneplusone 17y ago
At Guestlist we believe in short iteration and customer feedback. The best advice I can give you is to ignore the waterfall method of design that would have you believe you need to "gather requirements, sketch, create wireframe, etc." in order to be successful. There is value to such a method (if only to create a paper trail that you can use to sell your design) when you are working for clients, but when you are a co-founder the absolute best way to go about is to simple do it. Start with a specific section of your app and create a mockup in Photoshop. Work on it until you are happy and then implement it. Don't do 10 different variations. Don't worry if you don't know how everything is going to fit together. Just get it working so you can move onto a different page. The first designs we implemented at Guestlist were pretty terrible in retrospect. It had a lot of fatal logic flaws. We had no idea what our initial feature set would be. We knew we needed a public event pages so we started there. However, as we added more and more pages we realized our first couple of pages where shit so went back and iterated over them. Given enough time and iterations things will start taking shape. Just take a look at the very first mockup I did: http://dl.dropbox.com/u/410315/event.jpg http://dl.dropbox.com/u/410315/event.jpg It looks nothing like what we currently have. For reference here is the current public page: http://guestlistapp.com/events/7311 http://guestlistapp.com/events/7311 Now, it may seem like you could follow the 37Signals route and simply skip the Photoshop step altogether and get to using it faster. _Don't do this._ You cannot be creative with CSS. The Photoshop stage gives you a chance to do crazy things and not think with boxes. This can also be applied to websites. The current Guestlist website is very weak in my opinion. It was created over a weekend. There is a much improved version in the pipeline. Not a radically different site, but an evolution that iterates over the weak areas. The key is to never stop iterating. Never lock down the design. Never let somebody tell you you can't do something because it's inconsistent with the rest of the site. Just change the rest of the site too! Design must evolve constantly.

by csmeder 17y ago

oneplusone 17y ago

At Guestlist we believe in short iteration and customer feedback. The best advice I can give you is to ignore the waterfall method of design that would have you believe you need to "gather requirements, sketch, create wireframe, etc." in order to be successful. There is value to such a method (if only to create a paper trail that you can use to sell your design) when you are working for clients, but when you are a co-founder the absolute best way to go about is to simple do it. Start with a specific section of your app and create a mockup in Photoshop. Work on it until you are happy and then implement it. Don't do 10 different variations. Don't worry if you don't know how everything is going to fit together. Just get it working so you can move onto a different page. The first designs we implemented at Guestlist were pretty terrible in retrospect. It had a lot of fatal logic flaws. We had no idea what our initial feature set would be. We knew we needed a public event pages so we started there. However, as we added more and more pages we realized our first couple of pages where shit so went back and iterated over them. Given enough time and iterations things will start taking shape. Just take a look at the very first mockup I did: http://dl.dropbox.com/u/410315/event.jpg http://dl.dropbox.com/u/410315/event.jpg It looks nothing like what we currently have. For reference here is the current public page: http://guestlistapp.com/events/7311 http://guestlistapp.com/events/7311 Now, it may seem like you could follow the 37Signals route and simply skip the Photoshop step altogether and get to using it faster. _Don't do this._ You cannot be creative with CSS. The Photoshop stage gives you a chance to do crazy things and not think with boxes. This can also be applied to websites. The current Guestlist website is very weak in my opinion. It was created over a weekend. There is a much improved version in the pipeline. Not a radically different site, but an evolution that iterates over the weak areas. The key is to never stop iterating. Never lock down the design. Never let somebody tell you you can't do something because it's inconsistent with the rest of the site. Just change the rest of the site too! Design must evolve constantly.