At this point I tried to check through the users when they are using the data in the city and what feelings and emotions arise when they are forced to find new information when they are in the city.

After processing the insights of the research, I approached strategic development. The purpose of this strategic step is to characterize the users and to think about the process of translating a database into a product. From my research, I discovered that all the information that is on social networks can be used for 3 different types of users. for the community, the merchants who are not part of the community but serve the community, and for research and execution needs for the municipal authorities.

The first type needs data that is not related to the community life of the city but it does need recommendations from locals about urban functions like parking, restaurants, etc. The second persona who is a business owner in the neighborhood and also lives there, but does not feel connected to the neighborhood socially. The third wants to analyze information about the neighborhood and community life in each neighborhood

We clearly divided each component according to explicit heuristics in most of the firms.We did not encounter a problem except for two issues we had difficulty solving.
After we mapped the hierarchy of the categories, we started designing the user journey from the onboarding stage until reaching the main board.
Student Dashboard- The teacher can monitor the student's reading results and progress.
Users- A list that manages all the students who use the device, with the option to filter by groups or classes
Plans-Manage the devices you have and their programs
Discover- Essential learning of using the device and how to use it in your daily life.
Home screen-A general view of the devices and users' activity, plans, and updates.
Our most significant difficulty was creating a system suitable for both a physical device and a web platform. In a multi-cross device environment, we encountered issues that we had not experienced before-Our first solution was to activate the device and then force it to register itself as a user, But we understood that this could confuse him.

We used the concept exposure method, which is a type of semi-structured interview that, in the end, presents a prototype of the product to the user, and then he is asked a series of questions about what he understands from the product. The user experiences it and thinks out loud about how he would use it daily. Through this exposure, we know the user's way of thinking through the prototype we createdThe main goals of the dashboard are divided into an overview where the teacher can quickly and easily locate the student's improvements and performance. We divided the screen into three parts:

after that we made a usability testing and we got a great insights for some of our question.

After understanding where improvements need to be made, we mapped and coded the components to find repetitive behaviour. My main resrach insights

(1) The reading comprehension graph was not intuitive enough.so the solution was to turn it into two separate graphs. Do not insert another form of a chart that needs to be learned
(2) The teacher often identifies one problem and misses another-the list of problems is arranged according to the hierarchy. In the end, there will be a general tip.
(3) Need to sort groups of students according to their problems-so on the users' page, we will add an option to: "sort by..." where we will also enter sorting by specific problems.