Ride booking
Request, quote, then commit — fare is an explicit step.
LABAR
まちの移動を、支える。
LaBar is operated as a live platform — passenger, driver, delivery, and safety as product areas, not labels.
FLOW
Matching, live trip state, quotes, and safety sit behind HTTPS APIs. Cluster maps, private hosts, and credentials are not documented here.
AREAS
FEATURES
Request, quote, then commit — fare is an explicit step.
Passenger and driver session state over HTTPS APIs.
A separate driver surface, not a reused passenger UI.
Delivery flows on the same operational platform.
Scheduled rides and business transportation as first-class modes.
Airport pickup and drop as a dedicated product area.
Safety features scoped to people in the trip.
A trip is requested, quoted, then confirmed. Quote is not hidden in the UI chrome.
Authoritative trip state lives on the server. Clients subscribe to the trip they are in.
Driver permissions and screens are role-separated from passengers.
Delivery uses the same operational patterns where it is safe to share them.
Schedule is a product mode, not a calendar screenshot.
Business accounts are a surface for organisations, not a vanity metric.
Airport flows are called out because the constraint set differs from street hail.
Safety is scoped to the trip. No coverage or incident statistics are invented here.
ENGINEERING
Clients, APIs, and domain concerns. No private hosts or credentials.
Clients
Platform
Support
Safety
This marketing site does not proxy LaBar’s private monitoring. Lifecycle status is Live.
UI
CSS device frames. No unverified production screenshots are published.
RELEASES
No versioned changelog is published here yet. Status is Live at labartaxi.com.