Route Input Fields Have Poor Autofill Support

[Swi-ft]

Description

The Origin and Destination fields technically support autofill/autocomplete, but the quality is below average. Suggestions are limited, not context-aware, and often irrelevant, leading to a frustrating input experience.

Expected Behavior

Autofill should be:

• Fast and responsive
• Context-aware (relevant suggestions based on typing)
• Capable of handling typos or partial inputs
• Prioritizing popular or recent locations

Impact

Medium – affects user efficiency and satisfaction when creating trips.

[harshitptl21]

As I’ve already mentioned, this is a course project, not a fully-funded real-world application with access to premium services.

We’ve used Leaflet and OpenStreetMap, which are free and open-source tools. While this may result in slightly slower response times compared to commercial services, the performance and behavior are not as slow or irrelevant as you've suggested. Additionally, suggestions were intentionally limited to a maximum of 5 to prevent them from overlapping with or obstructing other components. As long as the input is relevant, the results will be equally relevant.

[Swi-ft]

These both are 2 different places by the way. For an app that is heavily relevant on the "From" and "To" locations, this is not acceptable.
-> "As I’ve already mentioned, this is a course project, not a fully-funded real-world application with access to premium services."
If in the beginning it was known that the app is going to be "sub-par" in terms of accuracy and results, a different and more satisfactory option should've been selected.

Please do let us know how we should close this issue if it isn't resolved?

[harshitptl21]

This type of issue, where places with very similar names but different locations exist, can be found on most maps.

Unfortunately, there's little we can do about this unless we adopt a more precise naming convention, such as using coordinates. However, this would compromise human comfort.

[Swi-ft]

So I'm gonna keep this Issue open, and in future if this does get implemented, I'll close it