30% planning, design data model, etc 25% Back end code (only the major part of it) 15% Client-side design and code (if it matters for the app I may spend more

30% planning, design data model, etc 25% Back end code (only the major part of it) 15% Client-side design and code (if it matters for the app I may spend more time here) 10% Integration At this stage if I was fooling myself I'd say I'm done. but this is just a prototype and I have only tackled the major parts of the application. There are lots of details that are laying around even though everything looks as if I'm done. At this stage it may look like your productivity is low but it is actually part of. So you have to do some tests step back and look at the whole thing and find that you have to spend another 10% modify things 30% to deal with little seemingly useless fixes or just making things look nicer or adding content etc. If I'm spending more time in any of these stages either I am being lazy or I didn't do the previous stage correctly and it is effecting what I'm doing now. so I stop and go back. it's better to cut your losses early or you'll really loose productivity and develop something bad. here is a tip to be more productive: When you get tired of thinking switch to graphic design and when you are stuck with a design idea switch to writing code and when you are thinking about your idea write content especially help files (even of an unfinished app). You'd be surprised how this may actually effect your own views about your ideas.