You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem Description
We have this amazing feature now since a few months called Event Collections, but it is not obviously accessible so more people can discover it on their own or start exploring.
Solutions
I'd like to suggest the following:
On the official https://app.unlock-protocol.com/event page I suggest to create an additional FAQ point for this. Something along the lines of "Can I create collections for events" or similar. I also think it would make a good point in this row:
Secondly, it should be accessible from the dashboard itself. So after or even during the editing of an event it should become a natural part of the flow if possible. That would allow for the feature to be more often used and known and in return heighten discovery of events. Here is a quick mockup:
Alternatives
Everything would be fine as long as discoverability is more obvious. The above are just my ideas but Unlock engineers might have even better ideas on where to make access more obvious. But what is the use of a great feature if it is not obvious to anyone :)
The text was updated successfully, but these errors were encountered:
Problem Description
We have this amazing feature now since a few months called Event Collections, but it is not obviously accessible so more people can discover it on their own or start exploring.
Solutions
I'd like to suggest the following:
On the official https://app.unlock-protocol.com/event page I suggest to create an additional FAQ point for this. Something along the lines of "Can I create collections for events" or similar. I also think it would make a good point in this row:
Secondly, it should be accessible from the dashboard itself. So after or even during the editing of an event it should become a natural part of the flow if possible. That would allow for the feature to be more often used and known and in return heighten discovery of events. Here is a quick mockup:
Alternatives
Everything would be fine as long as discoverability is more obvious. The above are just my ideas but Unlock engineers might have even better ideas on where to make access more obvious. But what is the use of a great feature if it is not obvious to anyone :)
The text was updated successfully, but these errors were encountered: