What to Eat for Lunch

Overview

I conceived and developed WhatToEatForLunch.com as a playful solution to an everyday problem: *Where should we eat?* The implemented web experience turns local restaurant discovery into an interactive decision rather than another list of search results. At its center is a location-aware digital wheel that helps users quickly discover nearby lunch options, transforming a repetitive decision into a fast, visual, and engaging experience. I led the product concept, UX/UI direction, interaction model, and development, working closely with v0 as an AI development partner to rapidly move from idea and interface exploration into a functional web product. Beyond the implemented website, I explored a broader physical + digital local discovery platform: Raspberry Pi-powered digital signage for offices, hotels, and public spaces; touchscreen discovery; and NFC interactions that could transfer an experience from a shared display to a personal device. The concept also considered expansion into coffee, nightlife, shopping, and other local experiences, with possible business models involving local advertising, affiliate relationships, and SaaS-based digital signage. These elements remain product and business explorations rather than claims of deployed functionality. WhatToEatForLunch demonstrates my approach to AI-native product development: combining an original business concept, UX strategy, working software, and emerging interaction models while keeping future concepts distinct from the released web experience.