Course development

For the next course offering, the teaching team plans to: 1. strengthen the mobile-specific and native content of the course and make the distinction between web React and React Native clearer, particularly by emphasizing that although JSX syntax is similar, the available widget/component sets and resulting design possibilities are different; 2. require students to use an appropriate mobile-device simulator when working with the native application material to increase engagement with the mobile development context; and 3. provide greater flexibility in the project by allowing students to use mobile development technologies or frameworks other than React Native, while still requiring them to demonstrate the course learning outcomes;

Mobile-specific improvements: Lab should be improved to include more native phone capabilities in order to challenge the students more on the Native front. This will also replace the provisory solution of asking students who read DH2642 before to do extra tasks. Students should be helped to set up Expo Go better. These instructions need to be per platform (Android, iOS) ----- Improvements common with DH2642: Lab examination 10 minutes per student per week instead of 5. After the student fails a "short" examination, there is a longer examination with a faculty or PhD student. We aim to limit the number of times that students can fail the oral lab examination. After one failure, the student has to start the lab again. We will consider individual lab for week 2 and 3 (so all-individual) New vitest tests are faster to run. Lab text improvements were already made but they need to be double checked. We will train the TAs better in how to help at the lab or how to ask for help from other TAs/teachers. Also how to coach projects and how to convey grading criteria. Clarify to students that the individual reflection is a possibility to characterize how the project group work Coaches should be trained not promise a certain grade to the group, as there are other reviewers. Especially architecture and user experience. Help project coaches to organize regular contacts with the group, e.g. creating whatsapp groups, etc. Clarify grading criteria, especially that all features presented to the user must be complete and interactive. Consider giving students a repertoire of project ideas rather than grading them on creativity. Execution of the user experience is more important in this course than creativity per se. Execution and architecture go hand in hand. Maybe add isolated optional exercises, include them in the lab tables, can be used also for examining students.