You don't pick a micromobility app the way you pick a consumer scooter. The software has to unlock vehicles, take money, keep units on the street, and satisfy whatever the city put in the permit.
So which vendor should you actually shortlist?
Start with the rental model, not the logo. Free-floating scooters, station-based bikes, and a front-desk rental counter can look identical in a sales deck. They are not the same product.
Share platforms and shop rental tools solve different jobs
A share platform assumes a rider finds a vehicle on a map, unlocks it, and leaves it inside a service area. Your team lives in GPS pings, battery alerts, parking photos, and rebalancing lists.
A shop rental tool assumes someone booked Saturday at 10. Staff hand over a helmet. Staff take the vehicle back. That can be a solid business. It is not dockless sharing.
Thing is, operators burn budget when they force one product into the other job. A hotel with eight e-scooters may want a booking-fee tool and no monthly minimum. A 200-vehicle free-floating fleet needs a live rider app, geofences, and hardware that stays online at 1 a.m.
What you are actually buying
You are buying a rider app, an operator console, payments, and some way to talk to the vehicle. Everything else is a module, a partner, or a slide.
Joyride's rider-app docs describe the consumer side in concrete terms: a branded listing on the Apple App Store and Google Play, QR or manual unlock, cards plus Apple Pay and Google Pay, wallets, promo codes, parking rules, and ID checks. The app supports 15+ languages and multiple currencies. Store approval still takes time. Joyride cites a typical 2-3 week window after onboarding, which is a launch date, not a footnote.
Movatic leans bike share. It sells a branded app and will sell you locks, bikes, and racks with the software. Rider-reported issues can become maintenance tickets. If the public brand is the product, that pairing matters more than another analytics chart.
Vulog sits in a different lane. A Levy Fleets comparison (Levy sells competing software, so treat it as a competitor's sketch, not a scorecard) frames Vulog for automotive OEMs and large multi-service fleets, including carsharing, often in the hundreds to thousands of vehicles, with dynamic pricing and keyless integration. That is a poor match for a 20-bike neighborhood launch. The same write-up describes SharingOS, based in London since 2017, as covering bikes, e-bikes, scooters, mopeds, and e-cars on its own IoT stack.
Joyride, Ridecell, ATOM Mobility, ScootAPI, and Wunder Mobility keep showing up in operator roundups for scooter sharing. Donkey Republic and station-based vendors such as PBSC Urban Solutions show up more when the fleet is bikes. None of that is a lab ranking. Use it as a shortlist.
Who these platforms tend to fit
Hard numbered ranks only work when every vendor is scored on the same axis with the same evidence. Public roundups do not give you that. Fit is the honest comparison.
| Platform or category | Often a fit when | A weak fit when |
|---|---|---|
| Joyride | You need a branded share app, payments, and configurable rider rules | You only need a staff checkout book |
| Vulog | Large, multi-service, OEM-adjacent fleets | You are launching a tiny local bike pool |
| Movatic | Branded bike share, with locks and racks in the same conversation | You need a carshare-first OEM stack |
| SharingOS, ATOM Mobility, Ridecell, ScootAPI, Wunder Mobility | Dedicated share operations across vehicle types | You wanted shop reservation software |
| Donkey Republic, PBSC-style station systems | Bike share with docks, stations, or a bike-first ops model | Your core product is dockless e-scooters |
| Booking / reservation tools | Hotels, shops, seasonal hourly rentals | City share fleets that need geofences and live maps |
Read the table as "best for," not "winner." Two operators in the same city can pick different rows and both be right.
Don't confuse telematics with a rental OS
Samsara-style fleet trackers can show you where a scooter is. They will not give riders a white-label unlock app, parking geofences, or the city data feed your permit describes.
Pricing models that change the bill
Published prices disagree because vendors are not selling the same unit of work. Some charge a monthly SaaS fee. Some add a per-vehicle fee that looks harmless until the fleet grows. Some take a cut of revenue. Shop tools may skip the monthly bill and take a percent of each reservation.
Levy's operator roundup puts many scooter-sharing SaaS plans around €490-$900 a month before per-vehicle fees, and it estimates a custom in-house build at $100k-$300k. Other public guides list some share platforms starting in the low hundreds of dollars a month. Get a quote against your headcount of vehicles. Do not average those numbers and call it a budget.
Per-vehicle fees are quiet at 20 units. They are loud at 800.
Rider prices are a separate line. An unlock fee plus a per-minute rate is what the public pays. That is not your software invoice. Keep those cells apart.
Percent-of-booking math is easy to skip in winter and painful in July. A 5% fee on $1,200 of rentals is $60. That already rivals a cheap flat monthly plan. Run last season's actual bookings through the same arithmetic before you call the percent model "simple."
A selection workflow that starts with your fleet
Skip the trophy list. Write the operation down, then make vendors react to it.
- Put the model on one page: scooter vs bike vs mixed, docked vs free-floating, cities, who owns the vehicles, who owns the IoT.
- Copy the permit's data rules into that page. If staff already email a spreadsheet on Fridays, write that down too.
- Ask for pricing as monthly fee, per-vehicle fee, payment processing, SMS, app-store work, and what happens at 2x fleet size.
- Test hardware, not slides. Unlock 20 vehicles. Drain a battery. File a damaged-unit ticket. Try a failed payment.
- Export a sample city file before you sign. Watch someone generate it.
Turns out most painful contracts fail on step 4, after the heat maps looked great in the demo. If a vendor will not run that drill, you already have an answer.
City data and MDS
Many U.S. cities that host shared bikes and scooters ask for standardized feeds so they can see where vehicles sit in the public right of way. The Open Mobility Foundation's Mobility Data Specification (MDS) 2.0 is the open standard built for that job. MDS started in 2018 around micromobility. Version 2.0 lines up data types and endpoints so cities and operators are not maintaining two slightly different dialects.
It is not universal. Some agencies want MDS. Some want GBFS. Some still want a CSV. European privacy rules around the same feeds are a different conversation than a U.S. permit. Read your city, county, or campus contract. Do not let a salesperson flatten that into "we handle compliance."
Ask who implements the feed, who hosts it, who can change vehicle status in it, and who keeps the archive after you leave. If the permit names MDS or GBFS, make the sample file part of the pilot, not a post-launch ticket.
Hardware and the exit problem
To be honest, this is where fleets get stuck, and it rarely shows up in a features-versus-price chart because the lock on the stem is boring until you try to switch vendors and find the controller only speaks one cloud, the app store listing is in someone else's developer account, and the city feed dies the week you migrate.
Some platforms ship their own IoT. That can mean faster launch and one throat to choke. It can also mean new controllers, or new vehicles, if you leave. Hardware-agnostic software sounds safer. You still have to prove your specific lock, battery, and firmware on that stack.
Minimum fleet size is another quiet filter. Enterprise tools built for OEM carsharing may not want a 12-vehicle pilot. Other vendors advertise no minimum. Verify that on a call against your actual count, including spares sitting in the warehouse.
Payments and messaging are not "nice extras." If riders cannot pay locally, the app is a brochure. Confirm cards, wallets, and any regional processor you already use. Confirm who pays Twilio-style SMS fees when the unlock code fails at the curb.
FAQ
Is there a single top-ranked micromobility app?
No. Weighted scorecards that split "features 40%, ease of use 30%, value 30%" are a roundup device, not a measurement you can audit. Joyride, Vulog, Movatic, Ridecell, SharingOS, ATOM Mobility, Donkey Republic, and station-based bike systems are built for different operators. Match the job.
Can one platform run scooters and bikes together?
Some share operating systems are designed for mixed fleets. Bike-first vendors and scooter-first vendors still differ in docks, lock hardware, and rebalancing. If you run both, ask for a live mixed-fleet demo, not a roadmap slide.
How much should I budget for the software?
Treat any public band as a starting rumor. Monthly SaaS, per-vehicle fees, revenue share, and percent-of-booking tools price the same season differently. Add payment processing, SMS, app-store setup, and the cost of a failed migration. An in-house build is a software project, not a cheaper subscription.
What should I demand in a pilot?
A branded or white-label unlock flow, a payment that settles, a maintenance ticket that a mechanic will actually use, and a city data export that matches the permit. Twenty vehicles is enough to learn. Two hundred on a bad contract is not a better test.
Book two demos this week. Bring the one-page operating model. Sit there until someone unlocks a vehicle and generates a dummy MDS or GBFS file while you watch.