589 reputation
26
bio website
location Phoenix, AZ
age
visits member for 3 years, 11 months
seen May 14 at 4:12

Husband, Dad, other stuff...


Sep
24
awarded  Autobiographer
Dec
28
awarded  Yearling
Feb
14
comment How to communicate foreign key constraints in a business application?
While generally accurate; the user may care about the underlying data, depending on who the user is and who the application is targeting.
Feb
9
comment Do people respond more to $ off promos or % off promos?
The conversion rate is key. Misleading a consumer (can we say asterisk?) initially to gain interest will most certainly hinder the conversion rate.
Feb
9
comment Do people respond more to $ off promos or % off promos?
@Joe You need to clarify if you are concerned with clicks or purchases. While more people may click on a banner; it's irrelevant if the purchase is never made.
Jan
9
comment How does use in bright sunlight affect how a web site should be designed?
@TonyBolero They won't have interest? If they can't see your site due to the sunlight they will.
Jan
9
comment How does use in bright sunlight affect how a web site should be designed?
@dnbrv Agreed, however adjusting contrast, font size, etc... has been around before mobile and the Kindle. Certain paradigms transcend device type IMHO.
Jan
9
comment How does use in bright sunlight affect how a web site should be designed?
Many of these items you list are adjustable within a device like the Kindle. Be careful, assuming one flavor is sufficient for all may not in fact be the case. Make it adjustable if you can; coloring schemes, font adjustment, etc...
Jan
9
comment How does use in bright sunlight affect how a web site should be designed?
@Rahul You should know your customer base to some degree. Do you consider how easy a button is to select when my fingers are frozen due to me sitting at a bus stop in 0F weather and my gloves are the size of my shoes? The belief of design for everything always feels like a scholastic answer IMHO. Know your customer base and usage situations or you're shooting in the dark; the 80-20 rule.
Jan
6
comment Is there any in-depth data on tappability of touchscreen areas?
@PatrickMcElhaney There is certainly a fine line. It would be a judgement call and could go either way.
Jan
5
comment Merging firstname/last name into one field
If the DB is expecting the name as seperate fields then attempting to create a automated system to split the full name into its component parts Splitting a string is trivial. Getting accurate, useful data from a string of dynamic lengths and assigning a type to each portion is the difficult part.
Jan
5
comment Merging firstname/last name into one field
I think the UX would be pleasant but I think your data will quickly become dirty, more so than if you had the data fields separated. It is unfortunately impossible to deduce what someone wants to be referred to when they list their name as Joe De Maggio.
Jan
5
comment Is there any in-depth data on tappability of touchscreen areas?
@DanielNewman Everything plays a roll within UX. Ease of use viewing a screen when the sun is at high noon, the weight of a phone, the processor within the device, etc... It just feels more like an engineering question more so than a UX question. Worthwhile? Certainly, just not for this site IMHO.
Jan
5
comment Unit of measure and Quantity in Purchase Orders
@jberger It's contingent on the application; however I would lean to storing the data outside of the client with a cached copy locally so that is is reachable across multiple devices and platforms.
Jan
5
comment Unit of measure and Quantity in Purchase Orders
@Sparafusile Once the user enters the amount, that can be stored and referenced by the application at a later point in time. The key here is uniqueness and making certain that you can guarantee uniqueness between the vendor data (however that is obtained) and your application. This is partly why I believe this is an architectural problem more so than a UX. Once the architectural approach is determined, I think your UX will surface fairly naturally.
Jan
5
comment Unit of measure and Quantity in Purchase Orders
@Sparafusile I'm not intimate with your application and how data comes in and goes out so this is a bit difficult to answer. The concept of templates needs to remain that, a concept. If this can be handled automatically by the application since it interfaces with these vendors and pulls the data in then by all means do so. Let's say we have Vendor A. If the application is pulling in what Vendor A carries, then at each unique encounter you could ask the user to enter the relationship to product. We have not seen this unit before. How many cc does 'pallet' equate to with this vendor?
Jan
5
comment Unit of measure and Quantity in Purchase Orders
@jberger That is an architectural decision outside of this scope.
Jan
5
comment Unit of measure and Quantity in Purchase Orders
@jberger If the unit of measure varies incoming and outgoing, then the first problem is Sparafusile stating to the customer to treat this as the unit which they sell or consume as that is not the case. The goal of the UX should be to minimize the impact of the translation to the customer. Templates as mentioned previously is one way to go about this. The customer may purchase in pallets but unless their business is destined for failure they know how much product exists on that pallet as well.
Jan
5
comment Unit of measure and Quantity in Purchase Orders
@Sparafusile If the purchasing unit of measure does not equate to the selling unit of measure, someone has to do the translation. Either the application or a user. If the unit of measure is 1 bottle from the manufacturer, is this auto-populating within your application? Does the user say I purchased 1 bottle manually? Allow the user to set up mappings, templates if you will. Make them easy to edit and maintain. You can leverage the users intimate knowledge of a vendor to do the translation for them. MyTemplate1 (1 btl = 1000 cc) or something similar.
Jan
5
comment Unit of measure and Quantity in Purchase Orders
@Sparafusile Back to my answer, you state to label the unit of measurement as you would consumer or resell, not purchase. I'm confused as it sounds like they are violating this principle.