Phase 01
Wireframes
The first job was getting the highest-value actions clear. Open the map fast. See what is recent. Filter by species and area. Understand how to use the information responsibly.
Building a wildlife map that helps people plan without turning animals into live targets.
Where the Wild Beasts Roam needed a better way to help visitors plan wildlife viewing without relying on live crowd behavior, roadside rumors, or blind searching. The result was a mobile-first wildlife map built around delayed observations, useful filters, safety guidance, and cached access for low-signal areas.
UX + Dev
End-to-end delivery
Mobile-First
Design approach
18
Species totals
12–48 hr
Delayed updates
2 min
Average setup time
The Challenge
Visitors were losing their best hours chasing crowds, brake lights, and scattered information. The product had to give people a better starting point without turning wildlife into a live-tracking spectacle. It also had to work where a lot of products fail, on a phone, in the parks, with limited service and very little patience for friction.
The Approach
The platform was built as a planning tool, not a live feed. That meant delayed field observations, general viewing context, species and area filters, safety guidance inside the product, and a mobile map that can cache before the day starts.
What this project Delivered
Mobile-First
Field-ready map experience
Offline-Ready
Cached access in low-signal areas
Clearer
Species and area filters
Safer
Delayed sightings and built-in guidance.
Key Improvements
What Changed
1
Replaced blind searching with a structured wildlife map that shows recent activity, date stamps, species, and viewing context in one place.
2
Added species and area filters so visitors could plan around what they actually wanted to see instead of driving without a clear starting point.
3
Built safety guidance and responsible viewing reminders into the product so the right behavior lived inside the experience.
4
Made the map practical in the field by allowing it to cache ahead of time and stay useful even when service drops.
Who this was built for
The product was shaped around the people most likely to use it during a real day in the parks. That drove the structure, the filters, the safety content, and the mobile priorities across the platform.
Park Visitor
Needs a better starting point, recent wildlife context, and clear guidance so the day does not get wasted chasing crowds or bad information.
Wildlife Photographer
Needs fast access to recent activity, species filters, field notes, and a mobile experience that still works when service gets weak.
The Process
Wireframes to Launch
Phase 02
Development
Once the structure was set, the product moved into build as a cleaner, faster experience designed for real use in and around the parks.
Mobile Experience
Built for the phone first
This product gets used on the move, often in low-signal areas. So the mobile experience had to work there first.
- Cached map access for limited-service areas
- Scannable sightings with date stamps and behavior notes
- Fast species and area filtering
- Fast-loading mobile pages.
Principles that drove every decision
The product was built around how wildlife viewing actually works in the parks. That shaped the update model, the map behavior, the content structure, and the mobile priorities across every screen.
Protect the wildlife
The experience avoids live tracking on purpose. Delayed observations and built-in guidance help reduce crowd pressure and support safer behavior around animals.
Build for real field use
The map had to work from a phone, in low-service areas, and in short moments between stops.
Explain the product faster
Users needed to understand the value in seconds: recent wildlife context, better trip planning, useful filters, and safety guidance that travels with them.
Keep the next step clear
Every screen was designed to make the next action easier to understand, from opening the map to filtering what matters and planning the day.
Why agencies bring me in
One person across message, UX, and build.
Most teams split strategy, copy, design, and front-end work across different people. That is usually where sharp pages get softer. I work across the page so the message stays aligned from first review through launch.
Start With a Free Page AuditUX Research
Wireframing
UI Design
Front-End Dev
Copywriting
Page Optimization
Ready to Work Together
Need this kind of page support on a client project?
Send the page, the brief, or the bottleneck that is closest to revenue. I’ll review it by hand and show you what I would fix first.
