Thread

Blasted IE 6 & 7 ... anyways ... when do you test browser compatibility? I guess it would be nice to start at step #1, but when you client is the type that makes ass loads of knee jerk changes, I find it too much to test at the beginning.

[rant]I’m not sure if this helps or hurts me ... as I’m expected to pretty much work in overdrive mode 24/7. [/rant]

As soon as my design is ready I test it with all browsers I got my hands, currently that’s Chrome, Safari, IE and FF. By testing I mean surfing the side and looking for parts that look nice in FF but not in the other 3 :D

The other parts of creating a website (mainly the coding) should not depend on a specific browser and therefor needs no real intense testing in different browsers, FF is enough for me 😊

All the “knee jerk” changes clients will try to make is precisely why I have set up a “system” of handling client requests.

First things first, and that is I talk it over with the client, and record the entire conversation so there can be nothing like “but I said” because I’ll have a recording of it.  Then I write up what the client is wanting and include a flowchart or UML diagram of an overview of the functionality of the application.  Once this is approved, I will give a quote for the “application” programming, and let them know if once we reach the “design” phase if they want a great deal of fancy design, it will increase the price a bit, and go over with them what things will affect the price.  They don’t even get an initial quote until they have “agreed” to the contract with their signature on the line.  That way, if they start making changes, I start adding quotes to each change.

I also wait until the application is complete according to how they originally approved it before they get a chance to see it and test it.  This also prevents a lot of changes along the way.  Initial customer testing is done in simple views where a “design” has not yet been applied.  Once the functionality has been approved, the application is then “skinned” so to speak, where the design will be approved and applied. 

Generally speaking, the browser testing comes into play at the point that the application is being skinned.  Session handling and other “non-display issue” browser testing is done before the client approves the application itself.  Browser display testing is done once the application has been “skinned.”

This generally works for me very well.  Others, I am sure, will have other opinions on the same subject.

[rant]I’m not sure if this helps or hurts me ... as I’m expected to pretty much work in overdrive mode 24/7. [/rant]

Ok, you probably don’t expect a response to this part, as it wasn’t really part of your plea for help, however, this was a sore spot with me in the past, and I will address it.  Take or leave anything I say for the rest of the post.

I had the same expectation for my first few clients.  Since I am a freelancer, I now let the clients know up front what my time limitations are, and what they can expect certain tasks to take time-wise.  Being up front with this will help the client be more patient than they would otherwise.  If a client insists on my operating in 24/7 mode right away after explaining the time restraints, I generally will politely ask him to find another developer.  If he decides half-way through the project that he needs me in 24/7 mode, then I will evaluation the reasons for his request, and tell him I must recieve approval from my “business partner” first.  Then I make sure it is ok with my wife and family.  If it is ok with my wife, then I proceed to give the client a quote for the 24/7 mode, which is approximately 3 times my normal rate, and explain to him that this is the extra cost for expediting an application. 

Why do I do that?  Because my life is good, and I have a priority that my family always comes first.  I provide well enough for them.  You can always earn more money, but you can’t ever get back time lost.

Ok, I know I ranted more than you did.  Sorry about that, but I feel there is some good advice there as well.

well, all contracts are different, sometimes they aren’t contracts but jobs (or perm contracts) (and not in a design company) and often things are dictated by people who don’t give a **** about you process/methods.

also ... sometimes it’s not an app ... sometimes it’s a bastardized landing page, that you wouldn’t put your name on because you wouldn’t want to anyways! i could rant here.

i’m just asking why some may or may not feel that you need to code with 3 browsers open at all times.

as a rule, i try to keep things simple anyways… but then a misc float nightmare pops up.

well, all contracts are different, sometimes they aren’t contracts but jobs (or perm contracts) (and not in a design company) and often things are dictated by people who don’t give a **** about you process/methods.

I’ve been fortunate enough to be able to pick and choose so far.  Of course, a tad bit of financial stability will give you that luxury.  When times are lean, choices are no longer choices, but things that simply must be done.  I hope things improve for you on that front.

i’m just asking why some may or may not feel that you need to code with 3 browsers open at all times.

as a rule, i try to keep things simple anyways… but then a misc float nightmare pops up.

I don’t code with multiple browsers open.  I try to use CSS templates that are cross browser compatible, and just test it (with all major browsers) and tweak it when I’m “finished”.  Once the final tweaking is done, then it’s all done.  Browser testing pretty much comes into play at the very end for me.  If you’re using a solid template or framework for CSS to start with, it shouldn’t be a very large issue.