Elicitation Questions

Points of Interest

• Which sort of places are considered Points of Interest?
• How are Points of Interest added to a route?
• There are POIs defined by system users and ones already included in Google Maps API. How will we handle this distinction?
• What should the POI page include?
• What should the POI page not include? -Who shoul be able to access to POI’s which are not loaded from wikidata but created by users.

Feed Design

- What is the maximum length for a route?

• What details will be shown to the user when browsing through posts in the feed? (Route title, time of sharing, chosen display name of the poster, number of likes, number of comments)
• How will routes shared by users who choose to remain anonymous be displayed to users, and what details will be different?
• Will there be options to hide the number of likes and comments?
• Will the number of saves be shown, and can it be hidden?
• Will there be an option for users to say I am not interested in this topic?
• If the user finishes the posts what will be shown?
• Will clicking on the route post lead to accessing more detailed information about the route?
• Will there be options related to posts that are not liked? Such as reporting, selecting "Not interested" preference?
• Is promoting with advertisements on the platform a possibility?
• Can posts from tour companies be promoted with advertisements to users?
• Which information will be used to determine the posts on the feed page? (likes, comments, etc.)
• How frequently is the feed page refreshed?
• How will the feed page be created if the user is new?
• If a user says I am not interested in this post, how does it affect the feed page?

Routes

• What is the maximum length for a route?

• Will the routes be importable/exportable if so, in which format?

• Should the route details found by searching or on the feed be the same?

• Should there be suggested routes below the details?

• What should be the size of the map that will appear in the route details section?

• Will there be a report route button?

• How will similar routes be recommended (which algorithm, etc.)?

• Which map API will be used? (Google Maps, Yandex, etc.)

• How many similar route recommendations will there be?

• Will personalized recommendations be made to users, or will the same recommendations be shown to every user?

• Which functionalities will be used: saving a route, liking a route, or rating a route? (or combinations of them?)

• Will one user's saved/liked routes be visible to other users? (We can either directly show the saved ones or create two separate lists, public and private, such as hidden saved and waitlist)

• What is considered as a route?

• Which features or info are required to create a route? Which ones are optional?

• What is the minimum number of places to create a route?

• Are locations of places mandatory to add into a route or are their names enough?

• Are everyone allowed to create a route?

• Is creating a route, saving it for yourself but not posting is allowed?

• Who can see created routes? (followers only, everyone, customized groups like close friends etc.)

• If the application is closed while creating a post, will we keep the existing draft locally, etc.?

• Are there any daily limitations to create a route? (to avoid spamming)

Route Details

• What details could be accessed? (Route description, location details, comments about each route)
• Will there be details about the person who shared it? Will the number of followers be visible?
• Will it be possible to access the account of the person who shared the post from the post details? How will access be provided? (Clicking on the profile photo, clicking on the username, swiping right for quick access to the profile, etc.)
• What quick options can be applied for users from the post details? (Saving, liking, rerouting)
• Will there be an option for rerouting?
• Will comments made by users who are not followed be shown on the route?
• Will comments made by blocked users be shown?
• Will comments made by users who have been reported on another post be shown?
• Should comments made by followed users be displayed higher than others?
• Is there an option to like, save, or share comments?
• Can someone re-share the post? (rerouting)
• Which platforms can I share the post on?
• When sharing the post, is it a link to the post or is the post converted to text? For security reasons, the former should be done.
• Can the links to posts of private accounts be shared?
• How will posts shared from a private account be protected when someone who doesn't follow that account tries to view the post?

Search results and the page design

• Should Explore be on a separate page?

• Should Explore be something that can continue endlessly?

• How will Explore be determined based on the user's previous likes, saves, and followed accounts?

• Will there be a refresh feature for Explore?

• Will there be any differences in how Explore posts are shown (e.g., interested, not interested)?

• Will Explore posts be shown more frequently as they are liked?

• Will the color theme of the Explore page be different from the feed?

• Will the Explore page have any other distinct features from the feed?

• How many posts should be fetched from the database for Explore, and what should the limit be?

• If Explore posts are limited, how will it be determined when the user reaches the limit?

• What is the best way to store liked posts in Explore to ensure that similar routes are shown more frequently in the future?

• What should be included in the search bar? (Profiles, route names, travel preferences)

• What should be the main result of the search? Routes, profiles, or travel options?

• Should these quick results be shown to the user instantly as they type in the search bar?

• Should the user search by applying filters in the search bar or filter the results after performing the search (similar to websites like Sahibinden.com)?

• Should the text entered in the search bar be searched across all databases collectively, or are there priority queries that need to be searched first?

• How can fetching and processing results from the query be implemented simultaneously as the user types in their search?

• Should the most searched keywords be stored along with their results in another database for faster retrieval?

• Are there any daily limitations on displaying routes to prevent scraping?

• What should be included on the result page?

• Can routes that use the location be placed below the location on the location result page?

• Can a section be added to the side, similar to an Amazon chart, for quickly adding the ongoing route to the location result page?

• Will the location result page include the location on the map?

• How will the display style change, if at all, based on the type of result (person, place, route)?

• What information about the person will be displayed on the result page?

• If the result is a route, will possible routes be listed or the most likely one be placed at the top?

• Can multiple types of results be shown harmoniously on the result page (e.g., person and route)?

• If there is harmony, will the space they occupy on the page be equal, or will one have more details than the other?

• What details will be shown to the user on the person result page?

• If the location of the result is to be shown on the map, should Google API be used simultaneously?

• If a map API is used, how can it be determined whether the result is a location or another category?

• How many results will be shown on one page, and will more appear as you scroll down? Will there be any limitations?

Log in

• Which third-party platforms can be used to login (Gmail, Facebook)?
• Should logins and registers be via e-mail or username?
• Do users need to provide any additional information for identification purposes?
• If logging in with a username, should this username be displayed in the posts?
• Should everyone be able to choose a non-unique name for themselves as there may be people who want to remain anonymous?
• Will the user remain logged in indefinitely after logging in, or will they be automatically logged out if they don't log in for a certain period of time?
• Will there be a remember me option?
• If a user chooses to use the remember me option, how do we store the information?
• Is there a need for password reset functionality? If so, how should it work?
• Are there any accessibility requirements for the login page?

Sign up

• Will sign ups be via email or username?

• What will be the restrictions when determining username and password?

• Will there be an email verification for sign up?

• Will there be any requirement for unique username or email,for example,"this username is already registered"?

• Will there be some verification system for preventing some blacklisted email addresses from being registered?

• Will the system automatically log in to the created account after signing up?

• Will there be an option for signing up via accounts from other platforms,like Facebook?

Profile page

• Will there be private profiles? If yes, how do they interact with public profiles?

• Will private profiles’ likes and comments in public profiles’ posts be visible to everyone or just the 2 users in that specific interaction?

• If there are private profiles, can their names appear in search results?

• How will the password resetting be done, if the user forgets it? Will there be a recovery email or security questions?

• Can users block other users and report them? Are comments made by blocked users on routes also hidden from us?

• Can users directly communicate with each other, like Instagram DM?

• Can users delete their account, and use the same email/phone number to login again?

• Can users share other users' posts?