>Ask the user to select a location. I may want to know the nutritional facts about an item somewhere else. Say I'm traveling there.
At the time, it was only National in the USA. You could lookup different stores to get menus after the app determined your closest store.
>Have websites in different countries: like if I go to macdonalds.co.jp, I get the nutritional facts in Japanese about the Japanese Big Mac.
I believe they do this now.
At the time it was implemented, there wasn’t a bias like there is today against location API’s. They hadn’t been used (yet) for tracking purposes outside of maps and what we were doing. No ad based geo fencing and location sharing.
The big issue is QSR’s are fast food. Fast food must be fast. Under 10 minutes. Any select, drop down, input box to enter in your address, added extra complexity to the checkout ordering process during our focus groups. Having an image of the item, add to order, checkout to nearest store, results in a 10x reduction in ordering time. It makes the user experience of the ordering process streamlined and smooth and operational from your vehicle with one hand.
I would build the same system today.
