Design Process

The purpose of this design process is to understand the needs of users and guide the requirements of the application through research and analysis. Figure1-design process flow

Context queries understand the user in the context of the application. In background checks, we try to understand the different activities, motivations, recommendations, and reasons users choose to exercise. To achieve this goal, we conducted paper studies, similar to existing studies, online surveys, and interviews with different students on campus. Surveys and interviews include questions related to users' exercise habits and recommendations from fitness apps. The information collected in the form of chart and text description is the output of background investigation.

Figure2-Define scope

Context analysis is about systematically analyzing context data to make it serve system design. In context analysis, further organize, interpret and summarize the data collected in the context of the application in order to determine user requirements and system requirements. We rank and interpret data collected from online surveys and interviews. Finally, the analysis can clearly identify users' requirements for fitness applications. The output of this step includes stakeholders, users, workflows, and affinity diagrams.

Figure3-Design

The final step is to analyze what the application needs to implement the requirements we obtain and create a conceptual model. This step focuses on user entry requirements and involves problem statements, descriptions of how the system works, selection of interaction paradigms, interaction patterns, and key interface metaphors. Then, a conceptual model is established, which describes how the application works ideally, the ontology structure of the system, and the mechanisms behind the different tasks. In addition, our team produced a lo-fi prototype to evaluate the concept model we created.

All three of these steps fall within the established requirements of the interaction design lifecycle. Establishing requirements is the first step in the design lifecycle and lays the foundation for other steps. Different design alternatives can be created as required. In addition, if the system is inefficient due to the lack of certain basic functions, the requirements should be modified.

After the team completed the preliminary survey (questionnaire and interview) and determined the audience, our team first completed the Low Fidelity Prototype in the library and conducted user tests on the use of the model. In the feedback of the test, We got a lot of useful feedback:

1. The scope of this model is too broad. It not only introduces the specific cultural situation of the country but also provides a field for exploring different cultures. It will be more targeted to narrow our goals.
2. This model still lacks a lot of details, we need to make a more detailed description of all the features of this website.
3. I can't figure out the role of the user's login account and need more useful information.

Therefore, we started to make Medium Fidelity Prototype and used "Marvel" to connect each designed page, which is convenient for users to operate, reducing operational errors and improving test accuracy. Figure4-Prototyping

After testing the user test of the intermediate simulation model, we conducted a new round of questionnaires and interviews and analyzed the data to start making advanced models and starting the production of the website.