Prepared for Yalla
46 Sheshet Hayamim
Givat Hamivtar, Jerusalem
Israel
This document outlines the custom scooter rental solution we are building for Yalla. Unlike traditional scooter sharing where riders use their own smartphones, this solution embeds a smartphone directly on each scooter, enabling customers without smartphones to rent and ride.
Each scooter has a permanently mounted smartphone powered by the scooter's battery. Customers only need a basic phone capable of receiving SMS text messages to create an account and start riding.
Each scooter in your fleet will have a smartphone permanently mounted and powered by the scooter's battery. This phone runs a dedicated Levy app that allows customers to:
The screen displays a welcome message and "Start Ride" button.
Customer types their mobile number on the scooter's touchscreen.
A 6-digit code is sent via SMS to their phone (even a basic flip phone works).
Customer types the code on the scooter screen to verify their identity.
First-time users enter their name and email address.
Customer reviews and accepts the rental terms.
Customer enters their credit or debit card information.
Based on your configured settings, some customers may be prompted to take a photo of their ID and a selfie.
Customer taps "Unlock & Go" and the scooter unlocks.
Returning customers skip steps 5-8. They simply:
Enter their phone number
Enter the SMS verification code
Tap "Unlock & Go"
Scooter locks, billing continues at reduced rate
Scooter locks, final charge processed
When the customer taps "End Trip":
Scooter locks
Trip summary displays
Payment processed
Screen returns to welcome
Your technicians will set up each device by:
Once configured, the phone is permanently paired to that scooter.
You manage your kiosk fleet through the same Levy Fleets Dashboard you would use for any other fleet:
No special dashboard or tools required — the kiosk scooters appear and function like any other vehicles in your fleet.
The following settings are configured through your Levy Fleets Dashboard and apply to your kiosk fleet:
| Setting | Description |
|---|---|
| Pricing | Per-minute rates, unlock fees, and any other charges |
| Pre-authorization | Required wallet balance or card hold amount before riding |
| Payment method | Wallet-based, pay-at-end, or hybrid |
| Identity verification | Whether to require ID + selfie verification for new users |
| Zones | Service area boundaries, parking zones, no-ride zones |
| Auto-end | Automatic ride termination after period of inactivity |
| Out-of-zone parking fee | Optional fee for ending rides outside designated parking areas |
Our backend is designed to handle real-world scenarios automatically. Here's how the system responds to common edge cases:
If a customer starts a ride but walks away without ending it (e.g., leaves the scooter unattended):
Automatic handling: The backend detects inactivity and automatically ends the ride after your configured threshold. Payment is processed, and the kiosk returns to the welcome screen ready for the next customer.
If the embedded phone crashes, loses cellular connectivity, or experiences any malfunction during an active ride:
Automatic handling: The backend monitors all active rides independently of the phone. If the ride isn't properly ended, the auto-end logic kicks in based on inactivity, ensuring the customer is charged correctly and the ride is closed.
If the scooter doesn't respond to an unlock or lock command (e.g., due to temporary IoT communication issues):
Automatic handling: The backend includes built-in retry logic for all IoT commands. Commands are automatically retried until successful, with appropriate timeouts and error handling.
The phone is always on and exposed to sunlight. How do we manage screen burn-in and power?
Built-in handling: The screen automatically dims after 5 minutes of inactivity to reduce burn-in and conserve power. The phone wakes instantly on touch. Power is continuously supplied by the scooter's battery via USB.
What if you need to end a ride remotely from the dashboard (e.g., customer calls support)?
Fully supported: Operators can end any ride remotely from the Levy Fleets Dashboard. The kiosk app detects that the ride was ended remotely and automatically returns to the welcome screen.
How do we ensure one customer can't access another customer's account or ride?
Automatic logout: Unlike the standard mobile app where users stay logged in, the kiosk app automatically logs out after each ride ends. The next customer must authenticate with their own phone number and SMS verification.
You will need to provide:
| Item | Specification |
|---|---|
| Smartphones | Android or iOS devices with cellular data connectivity |
| Mounting hardware | Secure mount to attach phone to scooter handlebars |
| Power connection | USB cable from scooter battery to keep phone charged |
| SIM cards | Data plan for each device (app requires internet connectivity) |
The phones should be:
Development will proceed in phases:
We will provide updates as each phase completes and coordinate with you for testing on actual hardware.
Please reach out to your Levy account representative with any questions about this solution.
Contact Support