Case Study 5: Feathersnap App Retention Redesign
Overview:
While working at Tactacam, I noticed something troubling about our Feathersnap birdwatching app—people loved it initially, but 43% stopped using it after a month. As a bird identification app designed to work with smart feeders, it solved immediate problems but didn't give users reasons to stick around.
My job was to figure out why people were losing interest and design something that would keep them coming back through gamification and learning.
Problem:
The numbers told a clear story about engagement dropoff:
When I talked to users, the pattern became obvious: "I love identifying birds, but once I've logged a few dozen, what's next?"
We had built a useful tool, but we hadn't built a habit.
Discovery/Research Process:
I needed to understand what would actually keep people engaged:
Key insight: People genuinely wanted to learn more about birds, but needed structure. One user said: "I see a cardinal every day, but I realized I don't actually know much about them beyond what they look like."
78% said they'd be interested in bird-related quizzes. People weren't looking for competition—they wanted to become better birdwatchers.
Design and Leadership Approach:
With a tight deadline, I had to keep the team aligned and moving fast:
Management philosophy: Empower people with clear priorities, but don't leave them guessing what success looks like.
While working at Tactacam, I noticed something troubling about our Feathersnap birdwatching app—people loved it initially, but 43% stopped using it after a month. As a bird identification app designed to work with smart feeders, it solved immediate problems but didn't give users reasons to stick around.
My job was to figure out why people were losing interest and design something that would keep them coming back through gamification and learning.
Problem:
The numbers told a clear story about engagement dropoff:
- Initial excitement faded after identifying a few dozen birds
- Only 12% of users ever interacted with others in the app
- Most people ignored half the features we'd built
- Usage dropped dramatically during certain seasons
When I talked to users, the pattern became obvious: "I love identifying birds, but once I've logged a few dozen, what's next?"
We had built a useful tool, but we hadn't built a habit.
Discovery/Research Process:
I needed to understand what would actually keep people engaged:
- Interviewed 8 users (active and lapsed)
- Surveyed 300+ users (73 responses)
- Analyzed 6 months of app usage data
- Researched successful nature apps
Key insight: People genuinely wanted to learn more about birds, but needed structure. One user said: "I see a cardinal every day, but I realized I don't actually know much about them beyond what they look like."
78% said they'd be interested in bird-related quizzes. People weren't looking for competition—they wanted to become better birdwatchers.
Design and Leadership Approach:
With a tight deadline, I had to keep the team aligned and moving fast:
- Daily 15-minute check-ins with developers to catch problems early
- Weekly working sessions with design team and product owner
- Shared project board for transparency
Management philosophy: Empower people with clear priorities, but don't leave them guessing what success looks like.
Due to the timing of my departure, i was not able to get full representation of the feature. Below are just some examples of the design direction that I was implementing.
Design Solution:
We designed three integrated features that enhanced existing behavior:
Design challenge: Making gamification feel natural in a nature app. We kept the clean, outdoorsy aesthetic but added playfulness that signaled "this is fun" without feeling childish.
Key decision: Integrated everything into the main experience instead of hiding features in separate sections. Gamification enhanced what people were already doing rather than distracting from it.
Implementation Challenges:
The brutal timeline required creative quality management:
Technical hurdle: App needed offline functionality for remote birdwatching, but achievements needed validation—found hybrid solution
Results and Impact:
I left before launch, but early testing showed strong promise:
User feedback: "This makes me feel like I'm actually getting better at birdwatching, not just collecting photos."
Leadership was enthusiastic, which matters for securing resources for future projects.
Key Learnings:
Good gamification doesn't feel like gamification—it just makes something you already want to do more engaging.
What worked: Tight timelines forced focus on what really mattered. Daily check-ins prevented small problems from becoming big ones. Building on existing user love instead of changing behavior completely.
What I'd do differently: Start with just trivia feature and measure impact before building everything else. Sometimes less is more when changing user behavior.
Management lesson: When people are stressed about deadlines, they need clarity and support, not micromanagement.
The best part wasn't the features we built—it was watching a team come together to solve a real problem for people who genuinely love birds.
We designed three integrated features that enhanced existing behavior:
- Daily Bird Trivia: Questions that got progressively harder, focusing on practical birdwatching knowledge rather than random facts.
- Achievement Badges: Rewards for both learning (trivia streaks) and real-world spotting, designed to feel meaningful rather than participation trophies.
- Seasonal Challenges: Special events tied to actual bird migration patterns and behaviors.
Design challenge: Making gamification feel natural in a nature app. We kept the clean, outdoorsy aesthetic but added playfulness that signaled "this is fun" without feeling childish.
Key decision: Integrated everything into the main experience instead of hiding features in separate sections. Gamification enhanced what people were already doing rather than distracting from it.
Implementation Challenges:
The brutal timeline required creative quality management:
- Worked closely with developers to identify realistic build scope
- When features were too complex, brainstormed simpler approaches that still solved user problems
- Partnered with bird experts to ensure trivia accuracy
Technical hurdle: App needed offline functionality for remote birdwatching, but achievements needed validation—found hybrid solution
Results and Impact:
I left before launch, but early testing showed strong promise:
- 60% of test users said new features made them want to use the app more
- 25% increase in time spent during testing
- Expected 30-35% better retention at 60-day mark
User feedback: "This makes me feel like I'm actually getting better at birdwatching, not just collecting photos."
Leadership was enthusiastic, which matters for securing resources for future projects.
Key Learnings:
Good gamification doesn't feel like gamification—it just makes something you already want to do more engaging.
What worked: Tight timelines forced focus on what really mattered. Daily check-ins prevented small problems from becoming big ones. Building on existing user love instead of changing behavior completely.
What I'd do differently: Start with just trivia feature and measure impact before building everything else. Sometimes less is more when changing user behavior.
Management lesson: When people are stressed about deadlines, they need clarity and support, not micromanagement.
The best part wasn't the features we built—it was watching a team come together to solve a real problem for people who genuinely love birds.