ScootRoute / Independent project / Vancouver
The journey
doesn’t end
at the scooter.
I designed a mobile planner that brings pickup, riding, return and the final walk into one journey.
Choose a Vancouver trip, compare vehicles and press Go to follow the turns. Routes follow mapped streets and paths. Vehicle availability, parking and movement are simulated.
Select image to enlarge
- My role
- Problem framing, research synthesis,
UX/UI and implementation - Scope
- Working mobile web prototype
User benefit not yet tested - Method
- Secondary research · AI-assisted development
No interviews or participant testing
The central decision
Plan the return
before unlocking.
A rider needs to reach a destination, leave the scooter in an allowed place and finish the walk. I made those parts visible together before the ride starts.
An error without a next step
The message ends with “OK”. A route to allowed parking is not offered inside this message.
The rule is clear. The last walk is absent.
The parking-pin card does not show the walk from that location to the rider’s destination.
Make the first and final legs visible
I brought the walk to pickup, the return bay and the final walk into the pre-ride plan.
Evidence and its limits
The research narrowed
the opportunity.
I began with a prototype, then used an 18-source secondary review to assess its rationale and identify gaps. I focused on people deciding whether a shared scooter fits a Vancouver trip, including the parts they would walk.
Returning is part of the trip.
Vancouver requires Lime trips to end at designated stations.
City of VancouverI treated the return station as a planning constraint, separate from the destination.
A rule does not tell me how often riders struggle with it.
Lime already supports parking planning.
Its Vancouver guidance explains capacity checks and full-station alternatives.
Lime VancouverI focused the design on whole-trip clarity, including the final walk.
Published instructions do not prove how easily people find or use a feature.
Arrival can leave uncertainty.
One Vancouver rider described docking difficulty and continued charges.
Read the rider’s accountI kept rental completion explicit before advancing to the final walk.
This is an unverified account. It does not establish cause, frequency or a typical experience.
Whole-journey planning exists elsewhere.
Citymapper documents pickup, riding, parking and final walking guidance.
CitymapperI used the whole journey as a design baseline and questioned the need for a separate planner.
I did not verify equivalent Vancouver coverage or comparative usability.
The wider review included access-distance research, a historical Mobi survey and local reporting. These are context, not Lime complaint rates. No interviews, surveys or participant usability tests were conducted. Explore the full source ledger
Make the trade-off visible
A short ride can
still be a long trip.
I made total time and walking visible in the comparison. Each option brings together the access walk, ride and final walk, with an allowance for unlocking and returning.
This gives the rider a way to compare the commitment before choosing a route. The estimates remain model outputs, not measured trip times.
Compare the demo options
- Estimated total
- 13min
- Walking distance
- 260m
2.2 km ride · 260 m walk
Sample trip from Canada Place to Sunset Beach. Times include the walk to pickup, the ride, the return and the final walk.
- My decision
- Compare the complete trip, rather than rank options only by riding time.
- The trade-off
- More information helps expose the journey, but also makes each result denser. Whether the distinction is clear needs evaluation.
From riding to walking
Return the scooter.
Continue on foot.
I gave the return its own step between the ride and the final walk. The screen brings the parking location, rental reminder and next action together.
Show where the ride ends.
The screen names Sunset Beach parking bay and highlights “Return” in the journey tracker. The destination is still a short walk away.
Make the next action clear.
I paired the reminder to return the scooter and check Lime with “Continue on foot”. Selecting it starts the final walking leg.
From interface to implementation
I built the live-data connection, too.
The prototype includes an adapter for Lime’s public Vancouver GBFS feeds. These are data endpoints, not shared API keys. The adapter reads scooter coordinates, station locations and reported return availability.
- Implemented
- Vehicle and station feeds are normalized into pickup and return options. Disabled or outdated records are excluded, and the interface refreshes availability every minute when live mode is enabled.
- Public walkthrough
- Visitors explore a complete sample journey using fictional availability and simulated navigation. They can also change either address, compare another trip and follow each leg on the map.
- Deployment boundary
- Lime’s published terms restrict public display and aggregation. Live Lime data remains disabled in this public deployment while the applicable permission is unresolved. Public access to a feed is not the same as permission to redistribute it.
Current outcome
A working exploration.
A benefit still to establish.
I built the journey model, comparison, GBFS adapters and foreground navigation states. The strongest result is a concrete way to examine the decisions around a ride. I have not measured an improvement for riders.
Implemented
Complete-trip comparison, named return locations, final-walk details, active-leg navigation and explicit provider handoffs.
Technically checked
Controlled journeys and synthetic location updates exercised navigation and recovery states. These were software checks, not participant research or outdoor ride validation.
Not established
Better comprehension, fewer failed returns, lower charges, reliable background tracking or demand for a separate planner.
I learned that a route interface needs to explain both the journey and the limits of the information behind it.
Research trail
Follow the evidence.
18 core secondary sources, plus imagery, technical documentation and presentation references. Each source has a stated use and limitation.
Local context and existing capabilities 6 sources
- R01Lime shared e-scooter system
Official local context
Vancouver requires station returns and publishes availability data. This makes the return location a planning constraint. It does not establish how often returns fail or guarantee space at arrival.
- R02Vancouver location information
Existing Lime capability
Lime documents destination-area capacity checks and alternatives for full stations. This narrows the opportunity to how a complete trip is presented, not an absent parking feature.
- R10Using a parking station
Official Vancouver service flow
Lime describes securing the scooter and helmet at a station, after which the rental ends automatically and the app confirms completion. Arrival alone is not completion.
- R11I'm still getting charged after ending my ride
Official support scenario
Lime explains delayed ride completion and recovery steps. The help page establishes a supported scenario; it does not establish its frequency or confirm a specific rider’s account.
- R17Making Scooters Usable
Competitor documentation
Citymapper documents pickup walking, scooter navigation, parking and final walking. Whole-journey planning is not a new category. Vancouver Lime coverage and comparative usability were not verified.
- R18Using bikeshare and scooters
Competitor documentation
Transit documents pickup and return planning, alternatives and provider handoffs. Capabilities vary by service and city. This does not establish which features work with Vancouver Lime.
Published research and reporting 4 sources
- R04Vancouver Bike Share 2018 Member Survey Results
Published survey, Vancouver, 2018
The Mobi member survey received 1,722 responses. Empty and full stations prompted some members to use alternatives. This is historical bicycle-share context, not a Lime failure rate.
- R05Access distance to e-scooters
Published research, Stockholm, 2023
Wincent, Jenelius and Burghout analysed scooter access distance using app openings and trip records. It supports including the access walk. Parking conditions and geography differ from Vancouver.
- R06Vancity Lookout article
Local first-person reporting, 2025
Nate Lewis describes destination coverage and more frequent use after expansion. This is one journalist’s historical experience, not a representative study or today’s service boundary.
- R08Differences in route choice behavior when riding shared e-scooters vs bicycles
Published research, Dresden, 2024
Ringhand and colleagues studied 52 participants. Scooter riders placed greater importance on surface and safety than cyclists. It cautions against assuming bicycle routes fully suit scooters.
Public rider discussions 6 sources
- R03Lime now goes over Granville
Public discussion, November 2025
Includes full-station concerns and a recollection of encountering a restricted area. Dates and causes are not verified. Positive comments favour orderly docking. Anecdotes do not establish prevalence.
- R07Lime e-scooter question
Public visitor question, May 2026
A visitor asks about Stanley Park access after encountering older information. This supports planning uncertainty, not a verified failed ride. Replies are not current permission to ride.
- R09Lime Scooter won't dock into station
Public rider report, September 2026
The author describes docking difficulty, continued charges and eventual completion after an update. The cause, charge and refund outcome are unverified. Another commenter reports successful recovery.
- R12Can Someone Explain the LimePass
Public discussion, October 2025
The author asks about pass terms and later corrects their understanding. Preserve that correction. The thread supports comprehension questions, not the original misconception or current pricing.
- R13Cost of Lime e-scooter
Public discussion, July 2026
A commenter asks how to compare repeated short trips. Calculations are disputed. This supports comparison effort, not verified savings, a fare model or purchase advice.
- R14Record usage discussion
Public discussion, June 2026
A rider asks where to find passes; another commenter explains. Positive value comments provide counterevidence. The title’s record-usage claim is not used as a verified statistic.
Product terms, imagery and other references 8 sources
- R15Ride costs and rates
Official pricing documentation
Lime explains unlock and time-based charges, varying rates and pass terms. Fare comparison is a separate data problem. No current Vancouver tariff was verified for ScootRoute.
- R16Canadian user agreement
Official product context
The Canadian agreement describes conditional destination-based route, parking and price suggestions. This contradicts an absolute claim that Lime lacks planning. It does not verify each account’s experience.
- V01Lime parking guidance and refusal screens
Published app illustration, accessed October 31, 2026
The two-screen image is published by Lime on its Stuttgart page. It shows parking pins and a parking refusal message. Screenshot location, app version and capture date are unverified. It is not a Vancouver app audit.
- V02Lime end-trip photo screen
Published app illustration, accessed October 31, 2026
The image is published by Lime on its Utrecht page. It illustrates a photo-based completion step in another market. Vancouver has a different physical docking flow. Screenshot version and capture date are unverified.
- D01Work & Co: MTA Live Subway Map
Professional presentation reference
Informed the transportation-focused opening and the connection between map information and journey decisions. Its research, assets and outcomes are not ScootRoute evidence.
- D02Lin Ong: Slice App Redesign
Professional presentation reference
Informed the pairing of mobile screens with concrete design goals and clear research provenance. The case-study structure was adapted; its findings and outcomes were not reused.
- D03Natalia Koldaeva: Numerade Navigation
Professional presentation reference
Informed early role framing and the problem-to-interface narrative. Published performance claims were not independently audited and were not transferred to this project.
- T01MDN: Geolocation watchPosition()
Technical reference
Documents location updates, permission and secure-context requirements. API availability is not evidence of reliable outdoor tracking, background behaviour or successful rider outcomes.
Independent project, not affiliated with Lime. Research reviewed October 30, 2026; published app imagery added October 31. ScootRoute screens show the November 13 walking and cycling routes with simulated vehicles and movement. Lime imagery © Lime. Prototype maps © OpenStreetMap contributors. AI assisted research, development and verification.