I take your point about the ease of entering numbers on phones - although that may become less relevant as smart phones take over the world (on my low-end Android phone for example it's easier to enter letters rather than numbers in web forms).
My CouponCode algorithm embodies a number of trade-offs. I went for a base-32 encoding scheme to increase information density while avoiding having to use upper and lower case characters. The checkdigit on each part then adds extra data entry overhead but hopefully the instant feedback benefits outweigh that.
With a numbers only code, the base-10 encoding would significantly reduce the information density. So a 4-digit part could only encode a key-space of 1000 possible codes vs 32768 for my alphanumeric codes. To get the same keyspace as my three part codes (XXXX-XXXX-XXXX) a numeric-only code would need 5 parts (XXXX-XXXX-XXXX-XXXX-XXXX) which is probably a bit unweildy.
In reply to Re^2: RFC: Algorithm::CouponCode
by grantm
in thread RFC: Algorithm::CouponCode
by grantm
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |