Lyber: Rideshare Product Concept
Lyber is a work-in-progress rideshare clone exploring pickup, destination, route, and fare interactions with Google Places and Maps APIs. The goal is to build a product that feels familiar enough to use instantly while still serving as a playground for map-based UX and full-stack iteration. The current demo is available at lyber-rideshare.herokuapp.com.
Image coming soon!
Future route states, driver matching flows, and fare breakdowns coming soon.
Working Through Map-Based Complexity
Even in progress, Lyber captures a useful design challenge: geospatial products ask users to make decisions on top of moving data, predictions, and context. Pickup and destination fields have to feel precise, maps have to stay readable, and pricing feedback has to make sense quickly. That makes this project a strong study in designing around location, not just forms.
Focus: Maps UX, third-party API integration, and iterative product development.
Stack: React, Node, Express, PostgreSQL, Google Places, and Google Maps.
What it shows: Comfort with unfinished but meaningful product exploration, especially where interface complexity is high.
Why It Matters
Lyber represents the side of my work that is exploratory and system-minded. Not every project is about polish at the final pixel. Some are about proving flows, testing constraints, and pushing through the hard parts of map interaction, state, and product logic until the right shape becomes clear.