MyWDFW
For recreational hunters and anglers in Washington state who need to manage their licenses, report harvests, and comply with state wildlife regulations.
MyWDFW is a struggling sports app that is completely free. With a 1.4/5 rating from 195 reviews, it struggles with user retention. Users particularly appreciate functional utility, though login and authentication failures remains a common concern.
What makes this app unique?
What Does It Look Like?
What Are The Key Features?
Purchase and display hunting and fishing licenses directly within the app
Digitally notch and record harvests for big game, turkey, and fish
Submit mandatory catch records and migratory bird harvest reports
Access key licensing and reporting features without an active internet connection
How much does it cost?
- Free to download and use for all licensed hunters and anglers
The app is a government-provided utility tool rather than a commercial product; monetization is not a goal, as it serves as an official compliance and management platform.
Who Built It?
Portfolio
7
Apps
What other apps does Washington Department of Fish & Wildlife make?
Explore the full Washington Department of Fish & Wildlife report
Portfolio breakdown, audience, momentum, and every app published by Washington Department of Fish & Wildlife.
What do users think recently?
High confidence · 33 reviews analyzed
How did the latest release land?
What is the recent mood?
Recent user voice shows a upset sentiment. Users appreciate functional utility, but report login and authentication failures and app stability and performance.
Limited review volume (33 reviews). Sentiment analysis will deepen as more data lands.
View the full user-sentiment analysis
Mood gauge, ratings & review-volume history, every praise / complaint / request, and sentiment over time.
What is the competitive landscape for MyWDFW?
How's The Sports Market?
How does it evolve in the Sports market?
Rank progression
2 active rankings tracked — 30-day window
The rivals identified
The outtake for MyWDFW
Strengths to defend, gaps to attack
Core Strengths
- Official government mandate for licensing and reporting
- Offline functionality for remote field use
- Consolidated reporting for multiple species (birds, shellfish, fish)
Critical Frictions
- Critical login loops and 2FA failures
- High friction from mandatory device passcode requirements
- Unstable splash screen and frequent freezing
Growth Levers
- 2026-2027 mobile-first transition creates a mandatory adoption window
- Integration of map layers to compete with regional benchmarks
Market Threats
- Technical superiority and high trust of neighboring MyODFW app
- User abandonment in favor of paper systems due to reliability issues
What are the next best moves?
Resolve 2FA and Login Loops
This is the #1 complaint theme and a total blocker for core functionality, leading to the current 'terrible' sentiment.
Re-evaluate Mandatory Device Passcode Requirement
Users cite this as a major point of friction and privacy concern, preventing them from even attempting to use the app.
Optimize Splash Screen and Initial Load
Frequent reports of being 'stuck on splash screen' indicate a critical performance bottleneck that prevents app entry.
Feature Gaps vs Competitors
- Integrated map layers for wildlife management units (available in MyODFW)
- In-app trophy gallery and social sharing (available in Go Outdoors Virginia)
- Predictive fishing forecasts (available in Fishbrain)
Key Takeaways
If I were the PM, I would halt all feature development to focus exclusively on the authentication and boot-up sequence. While the app has strong differentiators like e-tagging, they are currently irrelevant because the 'upset' user base cannot get past the login screen; the 2026-2027 transition is at risk unless stability is achieved immediately.
Where Is It Heading?
Stable
Rankings dropped to #91 (↓17) — indicates declining user acquisition or retention.
Recent updates focused on bug fixes and login stability (April 2026) — active maintenance but no new features.
Upset user base due to forced passcode requirements — persistent friction point.