A better user interface

Have you been to the Canada Post Postal code lookup site recently?

 

Go ahead, check it out.  I’ll wait.

 

From a developer perspective, this form makes perfect sense.  Each box is a part of the data to ask for, then you check for mistakes, combine it all up check what the postal code is for that location.

 

But to me, that’s an old way of thinking about it.  Why can’t I just have a box that I type stuff into?  Websites are smart enough to figure out what we are trying to write.  Find the province, figure out if I wrote “street” or “crt” or whatever, and present me the two or three likely options.

We Can Eat Here is trying to do better where we can.  Drop us a line if you have suggestions.

 

Food allergen detector – not there yet

I found a great “design concept” (read — brainstorming idea) of a Food Allergen Detector (via Laughing Squid). The concept here is a little device you carry with you to restaurants.  Red: bad.  Green: good.  Couldn’t be simpler, right?


Personally, I can’t wait for such an idea to develop, but I’m not convinced it ever will.  I worry that any company that would consider building such a detector couldn’t cover the risk of being sued in case the detector failed, even once.
Consider that: if your tool makes one mistake, it could be all over.  That’s the risk with allergies and sensitivities.  And would people ever fully trust such a tool?  I suppose a glucose-monitor is a similar analogy.  As more people get more information and learn about how to cook for allergies, we all win.And until the day that a silver-bullet allergen detector can be made (if at all?), we all need to continue to be vigilant.