Back to Work
Reasy

Reasy

Safety-focused consumer app making roads safer through community reporting.

Role: Founder & Lead EngineerTimeline: 2023 – Present
Next.js
TypeScript
React Native
PostgreSQL
Vercel
Mapbox

Overview

Founded and built Reasy, a safety-tech product designed to improve road safety through real-time community reporting and data-driven insights. Handled everything from product design to full-stack development, launch, and iteration.

Key Results

X+ reports submitted

X cities covered

X% user retention (30-day)

Case Study

The Problem

Road safety data is fragmented, delayed, and often inaccessible to the communities most affected. By the time a dangerous intersection or road hazard is officially documented, incidents have already occurred. Communities need a real-time, ground-up approach to road safety.

The Approach

Reasy bridges the gap between community knowledge and actionable safety data:

  1. Community reporting — anyone can report hazards, near-misses, and safety concerns
  2. Data aggregation — reports are clustered and analyzed to identify patterns
  3. Visualization — interactive maps show safety hotspots and trends
  4. Advocacy — aggregated data can be shared with local governments and transportation departments

Implementation

The technical architecture prioritizes real-time data and mobile-first UX:

  • React Native for cross-platform mobile app (iOS and Android)
  • Next.js for the web dashboard and public-facing pages
  • PostgreSQL with PostGIS for geospatial data
  • Mapbox for interactive mapping and visualization
  • Vercel for web hosting with edge functions for API routes

Key technical challenges:

  • Geospatial clustering — efficient real-time clustering of reports on the map
  • Offline support — reports can be submitted without connectivity and sync when back online
  • Data validation — balancing ease of reporting with data quality
  • Privacy — protecting reporter identity while maintaining data integrity

Results

  • X+ reports submitted across X+ cities
  • X% user retention (30-day)
  • Partnerships with X local transportation departments
  • Featured in X publications

What I'd Do Next

  • Machine learning for automated hazard classification from photos
  • Integration with official crash/incident databases
  • Predictive modeling for emerging safety risks
  • API for third-party developers and researchers