LifeExplorer is a real-world discovery app. Point your camera at something alive and it tells you what it is. Point it at a city block and it tells you what's worth your time. The thesis is that both of these are the same action.
Discovery is a behavior, not a category. People who stop to identify a bird on a trail are the same people who want an honest read on a neighborhood bar — they're curious, they're present, and they distrust algorithmic feeds that optimize for engagement over truth.
Every app in this space picks a side: nature or city. LifeExplorer's bet is that the overlap in user intent is large enough to make a single app with two modes better than two separate apps.
Species identification via camera. Powered by iNaturalist, Merlin, and on-device ML. MVP-first — this is the wedge.
Urban discovery with an implicit taste graph. Check-ins build a preference layer that improves recs without requiring explicit ratings.
The nature-app market has Seek, iNaturalist, and Merlin. The city-discovery market has Yelp, Google Maps, and a graveyard of failed social check-in apps. Both are crowded. Neither has been approached as a behavior-first product that happens to surface in two contexts.
CaptureLife — the in-app AI identification engine — logs every identification event. Over time, this is a proprietary dataset of what people find interesting in the real world, timestamped and geolocated. That's the licensing play. Universities, conservation orgs, and urban planners pay for behavioral data at scale. Neither Yelp nor iNaturalist has cross-context behavioral data.
WildLife: iNaturalist API + Merlin (Cornell Lab). CityLife: Google Places API + a lightweight taste-graph layer in Supabase. CaptureLife wraps both with a unified camera interaction model — same gesture, different classification target.
Revenue model: freemium consumer with institutional data licensing as the B2B layer. No ads in v1. Ads would poison the taste graph signal before it's worth anything.
Concept / ideation phase. WildLife is the MVP — narrow scope, proven API surface, clear user value. CityLife follows after WildLife has traction. No code written. No timeline committed.
Is the overlapping user cohort large enough to justify one app over two? The answer is probably yes — but only if the mode-switching UX is so frictionless that users don't notice they're crossing contexts. If it feels like two apps bolted together, it is two apps bolted together, and the thesis falls apart.
That's the design risk. Everything else is execution.