Audit
A full review of the Lovable project and its code, not only the live site, to see where the build had drifted from what the team believed it did.
All case studies
Case study
A wildlife learning game for children
Status
Maintenance
Platform
Web responsive
Public launch
July 2026
Stack
Lovable + Vercel
The brief
Audit, fixes, mobile, and sound admin
We audited the Lovable project, closed the open bugs, rebuilt the layouts for phones and tablets, and added sound management in admin so the team can attach animal calls without another build.
- Audit
- Bug fixes
- Mobile & tablet
- New features added
- Launch support
How we framed it
Prioritize the real blockers first: bug fixes, the phone and tablet rebuild, and the public launch.
How the game works
Explore, find, and learn
Children leave the treehouse, choose an ecosystem, and search each illustrated scene for hidden animals. Opening an animal card reveals photographs, facts, and the animal's call.
What children can do
- Choose an ecosystem from the valley
- Move across wide scenes without losing hidden animals
- Tap an animal to open its learning card
- Read the facts and play the animal's call
Where we started
An audit-led path from launch to ongoing support
We opened the engagement with a full audit of the Lovable project: the codebase, the user experience across devices, and every open defect. That audit set the direction for everything that followed, from the UX and mobile rebuild through bug fixes, the public launch, and the maintenance and consulting that continue today.
UX audit and improvements
How the treehouse, the valley, the ecosystems, and the animal cards fit together, and where the experience needed rework to hold up on every screen.
Bug fixes and launch
The defects that had to close before the platform could go public, fixed and verified ahead of the public launch.
Maintenance and consulting
The relationship that continued after launch: ongoing fixes, new features, and advice as the team's needs change.
Before and after
What changed
The comparison covers how much of the platform a visitor on a phone can reach, and whether the team has someone who can resolve a problem when one turns up.
Before this work
After this work
Layouts were sized for a desktop window, so on a phone the sides of every scene were cut off.
Scenes, cards and buttons adapt to the width they are given, from a phone up to a wide display.
On a small screen, some of the ecosystems could not be reached at all.
Arrows step across the valley and across each scene, so every ecosystem and every animal is reachable.
The animal cards had no sound.
A tap on the animal plays its call, verified on real phones.
Nobody could say what stood between the platform and a public launch.
Blockers named up front, work completed in a clear order, and the platform live to the public.
Delivery
What we shipped
Each piece of work was delivered in the order the audit set.
-
Responsive rebuild
First pass- Layouts rebuilt so scenes fit a phone and a tablet, not only a desktop window
- Content that ran past the edge of the viewport brought back on screen
- Navigation between the ecosystems reworked for a narrow screen
- Shared layout code fixed once, so the change landed everywhere it is used
- Checked on real phones, not only in a browser resized to look like one
-
The fix list
From the soft launch- The defects the team and their testers had logged, closed one at a time
- Each fix checked on the screen size where the problem appeared
- Nothing added outside the list we had agreed on
- Any issue bigger than it first looked raised before we spent time on it
-
Animal sounds
The feature request- An admin panel added so the team can upload animal calls and scene sounds themselves
- Played by a tap on the animal, matching how the rest of the platform works
- Verified on phone browsers, which enforce stricter rules for audio playback
-
Launch support
Through to going public- Consulting for a team that owns the product and does not write code
- Answers in plain language, so the decisions stayed with them
- The Vercel deploy checked before the link went public
- Live at wildlifelookout.org, checked on real devices before the link went out
The result
Wildlife Lookout is live to the public, and it works on whatever device its audience uses to open it
The platform
Every screen working from phone to desktop, the open issue list closed, and animal sounds on the cards.
The team
A development team and a UX expert who explain every decision in plain language.
The launch
Blockers named in the audit, fixed in priority order, and checked on real devices before the public link went out.
Wildlife Lookout, its artwork and its teaching content belong to Champions for Wildlife.
Take your Lovable app to a public launch
We audit the project and tell you exactly what stands between it and a public launch, before anything starts. Most of that work takes weeks and does not require a rebuild, and you keep the product and the credit.