responsive site quote
Out of context: Reply #11
- Started
- Last post
- 16 Responses
- jtb260
^ This is true, but I think he's just looking for an approximation.
The important thing is to evaluate how much time you think it's going to take you, and multiply that by your typical hourly rate. You could then mark it up another 15% just to be sure that you're covered for any finicky nit-picking. Though it would probably be better to include rounds of revisions in your proposal, and then say that it's $XX/hour afterwards.
Designing for responsiveness works best when there is a good working relationship between designer and front-end developer. Even if you're delivering set break points you might find that the elastic layout effects things strangely, and need to adjust after the fact. Having a way to cover yourself for these changes is good, just make sure the client understands that's the case.