Our evaluations on evaluations on our demo

To sum up

1. Deployment issue: Many fellow students noted the lack of deployment. Although Frontend (web pages) were not deployed on the server, the application shared the same data with the mobile, ie. backend API calls were conviently done. So our fellow students should not have the impression that they were eyewitnessing a mockup data. But technically, this is something we are aware of and appreciate the comments.
2. Comments relating to UI/UX issues are strongly appreciated by the team and we work on improvements for that. Again, we have a strong excuse: The first milestone's biggest challenge was to have a usefull workflow. The UI/UX issues were not dealt with in deep as our priorities were related to the logic of the system.
3. Security and reliability is also a common issue in our fellow students' comments. This, we noted and will make efforts on this regard.
   • We have verification and validation processes in our design. Though they are not implemented in this milestone. But critiques also give us a warning about the importance of this issue.
   • E-mail verification is a common point in the evaluations. It was "missing" in the MS1, but surely enough is a critical part of our design and implementation.
4. We have written our notes on the evaluations but fellow students should be assured that their efforts on evaluating our work are always welcome.

Comments on comments

1. The team executed a swift and concise presentation. They showcased essential functionalities, such as the registration process and the ability to add resource needs and available resources on a map - pivotal aspects of the project based on my initial understanding. Visibility of needs and resources on the map was clear and easily comprehensible, allowing users to identify them based on location efficiently. The simplicity and clarity of the presentation were noteworthy, ensuring that the key aspects were effectively communicated. Currently, the platform has limited accessibility for guest users. However, upon registration and login, users will be able to access a broader range of features, most of those which are presently displayed as mock-ups. In the mobile demonstration, they highlighted the "need creation" feature. However, the registration scenario was shown towards the end of the presentation. It might be more conventional and effective if this part was introduced earlier. Moreover, the team did a acceptable job explaining the resource creation for emergent needs, detailing how data management and storage is handled in the database.

We appreciate that.

2. Email verification was missing. A part of main functionality showed in a good way in web demo. Mobile ui was not user friendly. Chosen colors and theme decreased readability and user experience tremendously. In projection I couldn’t understand what is going on. Liked the functionality provided for the Mobile demo

We appreciate that.

3. We could see many of the functionalities of the app during this customer review. It was a good opportunity for this group to get good feedback. There is one thing that really irked me in the mobile display of resource/activities/needs detail page. The details we see on this page had a really small font size and there were too many individual elements on the screen at a time. On top of that, the color palette made it even harder to recognize the information on the page. However, this can be fixed easily so it is not a big problem. Other than that, everything looked great and must have taken a lot of effort. We appreciate that. Finally, there was no email verification during the sign up process but maybe it was just not implemented yet. Exactly

4. Mobile app seems good. Storing local need data seems pretty satisfying. Map seems a bit clichy but it is good to have this in this time.

We appreciate that.

5. The milestone presentation of Group 2 was quite sufficient when it comes to express the idea of the Disaster Response application. This is mostly due to the scenario being well-prepared. It was a good example on how the application may be used in real life. The navigation bar was detailed and animated which felt good and shows effort design-wise. Connection of backend was smooth and that is presented well. The presentation generally shows that group embraced the project and knows what exactly they did and will do. One thing I realized was, there was no verification system while signing up, which is a bad approach on security.

We appreciate that. And thanks about your point about Verification

6. Group 2's Disaster Response System looks like a valuable tool and the logic seems cool. The duty of finding and serving issues is one of the most important things during disaster times. However, it has some deficiencies as any tool that is not mature enough. The most important thing to consider is that during actual disasters, there's often chaos, leading to a proliferation of incorrect information. The system currently lacks mechanisms to prevent or validate such false data. These validation issues pertain not just to the application's logic, but also to its technical aspects. For example, the sign-up mechanism doesn't validate email addresses, allowing anyone to use another person's email to create deceptive requests.

We appreciate that. Important point.

7. In the web presentation, the screen design was suitable for the scenarios. It was adorable to have the "proceeding bar" on the top right of the post-request process to show the user that the process is in progress. He completed the backend operations on mobile. The mobile design was not self-explained. Navigation was very detailed and easy to navigate, meaning that when you pressed a button, another page opened.

We appreciate that.

8. Scenario was detailed to follow the use case. But UI of the application was not applicable with such a scenario since a person in need during an emergency might not be able to read white small information on a light purple surface.

We appreciate that.

9. It would be better if they used more than 1 account to display need/help interaction between people, i would like to see how could someone answer another's need on that platform. For this demonstration i think a common data should have been displayed on both web and mobile; design, usecase, data were not common so on mobile presentation i felt like it was another application. Authentication page didn't have any checks such as password match, email format or they didn't display it. There wasn't an email verification anyone can easily signup.

We appreciate that. As noted above e-mail verification is a part of our design

10. Mobile UI is not where it should be. Light background makes it hard to read light colored texts. UX seems nice. With few clicks, main functions can be used.

We appreciate that.

• Positive Notes:

  • The persona and scenario for the frontend demonstration were quite powerful.

  • The included functionalities and given examples were good to deliver the main idea of the project.

  • Questions were well answered.

• Negative Notes:

  • The mobile design has many problems visually. Due to poor color and font selections the content was difficult to read.
  • General user experience for mobile doesn't seem to be as convenient as the web frontend.

We appreciate that.

12. I like the mobil app especially login and signup pages. But it is good to change color palette in home page.

We appreciate that.

13. Story structure was good but visual support was not efficient enough. Otherwise functionality was good enough for this milestone. Another weak point is login page structure was not reliable. Password title overflow on the email box. General UX design was good to me but UI has some user-friendly problems.

We appreciate that. Will work on the UI/UX issue.

14. The presentation and the story-telling of the project were impressive. The UI was simple and easy-to use. Though, the colour palette that they choose was tiring for eyes. In addition, the app bar and the status bar, where statuses of the battery, the Wi-Fi, the clock, notifications etc. are listed, can be made the same colour. I believe that they didn't make enough examination of the mobile app design. The mobile and the web application that they implemented seem responsive enough.

We appreciate that. Thanks for pointing out the UI consistency issue

15. The UI looks good enough in the web.
    The mobile UI looks quite bad, clumsy, and has nothing to do with the web version. It has literally no resemblance. That is bad for UX. Also the project is not deployed.

We appreciate that.

16. The app isn't deployed yet; it's running on a local host. The scenario presented was pretty good and easy to follow and understand app usage. However, web and mobile versions of app looks very different. On mobile, text is hard to read, especially pink neon color was very distracting. It was also a bit confusing to figure out what's connected to the backend, especially on mobile, as it showed random profiles that didn't make much sense.

We appreciate that. Thanks for pointing out the UI consistency issue. Priority of the first milestone was to validate the ideas and their representations actually.

• No deployment, I think it was kind of important to do.
• I could not truly understand the reason they went with such an example. I didn't truly understand the idea until it's pointed out by viewers.

We appreciate that. What can we do sometimes?

18. Due to color choices text on the mobile part of the application is very hard to read. Everything else was clear. If everything they showed is functional then they have made great progress.

We appreciate that.

19. The user flow appears to be straightforward, which is essential for a disaster platform. I appreciate the simplicity of it. However, the main page's color scheme could use some adjustments. I believe the color purple should be reserved for more attention-grabbing areas, and using it across the entire homepage feels a bit excessive.

We appreciate that.

20. Colors were incompatible between mobile and web. I liked the login and logout parts. I think they skipped the deployment issue. I liked it overall.

We appreciate that. Thanks for pointing out the UI consistency issue

21. There were really good for mobile. On the other hand I think websites frontend was not really look like their mobile. The implementation of map was impressive but it was not that compatible with the other parts of the frontend (for web). And as I can remember they tried to signup with the same username they used for sign in. It should have been throw an error since the logged in account should be already registered.

We appreciate your deep interest. Good for you that you catched the details.

22. Mobil frontend part seemed a bit hard to use especially for a disaster response platform to due to a bright background with white text. Although it was good to see actions can be taken with easy steps while using the application.

We appreciate that.

23. I think presentation was very good. Registration page or backend has an error that we saw briefly.

We appreciate that.

24. It is practical and straightforward. This situation might be considered of low quality in an ordinary project, but given that it is used by people in emergency situations, simplicity is indeed a significant advantage. The color choices for the mobile application make it difficult to read. It could be made more user-friendly in terms of readability, as it should also cater to elderly people or individuals with visual impairments who cannot easily reach their glasses. Additional options for specifying the urgency of the person in need are highly effective. There could be some form of input for assessing the degree of emergency.

We appreciate that. Thanks for pointing out the simplicity issue relating to the extraordinary conditions of disaster

25. Just an opinion but application can be implemented mainly for Ahbap like communities use. Since in realistic case disaster victim won't be able use electronic devices because of the disaster or they would be too old/young to use electronic devices. I think there are unrelated information on profile page. Instead of user's interests, some skills/labels like "knows first aid", "is a doctor", "is an operator", "in resque team" skills/labels can be added. The color palette can be selected and the project may be implemented accordingly.

We appreciate that. The system design aims to provide simplicity for people having hard times and detailed information flow for people trying to coordinate the efforts. But details you mentioned should have our interest.

26. As needed in disaster apps UI and UX should be as simple as possible. And in the web app is easy to use, and understandable. However mobile doesn't seem nice and not easy to use. The texts'; color is similar to background color and hard to read. Also login and sign up pages need to be improved.

We appreciate that.

27. After creating the need, pop-up page can disappear and user can go back to the map. Also the message of "need created successfully" message can appear in the middle. After sign-up user can automatically sign-in.

We appreciate that.