I've been building TapShop, an Android app that turns a shared grocery list into one-tap product search links at whatever store you're standing in. I use AnyList to plan groceries with my household, but the list itself is just text — "2 lbs chicken breast," "organic cane sugar" — and turning that into an actual cart still meant retyping every item into a store's search bar by hand. TapShop closes that gap: share the list from AnyList, TapShop parses it, and every item becomes a link straight into your store's own search results.

The non-obvious part wasn't the parsing — stripping bullets, quantities, and duplicate detection out of messy pasted text is the kind of thing you'd expect. It was deciding what "search across 30+ grocery chains" should actually mean. Real cart integration — add-to-cart, checkout, price comparison — means an API or scraped auth session per retailer, which is a maintenance nightmare for one person's side project and probably breaks a dozen terms of service. So TapShop doesn't try to add anything to a cart. It generates a direct search URL and hands you off to the store's own site.

What makes that actually cover 30+ stores instead of just a handful is that most U.S. grocery chains aren't running their own e-commerce stack — they're reskins of a small number of shared platforms. Harris Teeter, Kroger, Ralphs, and Fred Meyer are all the same Kroger search URL pattern under different branding. Aldi, Sprouts, and Publix's delivery site all run on Instacart's white-label platform. Food Lion and Giant Food share Ahold Delhaize's PRISM search path. Once I noticed that, the problem stopped being "build 30 integrations" and became "identify the ~6 underlying URL patterns and map every chain to its family" — which is a much smaller, much more honest project.

It's in private testing right now, not on the Play Store, so there's no link to hand out yet. If you want to try it — you use AnyList or a similar list app and this sounds useful — reach out and I'll get you access.