Escooter App Development Company: Rider Apps, Fleet Consoles and IoT for Scooter Sharing

Updated October 2026 · Written and maintained by the Progression Agency strategy team

An escooter app development company designs and builds the software a scooter operator runs on: the rider app that finds, unlocks and bills each ride, the console a fleet team uses to charge, move and repair vehicles, and the link to each scooter’s lock and telematics. We build e-scooter app development projects for sharing startups, city and campus operators, rental shops and scooter brands that want their own app. Progression Agency is based in New York City and works with clients across the United States and worldwide.

What does an escooter app development company build?

It builds the whole software side of a micromobility business: what the rider touches, what the operations team runs, and the code that talks to the vehicles. Buying only a rider app leaves the operator without a way to charge, move or bill a fleet.

The rider app

This is the part people picture first. It shows a live map of vehicles with charge levels, handles sign-up and payment, unlocks a scooter, shows the fare as the ride goes, guides parking and sends a receipt. It also carries safety lessons, help requests and damage reports, so the operator hears about a broken brake from the person who found it.

The operator and fleet console

A web console for the people who run the fleet: a map of every vehicle and its state, battery queues, rebalancing lists, repair tickets, rider accounts, refunds, zones and fares. It is usually bigger than the rider app, and it is the part that decides whether the business can run with a small crew.

The device and IoT layer

Each scooter carries a lock and usually a telematics module with GPS and a cellular link. The platform sends it commands (unlock, lock, sound the alarm, cap the speed) and receives its reports (location, battery, motion, faults). How that link behaves when the signal is poor shapes the whole rider experience.

The field crew app

Chargers, swappers and mechanics need their own tool: a task list by distance, a scan-to-confirm step for each battery swap or move, and a quick way to mark a vehicle out of service. A separate app keeps crew features out of the rider app and lets the crew work offline in parking garages and basements.

Micromobility app development: who we build for

Anyone who puts small electric vehicles in front of riders and needs software to rent, track and maintain them. Our electric scooter app development work changes with the business model, so we scope it from the model, not from a feature list.

Scooter sharing app development for startups

Dockless fleets that sell rides by the minute to the public. They need the full platform from day one, plus the permit reports and data feeds a city may require. Our software development for startups page explains how we keep a first release small enough to fund.

City, campus and private-site operators

Universities, business parks, resorts and airports that run a closed fleet on their own ground. Rules are simpler than on public streets, but the app often needs single sign-on for students or staff and billing to a department instead of a card.

Rental shops, hotels and tour companies

These businesses rent by the hour or day from a counter or a front desk. They need booking, waivers, deposits and return checks more than a live map. That is closer to classic scooter rental software than to e-scooter rental app development for a sharing fleet, and we cover it in its own section below.

Scooter and e-bike manufacturers

Brands that sell vehicles to owners and want a companion app for pairing, locking, ride modes, battery health and firmware updates. No fares, no fleet, but much deeper Bluetooth work and a long tail of device versions to support.

Franchise and white-label operators

Companies that license a brand or a platform to local operators. The software needs tenants: each franchise sees only its own vehicles, riders and money, while the head office sees everything and sets shared rules.

How does electric scooter rental work, step by step?

A rider opens the app, finds a scooter on the map, scans it to unlock, rides, parks in an allowed spot and ends the ride, and the fare is charged. Behind each step the platform is checking rules and talking to the vehicle.

Before the ride: account, payment and rules

The first time, the app collects a phone number or email, a payment method and whatever the city or the operator requires, such as an age check or a short safety lesson. Returning riders skip all of that, so the second ride should take seconds.

During the ride: telemetry and zone checks

The vehicle reports position, speed and battery at set intervals. When it enters a slow zone the platform tells the controller to cap speed; when it enters a no-ride zone it can slow the scooter to a stop. The app shows the running fare and time.

Ending the ride: parking, lock and fare

The app checks that the scooter is inside an allowed parking area, may ask for a photo, and sends the lock command. Only when the lock confirms is the fare final. A ride that cannot end is the most common support complaint in this business, so this step gets the most testing.

Unlocking: QR codes, Bluetooth and IoT locks compared

Most fleets use a QR code that triggers a cloud command to the scooter’s IoT module, with Bluetooth as a backup when the cellular link is weak. The choice decides how rides behave in garages, tunnels and dead spots.

Why tokens beat open Bluetooth commands

A Bluetooth unlock should use a short-lived token the server signs for one rider and one vehicle. That way a copied command cannot be replayed, and a ride can still begin in a basement where the phone has no data.

What happens when GPS or cellular drops mid-ride

The vehicle keeps a local log and sends it when it reconnects. The platform should bill from the vehicle’s own trip record when it arrives, not from the last position the app saw, and it should never charge for minutes after a confirmed lock.

Ending a ride with no signal

If the lock cannot reach the server, the app can end the ride over Bluetooth and upload the proof later. Riders should get a clear message that the ride has ended, so nobody walks away worried about a running meter.

Scooter IoT: telematics, locks and firmware updates

The IoT module is the scooter’s link to the platform. We integrate the module the operator has chosen, or help choose one, and apply the device patterns from our IoT app development work to a fleet that moves.

What the module reports

Position, speed, battery state of charge, lock state, motion while locked, tilt or fall, controller faults and the firmware version. Report intervals are a trade-off between fresh data and battery drain, and they can change by state: frequent while riding, sparse while parked.

Commands the platform sends

Unlock and lock, speed limit changes, headlight and alarm control, power down for theft, and a locate chirp for crews. Every command needs an acknowledgment and a retry rule, because a lost command looks like a broken scooter to the rider.

Over-the-air firmware updates

Updates go out in waves, starting with a few vehicles in the depot, with a way to stop the rollout if faults rise. The console should show which version each vehicle runs, so a support agent can see when a complaint matches a bad release.

Working with a hardware vendor’s cloud or the raw protocol

This is where an experienced escooter app development company saves the most time. Some vendors expose a cloud API; others publish a protocol the module speaks over cellular or a serial link. A vendor cloud is faster to start with; talking to the modules directly gives more control and removes a middleman. We read the vendor’s documentation during discovery before recommending either.

Geofencing: no-ride, no-parking and slow zones

Geofences are drawn polygons with rules attached. The app shows them on the map, and the platform enforces them through the vehicle, so a speed cap still applies if the rider closes the app.

Rules that city programs build into the app

Public programs can require specific behavior. When NYC DOT announced its eastern Queens e-scooter share expansion on June 15, 2023, it said new riders must complete in-app safety training, a quiz and age verification, and that each rider’s first three trips are limited to 10 mph. Read the full NYC DOT announcement. Rules like these become settings in the console, so they can change without an app release.

Photo checks at the end of a ride

Many operators ask for a parking photo before a ride closes. The photo is stored with the trip, reviewed when someone complains, and can feed warnings or fees for riders who park badly. Clear wording about how photos are used belongs in the privacy notice.

Keeping zones accurate

Zones drift out of date when streets change. The console should let operations staff edit a polygon, preview it, and publish it to every vehicle and app at once, with a log of who changed what.

Ride pricing and payments inside an e-scooter rental app

Fares are usually an unlock fee plus a per-minute rate, with passes, memberships and discounted plans on top. Payments run through a card processor or a mobile wallet, never through the app stores’ in-app purchase systems.

Holds, deposits and partial capture

Operators often place a hold on the card when a ride starts and capture the real fare at the end. On Stripe, for example, an authorization for an online card payment is usually valid for seven days, and capturing less than the held amount releases the rest automatically, as its guide to placing a hold explains. Day rentals with larger deposits need a different flow.

Why rides are not sold through in-app purchase

Apple’s App Store Review Guidelines (rule 3.1.3(e)) say that apps selling physical goods or services consumed outside the app must use purchase methods other than in-app purchase, such as Apple Pay or card entry. A scooter ride is that kind of service. The App Store Review Guidelines are the text reviewers apply.

Keeping card data off your servers

Stripe’s integration security guide notes that a business handling raw card numbers on its own payment page may face more than 300 PCI DSS security controls, and that low-risk integrations send card details straight to Stripe instead. We build that way, so your servers store only tokens and the last four digits. See Stripe’s security guide.

Refunds and disputes

Support staff need one-click refunds with a reason code, limits by role, and the trip record (route, photo, lock time) on the same screen. That is what keeps disputes short and chargebacks rare.

Micromobility fleet management software: the operator console

The console is where the business is actually run. It shows every vehicle, tells crews what to do next and turns rides into reports, and dashboards in it follow the same build approach as our dashboard development work.

Live map and vehicle states

Available, in a ride, reserved, low battery, out of service, missing, in the depot. Each state has a color and a filter, and every vehicle shows when it last reported, because a scooter that has been silent for a day is a problem even if the map shows it parked.

E scooter fleet management tasks, ranked by effort

Charging takes the most labor, then rebalancing, then repairs, then retrieval of vehicles left in the wrong place. The console should generate those tasks automatically from battery levels, demand and rider reports, and route them to the nearest crew.

Rebalancing toward demand

Rides pile vehicles up in some places and empty others. A rebalancing list compares where vehicles are with where rides usually start at that hour, and suggests moves. Simple rules from the operator’s own trip history are a good first version.

Maintenance and repair tickets

Rider reports, controller fault codes and crew inspections all open tickets. Each ticket keeps the vehicle out of service until a mechanic closes it, which protects riders and gives the operator a record if something goes wrong.

Theft, tamper and impound alerts

Motion while locked, a module that stops reporting, or a scooter leaving the service area outside a ride raises an alert. The console tracks impounded vehicles and their fees too, since cities can remove badly parked scooters.

Roles and permissions

Crew members see tasks, support agents see riders and refunds, finance sees money, and only a few people can change zones or fares. Separate roles keep mistakes small and give each action an owner.

How do rental e-scooters get charged?

Three ways: crews or contracted chargers collect scooters and charge them, crews swap batteries on the street, or vehicles return to charging docks. Each method needs different software.

Battery data the platform needs

Charge level, pack serial number, charge cycles and temperature where the module reports it. Tracking packs separately from scooters matters once batteries are swappable, because a weak pack can move between vehicles.

Pricing the charging work

If outside chargers are paid per vehicle, the app needs clear task rules, proof of drop-off and payout reports. Disputes over unpaid charges eat support time, so the rules should be visible to the people doing the work.

City permits, data sharing and MDS feeds

Cities that permit shared scooters can set caps, zones and reporting duties, and many have operators that report data in a standard format such as MDS. Each city’s permit text decides what applies; we build the feeds and reports it asks for.

What MDS is

The Open Mobility Foundation describes the Mobility Data Specification as a free, open-source set of six APIs that help cities manage transportation in the public right of way. Its Provider API lets operators report device data to cities, its Policy API lets cities publish rules on how, where and how many vehicles operate, and its Agency API supports real-time exchange between the two. The foundation’s list of MDS users says more than 1,200 cities and public agencies worldwide have mobility operators using MDS, and that over 70 cities publish real-time rules and geofences through MDS Policy.

What GBFS is

The General Bikeshare Feed Specification is an open standard, managed by MobilityData, for publishing shared bike, scooter, moped and car availability in a simple JSON format. Publishing a GBFS feed helps trip-planning apps show your vehicles to people who never installed your app.

Permit applications, the software side

Applications often ask how the operator will enforce parking, limit speed, verify riders and report data. A platform that already has those controls in the console makes the application easier to write and the promises easier to keep. Requirements vary by city, so we read the city’s own permit documents with you before scoping.

Rider safety, age checks and location privacy

The platform gives operators the switches; the operator and the city decide the rules. Age limits, license checks, helmet reminders and data retention are all configuration, and we build campaigns and apps inside these rules, not legal advice about them.

Age and license checks

Most shared fleets are for adult riders, and some vehicles or cities require a driver’s license. The app can collect a date of birth, scan an ID through a verification provider, or require a license for mopeds only. Which check applies is the operator’s decision, set per city and vehicle type.

Safety lessons, helmets and incident reports

A short in-app lesson and quiz, helmet reminders, a beginner speed mode and a clear button to report a crash or a hazard. Incident reports should reach a person quickly and keep the trip record attached.

Location data is personal data

Article 4(1) of the GDPR names location data as an identifier, so European operators treat trip routes as personal data. In California, the Attorney General’s CCPA page lists precise geolocation as sensitive personal information that consumers can limit. Retention limits and aggregated city feeds are part of our standard design.

App store rules for location

Apple’s guideline 5.1.5 asks apps to use location only when it is directly relevant and to get consent first. On Android 10 and later, background location needs its own ACCESS_BACKGROUND_LOCATION permission, and Google Play reviews apps that use it through a permission declaration with a prominent in-app disclosure. Most rider apps only need location while open, which keeps review simple.

Accessibility

Screen reader labels, large tap targets, high-contrast map pins and clear error text help riders, and parking rules that keep sidewalks clear help everyone else. Both tend to come up in permit conversations.

Features an e-scooter sharing app needs at launch, and what can wait

Launch with the features that let a ride start, end and get paid reliably, plus the console tools to keep vehicles charged. Loyalty, referrals and advanced pricing can follow once real rides show where the money is.

Companion apps for scooter owners

Owners who ask whether electric scooters have an app usually mean the manufacturer’s companion app. That app pairs over Bluetooth, locks the scooter, changes ride modes, shows range and battery health and installs firmware. It needs none of the fare or fleet machinery, but it must cope with every hardware revision the brand has shipped.

How a scooter connects to its app

The owner turns on the scooter, opens the app, allows Bluetooth, and the app finds the vehicle by its advertised name or a QR code on the frame. A good companion app explains each permission in plain words and recovers gracefully when pairing fails.

Scooter rental software for shops, hotels and tour operators

Counter-based rentals need bookings, waivers, deposits and check-in more than a live map. Electric scooter rental software for these businesses is closer to a reservation system with a vehicle register attached.

Hourly and daily bookings

Online booking by slot, walk-up rentals at the desk, extensions from the rider’s phone and late-return fees. Inventory is counted per location, and the system should prevent double bookings when two staff members rent the last scooter at once.

Waivers, ID and deposits

Digital waivers signed before pickup, ID capture where the operator requires it, and a card hold or deposit released on return. Store only what the operator truly needs, and set how long it is kept.

Check-out and check-in inspections

Photos of the vehicle at pickup and return, battery level and a damage checklist protect both the shop and the renter, and they settle arguments in seconds.

Bike sharing software, e-bikes and mopeds on one platform

The same platform can run bikes, e-bikes and mopeds next to scooters, with rules per vehicle type. Riders want one app, and operators want one console, so mixed fleets are a common second step.

Docked and dockless bikes

Station-based bike share adds docks: station capacity, dock faults and moving bikes between full and empty stations. Dockless bikes behave more like scooters. Bike rental software for tours and resorts follows the counter model described above.

Mopeds and license rules

Mopeds add helmets stored with the vehicle, license checks and higher insurance needs. The app can require a license only for moped rides while scooters stay open to every eligible adult.

One account, several vehicle types

Riders keep one wallet and one ride history, and passes can cover some vehicle types and not others. Pricing, zones and speed caps are set per type in the console.

How to start an electric scooter rental business: what the software must support

Settle where you are allowed to operate, choose vehicles with a lock and telematics you can integrate, line up insurance, decide who charges the fleet, and only then fix the app scope. The software follows the business plan, not the other way round.

How to start a scooter rental business on private property

Campuses, resorts and business parks can be a faster first market because the landowner sets the rules. The app still needs zones and safety settings, but there may be no city permit cycle to wait for.

The software lines in a scooter rental business plan

A plan should name the build cost from a written scope, monthly cloud and mapping costs, payment fees, the IoT module’s data plan and support staffing. Investors ask about rides per vehicle per day and cost per ride, so the console should report both from day one.

Are scooter rentals profitable?

It depends on how many paid rides each vehicle gets per day, how long vehicles last before theft or damage, and what charging and moves cost. Software cannot fix a weak market, but it moves every one of those numbers: fewer failed unlocks, faster charging rounds and fewer lost vehicles.

How long does it take to build a scooter sharing app?

A first launch in one city on hardware already chosen typically takes four to five months from the start of discovery: about a month to scope, about three months to build the MVP, and a few weeks of pilot.

What speeds a build up

Hardware with good documentation, one city with clear rules, decisions made quickly by one owner, and a launch fleet ready for testing during the build rather than after it.

What slows it down

An IoT module with no documentation, several cities at once, a custom payment method in each market, and fare rules that keep changing during the build.

Scooter app development cost: what decides the quote

We do not publish a fixed price for micromobility platforms, because the cost depends on scope. A quote follows a written scope after discovery, and our app development cost guide explains how app budgets are built in general.

Why we quote after discovery

An escooter app development company that names a fixed price before reading your hardware documentation is guessing. Two scooter apps can look the same on screen and differ several times in effort underneath, mostly because of hardware and city rules. Discovery tests the hardware link and reads the permit terms first, so the quote covers the real work.

Running costs after launch

Cloud hosting, maps, the IoT data plan, payment fees, app store developer accounts, monitoring and a maintenance retainer. We list them in the scope so the business plan has them from the start.

White label, custom build or an app like Bird or Lime?

A white-label platform gets a fleet running fastest; a custom build gives control over the product, the data and the margin; many operators start on one and move to the other. The phrase an app like Bird or Lime usually describes the dockless sharing model, and that model is what we build, under the operator’s own brand.

When white label makes sense

A short pilot, a small fleet, a single city and no plans to sell the software itself. The trade-off is per-vehicle fees, limited changes and data that lives on someone else’s platform.

When a custom build makes sense

A larger fleet, unusual rules or vehicles, a franchise or campus model, or a plan to license the platform to others. Owning the code and the data also helps when investors ask what the company actually owns.

Moving from a white-label platform to your own

Migration runs both systems in parallel by zone, moves riders with their balances and passes, and re-points vehicles to the new platform in batches, so service never stops.

The technology behind micromobility software

A typical stack pairs native or cross-platform mobile apps with a real-time backend, a mapping provider, a payment processor and a data store built for location history. We choose per project and explain the choice in the scope.

Native or cross-platform

Cross-platform frameworks cover most rider app screens well, and our Flutter app development and React Native app development pages compare them. Deep Bluetooth work can still favor native modules, which both frameworks support.

Real-time backends

Thousands of vehicles reporting every few seconds while riding produce steady event traffic. Queues, idempotent handlers and clear retry rules keep commands and bills correct when parts of the system slow down. Our backend development services page covers the general approach.

How operators and riders ask AI assistants about scooter apps

Founders ask ChatGPT, Claude, Perplexity, Gemini, Microsoft Copilot and Google’s AI Overviews questions such as which escooter app development company has shipped a fleet platform, who can build a scooter sharing platform, what one costs, or how to start an electric scooter rental business. Riders ask which app runs the scooters in their city.

What these assistants tend to cite

Pages that answer one question directly, comparison tables of build options, official city program pages, standards bodies such as the Open Mobility Foundation and MobilityData, app store listings and review sites. Vague vendor pages with feature lists and no specifics are rarely quoted.

What an operator should publish to be named

A clear service area page per city with current rules, fares written as text rather than only inside the app, an accessible help center, a GBFS feed where it applies, and consistent business details across app stores and directories. Our answer engine optimization service covers this work, and our app marketing team handles store pages and launch campaigns.

Why this page answers questions directly

Each section starts with a short answer a person or an assistant can quote, then gives the detail. That is the same structure we recommend for an operator’s own help center.

How to choose an e-scooter app development company

Choose a team that asks about your hardware, your city rules and your operations before showing screens, can explain how rides end when the signal drops, and gives you the code, the data and the accounts.

Red flags

Walk away from an escooter app development company that offers a fixed price before anyone has read your hardware documentation, a clone script with someone else’s brand still in the code, no answer for offline ride endings, and contracts that keep the source code or the app store accounts with the vendor.

Questions to ask in the first call

Which IoT modules have you integrated? How do you test unlocks before vehicles arrive? What does the console show a support agent during a dispute? Who owns the code? Our guide to hiring app developers lists more.

Related app development services

These pages cover the neighboring app types, the building blocks this page relies on and the services around a launch.

• App development services
• IoT app development for connected devices
• On-demand app development for marketplaces
• Taxi and ride-hailing app development
• Delivery app development
• Travel app development
• iOS app development
• Android app development
• Flutter app development
• React Native app development
• Cross-platform app development
• MVP development company
• Software development for startups
• Dashboard development for operations teams
• Backend development services
• API development
• Cloud app development
• Embedded software development
• Logistics software development
• UI and UX design services
• App development cost guide
• Hire app developers
• App marketing agency
• Mobile app PR agency
• App development company in NYC

Frequently asked questions