Anyone can follow a list of procedures, when do I get to make a difference? Can’t I just spend my time automating this?
I hate it when Web developers ignore analytics. It tells exactly what browsers and devices to design for.
Create a sound solution and let the user accomplish what they set out to do. In order to do that I have a set of key points I hold up and get others to buy-into as the development process starts.
It is always best to keep user submitted forms simple, as a recent episode of This Week In Google on the TWiT network recently explored live, on-air.
I preach the benefits of change, but when it takes over a year to adjust to a new method, something is broken. Something is flawed.
Adding new features is like getting a pet. Feature ownership can be very rewarding, but do you have the support and resources to take on such a commitment?
I have a suggestion for a popular calendar application when it comes to recurring events. Allow the user to select a third option: designate a day of the week in the nth full week of the month. As you can see in my screenshot I have the ability to select two options in date selection […]
When designing web or app functionality steps to be taken by the user, write out the steps, read the steps out loud, and see if at any point you stop and go, “this is ridiculously long.”