I am evaluating Story Map Crowdsource for agency use at Arizona Game and Fish. I have the following suggestions to make the user experience more rich:
Hi Richard,
Thanks for the thoughtful feedback! The first one is definitely on our list for the next release, and we will definitely consider your other two good ideas for future releases.
Owen
Thank you Owen for the instant feedback! This is an awesome template...we have, I hope, special plans for it.
Richard
Sent from my iPhone
Owen -
I have a related observation in Crowdsource Storymap (CS) that arises from real life experience. We are evaluating CS head to head with another photo submission app that has no mapping capability with it. I think we will, for two of our demographics (hunters and anglers) go with the other app because hunters and anglers typically want to submit photos and brag, but they don't want others to know where they got lucky. Wildlife Watchers, on the other hand, are a bit of the opposite and so CS is still a strong candidate for that public. However, having some additional options would help CS play better in all venues. Some I have already shared with you, but an additional one came up in discussions last week: Providing to the storymap creator the ability to make some of the required fields optional. Often, potential submitters won't submit because we have too many, or in some cases, ANY, required fields. I know that some are required, but providing flexibility also makes managing the content and structure of the storymap easier to adapt to certain publics. Thanks again for listening and I hope to hear soon when the next version of CS is arriving. Cheers!
Richard
Hi Richard,
Thanks for the feedback. We've heard this request from a few other folks as well and are considering it for a future release.
Owen
Cool... Thanks for the feedback I guess good minds think a like!
R
Sent from my iPhone