Wireframe questions and next steps

Hi All!

I started putting together some clickable wireframes so that we could better talk through the app. My inspirations were maps.me, google maps, yelp, ebay, pushpin, foursquare, alltrails and then ones for UI inspiration: airbnb, typeform and uber. I was going to put together a document today to point out the good and bad pieces of functionality in each one. I think this would especially be good for the client so that he can see how we got to the end result.

https://marvelapp.com/37a51d5/screen/27576373

Note that not every instance is accounted for, with this kind of prototype it seems ridiculous to account for every single click a user could potentially make. Hopefully, with this though we can get a good understanding of proposed functionality. Other things to note:

The first screen plays off of what Google maps does with their app. Because there are many different types of users with different use cases, (adding points, creating survey’s, editing points, seeing what’s around them, downloading maps for offline usage) I feel it is best to allow them to do whatever action they want to do from the homepage instead of forcing them into one of the actions above.

The gear and the person icon don’t do anything yet. I have questions and thoughts about those sections below.

When you add a new point, and are not within a survey, I thought it would be a nice user experience to do something similar to what Ebay does. You enter in what you want to map and it suggests the categories it should live under. This is of course much better than the user having to wade through all of the categories. Let me know if this might be possible.

For timeline based updates to points, instead of separating them out by editor, I instead combined them together as it’s nice to see how different aspects of the point have changed over time in one place. The edit functionality also reflects this thinking. Users are able to edit an individual attribute or add an update which will just give them a new field. One of my questions here is, do we need a field in these places to ask when the change was observed? Also, another thing to note on the form pages, I have been thinking about designing them so that users can scroll up and down through the questions. This is very similar to what Typeform does. This way, you can easily see all the questions on one page but hiding all but one with a gradient at the top and bottom of the page, both focuses the user on one question at a time and also keeps the form small to account for the keyboard.

My questions:
- I'd like to talk more about surveys. When a user adds a survey from the list of preset surveys, what will those be?
- How should we allow people who make custom surveys to add what category the survey fits into. For example, if they're going to map trees we should all them to say the initial category is 'natural' (I think this is the OSM category for it).
- Can we show things that the user has added? For example, a “Your Edits” section.

For the gear icon, I felt like it might be nice to have an about, some instructions and or a place to get a newer version of the app if that is how we envision a user doing so.

For the person icon, I know we talked about not having the OSM log in but maybe for now we could have them add a user name, email or other information that might help us.

I’m going to start putting together the comparative functionality doc but would love to get thoughts and feedback on this ASAP. Also, we should probably have a discussion around the web app as well, so that we can start architecting that.

Let me know what you guys think!

Thanks!