
Process
Part 1: Establishing app's overview
Part 3: Creating User Interface Prototypes
Part 2: Establishing app's context
Part 4: Listing Metadata schema / metadata records
Part 1: Establishing app's overview
Scope
-
Our purpose is for upcoming or experienced artists to unite as a unified group to help each other out.
-
Our goal is not only to bring forth artists but promoters as well
-
24 hours confirmation in order to receive the verification symbol
-
Submit any prior art work
User Types
-
Primary target audience:
-
Upcoming artists
-
Young, future artists such as musicians, vocalists, producers, painters, photographers, models, video producers, editors, and many more
-
-
Secondary target audience:
-
Promoters, managers, event planners, talent agencies, and mainstream celebrities
-
These users may only log into the app once to catch up on the new artists but may not be active on the app
-
User Tasks
-
Search for any type of niche to connect with
-
Marketing -- artists and promoters
-
Permits them to follow one another
-
Send videos, voice recording, sharing files, and call feature in chats
-
Able to click on the social media platform(s), filter location, promoters based on their specific interest, and have access to see which artists are beginners or advanced
Part 2: Establishing app's context
Market Comparison & App Rationale
Since we were making a social media app, we decided to compare our idea to three established social media platforms: Instagram, Discord, and Spotify.

Getting Data
-
Artico will be collecting data from users and will be managed by the staff.
-
Users must provide some personal information when creating an account with our app (name, email address, and date of birth)
-
Ask for the location (city and state) to find local artists
-
Banking information from payment methods such as Apple Pay, Google Pay, and Paypal
-
We are not planning to track users but will keep the information they provide
-
Social Implications
-
Copyright is the most considerable risk
-
We will manually verify our users, promoters, and companies to ensure their identity is valid.
-
communicating with verified people for safety issues.
-
sign a policy contract
-
-
Payment process may also bring a hard time for our users.
-
accepting payment before project collaboration starts and hold until approval.
-
manually step in to solve the problem and justify the issue.
-
Part 3: Creating User Interface Prototypes
Low - Fidelity Wireframes

I sketched a low- fidelity prototype so we could have an idea of the layout before we started designing it in Figma.
High - Fidelity Wireframes
.png)
Part 4: Metadata Schema
Summary Item Type Table
.jpg)
Detailed Property Information Table
.jpg)