Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Origin/Destination UI Component for Trip Planning #13

Closed
aaronbrethorst opened this issue May 15, 2024 · 1 comment
Closed

Origin/Destination UI Component for Trip Planning #13

aaronbrethorst opened this issue May 15, 2024 · 1 comment

Comments

@aaronbrethorst
Copy link
Member

aaronbrethorst commented May 15, 2024

As a frequent public transit user,
I want to easily input my trip's origin and destination within the OneBusAway app,
so that I can quickly and accurately plan my route using public transportation.

Requirements

Functional Requirements

  1. Input Fields:

    • The UI should have two clearly labeled input fields for the origin and destination.
    • Each input field should support text input and autocomplete suggestions based on nearby locations and recent searches.
  2. Autocomplete Suggestions:

    • Display a list of autocomplete suggestions as the user types, including recent search history and popular locations.
    • Suggestions should be fetched in real-time and displayed dynamically.
  3. Error Handling:

    • Validate the input fields to ensure valid addresses or transit stops are entered.
    • Display appropriate error messages if the input cannot be recognized.
  4. Accessibility:

    • Ensure the component is fully accessible, with support for VoiceOver and dynamic text resizing.
    • Provide clear labels and instructions for screen reader users.

Non-Functional Requirements

Usability:

  • The UI should be intuitive and easy to use, with minimal steps required to input origin and destination.
  • Provide visual feedback when locations are selected or errors occur.

Scalability:

  • Design the component to handle a large number of suggestions and high traffic without performance degradation.

Compatibility:

  • The component should work seamlessly across various iOS devices and screen sizes.
  • Ensure compatibility with iOS 16 and 17.
@hilmyveradin
Copy link
Collaborator

This issue is chucked to 4 different issues:

#14
#15
#29
#30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants