← Reddit

Built a lost-pet platform for the Colombian earthquake zone with Claude in two days. What worked, what broke, asking for feedback.

Reddit · ColombianEngineer · August 13, 2026
A WordPress developer built a lost-pet platform in two days using Claude after the August 10 magnitude 7.4 earthquake in Colombia scattered hundreds of pets across the region. Research into comparable disasters revealed that multiple competing platforms reduce effectiveness and that recruiting veterinarians and shelters is more critical than gathering reports from owners. Claude provided strategic pushback on design choices, including arguments against a donations section due to fraud concerns and proposals for compliant alternatives to bulk social media scraping.

Detailed Analysis

A WordPress developer in Pereira, Colombia built a lost-pet reunification platform using Claude in roughly two days following the magnitude 7.4 earthquake that struck the region on August 10. The project, now live at somosauraanimal.com, emerged from a practical observation: hundreds of displaced pets and their owners had no centralized way to find each other, with information scattered across ephemeral Facebook groups and Instagram stories that vanish within days. What distinguishes this account from typical "I built an app with AI" posts is the emphasis the developer places on Claude's contribution before any code was written — specifically, research into how comparable disaster-response platforms fared in Kumamoto, Turkey, Mexico City, Chile, Venezuela, and after Hurricane Katrina.

That research directly shaped the product's architecture and go-to-market strategy. Two findings stand out: in Venezuela, more than fifteen competing lost-pet platforms sprang up around a single disaster, and platform quality had almost no correlation with adoption — one poorly designed site captured nearly all reports while a better-built competitor got none, illustrating that fragmentation itself is often the primary failure mode in crisis-response tooling. Second, the developer concluded that the actual bottleneck in pet reunification isn't the volume of lost-pet reports but the scarcity of found-pet reports, which redirected outreach efforts toward veterinarians and shelters rather than anxious owners. This is a case where an AI tool's value lay not in generating code but in reframing the problem before implementation began.

The account also highlights instances where Claude pushed back against the developer's stated requirements, which the author explicitly says was more valuable than the code itself. When asked to build a donations feature, Claude reportedly argued against it, citing local news warnings about fraudulent donation schemes exploiting disaster victims and the reputational risk of a private business soliciting funds during a crisis. When asked to bulk-scrape social media for lost-pet posts, it declined that approach and instead flagged the conflict with Colombia's data protection law (Ley 1581), proposing an opt-in alternative where group administrators consent to indexing. These moments reflect a broader pattern in how Claude is designed to behave: not as a purely compliant code generator but as a collaborator that surfaces legal, ethical, and reputational risk even when unprompted, particularly around consent, fraud vectors, and regulatory compliance — themes Anthropic has emphasized in its constitutional AI approach.

Technically, the build reflects mature, pragmatic choices rather than novelty for its own sake: a WordPress custom post type, self-hosted Leaflet mapping with marker clustering (avoiding CDN dependency), client-side canvas compression that strips EXIF metadata to prevent leaking home GPS coordinates from pet photos, cached REST endpoints, and a human moderation queue gating all publications. The bugs Claude caught — a self-referential CSS variable silently breaking a filter, missing WordPress delete capabilities that would have violated data-erasure rights, and its own rate limiter locking out a legitimate bulk import — were found through testing rather than assumed away, suggesting a workflow where the AI verified behavior empirically rather than trusting its own output.

More broadly, this case illustrates a maturing pattern in how solo and small-team developers are using Claude for time-critical, socially consequential projects: not just accelerating code output but leaning on the model for domain research, regulatory awareness, threat modeling (scammers harvesting phone numbers from lost-pet posts, fraudulent donation solicitations, GPS leakage from photos), and design pushback under real time pressure. It's a small but telling example of AI-assisted development being used in humanitarian and civic contexts, where speed matters but so does getting subtle things right — consent, privacy law, fraud prevention — that a rushed human team might overlook entirely.

Read original article →