a platform designed to connect artists and galleries
DESIGN
Design Requirements
After we gathered the information we needed about our user group through the interviews, personas, and user journey maps, we started brainstorming the requirements we needed to make sure the product fulfilled the users needs. We put together a list of the important things the user will use the product for. This process helped us be thoughtful of what we’d include in our final product. This helped us gain a deeper understanding of what it means to make requirements for the product, focusing on what the user needs, not how the product behaves.
Key Design Requirements:​
-
Give curators, artists, and art collectors a platform to meet and discuss their interests. (place to communicate)
-
Allow users to explore current art trends that are happening throughout the world. (stay up to date on art trends)
-
Allow users to upload an archive of pieces still available for purchase or for viewing past exhibits. (artists have a place to showcase their work)
Storyboards
The purpose of the storyboard was to help us see what scenarios the user will be in when they may find the product useful. These 3-6 panels gave specific scenarios the user will be in based on the design requirements we made. This helped us visualize what we want specific pages to look like before seeing everything on a larger scale. This helped up be reflective of the information we got from the interviews, learning how to tell a story effectively, and only including necessary parts. These storyboards helped us identify important features that our product must have, as shown in our information architecture.
_edited.png)
_edited.png)
takeaways:
-
We started to visualize our product as an application
-
We began to focus on specific design requirements
-
We had a lot of ideas to choose from as each group member was tasked with two storyboards.
Information Architecture
After getting an understanding of the scenarios the user will be in based on our storyboards, we created a diagram of all the pages that will be needed in our interface. Having this diagram helped us see the bigger picture of what we wanted our product to look like. This visual assisted us when we started making the paper prototypes for our product. This helped us see what our purpose was on a larger scale rather than in small, detailed sections.
takeaways:
-
We broke down our app into 5 sections: setup, community feed, explore, calendar, and profile
-
We started making pages for specific design requirements.
-
Example: to help users connect and build relationships with one another, there’s a messaging page for them to interact with one another
