-
Notifications
You must be signed in to change notification settings - Fork 0
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
RESEARCH - New simplified bot creation flow. #2457
Comments
Beng, Pavel, and I talked this over on our morning call. We haven't identified any major technical roadblocks. Getting the pop-out/pop-in UI when switching from map mode to create mode and coordinating around the keyboard show/hide will take some effort, but nothing we haven't done before. @bengtan noted that this will require a backend tweak to store the selected icon but that shouldn't be a huge undertaking. |
@southerneer appreciate the update. |
We can probably close this ticket now that we have begun building out the actual "location create" tickets. Does anyone object? |
that works for me |
Problem Statement: Locations (formally known as Bots) are hard/cumbersome to create, this results in very low user content creation. To solve this, we need to simplify the creation process and make location/bot creation simple/fast.
Details: To create a location, users have two available options. The only difference between these two options is how initial location creation works. Option #1 ask the user to search for a location (via a search box) or allows a user to drag the map to the desired location (Option 1 accessed via tapping on create "+" CTA). Option #2 (accessed via long-press on the map) simply assumes that where the user long pressed is or is close to the position the user wanted to mark (there is no search box) and the user can adjust the map if needed.
Goals:
Option #1. Tapping the create "+" CTA:
Once a location is selected, the user is asked to fill out basic information to finish creating the location pin.
Option #2. Long-press on map:
The text was updated successfully, but these errors were encountered: