Get the latest tech news

Nuances around location-based programming

A post discussing the nuances around location-based programming. Various ways to access user location, how they can fail, and what to do about it.

Breeding, Kentucky Burnout, Alabama Burnt Store, Florida Butternuts, New York Butthole Lane Carefree, Arizona Center of the World, Ohio Cheesequake, New Jersey Chicken, Alaska Chugwater, Wyoming Cookietown, Oklahoma Correct, Indiana Dick’s Knob Ding Dong, Texas Disappointment Islands Earth, Texas Eggnog, Utah Fifty-Six, Arkansas Funk, Nebraska Greasy Corner, Arkansas Hell, Michigan Hot Coffee, Mississippi Humptulips, Washington Idiotville Imalone, Wisconsin Intercourse, Pennsylvania Ketchuptown, South Carolina Kickapoo, Kansas Looneyville, Texas Moose Factory Mosquitoville, Vermont Neutral, Kansas New Erection No Name, Colorado Normal, Illinois Nothing, Arizona Peculiar, Missouri Pee Pee, Ohio Red Shirt, South Dakota Sandwich, Massachusetts Satan’s Kingdom Scratch My Arse Rock Slaughterville, Oklahoma Stupid Lake Sweet Lips, Tennessee Worms, Nebraska Zzyzx, California Anyway, if you decide to take this approach, it’s a good idea to either use a form control with pre-selected options (select or radio), or integrate some sort of auto-complete (location API). For the first render of the page, I think it’s safe to either use the default language or the best guess, but the key thing is to let the user decide which is best for them (maybe they only speak French) and honor their decision on subsequent visits.

Get the Android app