Neibo

Neibo had built a neighborhood social platform with a clear mission — connecting people in their local communities. However, despite strong initial downloads, the app suffered from low retention and minimal meaningful engagement. Users were signing up but not returning.

The existing experience treated community interaction like a social media feed, which created passive consumption rather than active participation. The onboarding flow didn't establish community context, and users struggled to find relevant local content or people.

• 70% of users churned within the first two weeks
• Feed-based design encouraged scrolling over participating
• Onboarding didn't surface community value or local context
• Event and group discovery was buried under generic content

Focused research on understanding the gap between download motivation and actual usage behavior. Combined quantitative retention analysis with qualitative exploration of what "community" means to different user segments.

Research Methods

• 10 in-depth interviews with churned users and 6 with power users
• Cohort analysis of retention patterns across different neighborhoods
• Diary study with 8 participants over 2 weeks to track community behaviors
• Competitive analysis of Nextdoor, Meetup, and local Facebook Groups

Key Insights

• Users who joined a group or attended an event within 48 hours had 3× higher retention
• The "aha moment" was seeing a neighbor they recognized — proximity alone wasn't enough
• Users wanted structured activities (events, polls, requests) more than open-ended posting
• Trust was built through shared context (same building, same school) not profile completeness
• Power users acted as community catalysts — their activity predicted neighborhood engagement

Shifted the core interaction model from "scroll and consume" to "discover and participate." The strategy was built around accelerating users to their first meaningful community interaction within the first session.

Designed around the concept of "Community Catalysts" — identifying and empowering the most active neighborhood members with tools to create engagement, while lowering the barrier for passive users to take small, meaningful actions.

• Onboarding redesigned around local context: "Here's what's happening near you"
• Activity-first home screen replacing the generic social feed
• Micro-engagement patterns: quick polls, neighbor endorsements, event RSVPs
• Catalyst toolkit for power users to create and manage community activities

UX Improvements

Replaced the feed-first home screen with an activity-centric dashboard showing upcoming events, active discussions, and neighbor requests. Onboarding was redesigned to immediately surface nearby activity and prompt users to join a group or RSVP to an event.

UI System

Created a warm, approachable design system that balanced community friendliness with information clarity. Used rounded shapes, a warm color palette, and generous spacing to create a welcoming atmosphere distinct from typical social media coldness.

Key Features

• Activity-first home screen with personalized local recommendations
• Quick actions: 1-tap RSVP, quick polls, neighbor requests
• Smart onboarding that surfaces local context and prompts first interaction
• Community catalyst dashboard with engagement tools and insights
• Trust indicators based on shared context (building, school, interests)

Interaction Design

Every interaction was designed to lower the participation threshold. One-tap reactions on event posts, swipe-to-RSVP, and suggested response templates for newcomers. Notification design was carefully calibrated to create FOMO around local activity without being intrusive.

Community products require designing for network effects at the micro level. A feature isn't useful if the community isn't active enough to use it. This taught me to think about design in terms of critical mass thresholds and activation energy.

• Retention in community apps is driven by speed-to-first-meaningful-interaction
• Empowering power users is more scalable than trying to activate everyone equally
• Social features need social context — proximity alone doesn't create community
• Onboarding is the product's first community experience, not a separate flow