
Reducing barriers to essential services with the help of AI
Summary
Opendoor is a mobile app designed to help people find and access local shelter, meals, and support services in minutes, cutting through the fragmented, outdated resources that used to make this search take hours.
My Contribution
I co-founded Opendoor, leading the entire end-to-end design as we reimagine the concept as a nationwide, AI-powered resource aggregator. I've led designs for 3 core user flows across 10 screens for iOS and Android.
Timeline
From May 2025 to January 2026
Team
1 Product Manager
3 Designers
2 Engineers
Skills
User Research
Interaction Design
Prototyping
Usability Testing
Tools
Figma
UserTesting
Claude Code
Gaps in access prevent people who need them most from connecting with available local resources.
This problem surfaced while auditing the Good Samaritan Shelter website: even after finding the right service page, users had to scroll through 4 screens before reaching eligibility requirements, one of the first things people need to know before calling or visiting. That audit became the foundation for Opendoor, rebuilt as a mobile-first experience designed around clear information hierarchy from the ground up.


Our core user on average had to spend 20+ min searching 4+ sites to find a single relevant service.
Through 13 stakeholder interviews and surveys with 50+ program respondents ( conducted during our initial research for Good Samaritan), two patterns surfaced consistently. Users were spending time searching across 4+ fragmented, outdated sites just to find one relevant service, and when they arrived, critical information like eligibility requirements, walk-in hours, and what to bring was either buried or missing entirely.
Key Insights
48%
Reported a wasted trip due to missing or unclear eligibility information
20+ minutes
Minutes spent searching, on average, per service found
4+ sites
Sites were visited on average before finding one relevant service
87%
Rely solely on a Lifeline-subsidized phone for internet access

Competitive Analysis
Current solutions fail to serve people navigating financial strain with local, contextual needs.
The patterns from our Good Samaritan research pointed to a gap larger than one shelter's website. Existing directories like 211 and FindHelp aggregate resources but are hard to navigate, while general tools like Google Maps and Yelp are easy to use but aren't built for the specific, often urgent needs of vulnerable populations. Opendoor was built to sit in the gap between the two: a resource finder that's both comprehensive and genuinely easy to use under pressure.

Our Bet: Conversational AI to reduce staff burden and personalize support as needed.
To maximize impact with limited resources, we categorized potential features into an impact matrix, prioritizing AI search and offline access as critical 'Big Bets' while cutting low-value friction like forced account creation. This helped us focus our time on the features most likely to improve access for users, rather than spreading resources across every possible idea.

Using AI to speed up early ideation
To explore direction quickly, we used AI to help generate and iterate on multiple early concepts in parallel, ranging from a simple hotline-first layout to a guided chat assistant, a map-based explorer, a categorized directory, and an action-plan checklist. This let us compare structurally different approaches before committing to a direction.

Defining the core MVP user flow by identifying what to prioritize and intentionally cut.
Before designing any screens, we mapped every possible user action and narrowed the core experience down to three core MVP flows: the homepage, service details, and conversational AI search, with supporting features like offline access, bookmarks, and accessibility settings built around them.

Design Systems
Building out a WCAG 2.0 Accessible Design System
Opendoor is a mobile platform that helps 5,000+ vulnerable residents in Santa Barbara County find and access local shelter, meals, and support services in minutes, cutting through the fragmented, outdated resources that used to make this search take hours.

Over the course of 8 weeks, we designed 10+ screens, 26+ components, built for Android and iOS.










