HW01: Repo, App Critique, Drawing, Teamwork due Mon 19 Jan 23:59

Overview

Part 1: Repo Setup (6 points)

• On your laptop, open the command line and clone the course repo and remove the remote called origin:

  	git clone https://github.com/tsergeant/ui_homework.git
  	cd ui_homework
  	git remote remove origin
  

• In GitHub, create your own private, empty repository by visiting https://github.com/new.
  • Name it ui_homework
  • Select Private
  • Do NOT add a README, .gitignore, or license (leave it completely empty)
  After the repo is created, add the instructor (terrys@gmail.com) as a collaborator on your repo.

• Back on your laptop, setup the remotes so that “origin” points to your github repo and “upstream” points to the course repo:

  	git remote remove origin
  	git remote add origin https://github.com/<your-username>/ui_homework.git
  	git branch -M main
  	git push -u origin main
  	git remote add upstream https://github.com/tsergeant/ui_homework.git
  

• Verify that the remotes are correct with: git remote -v

  You should see:

  	origin   git@github.com/<your-username>/ui_homework.git (fetch)
  	origin   git@github.com/<your-username>/ui_homework.git (push)
  	upstream https://github.com/tsergeant/ui_homework.git (fetch)
  	upstream https://github.com/tsergeant/ui_homework.git (push)
  

• Push your initial copy to your private repository:

  	git push -u origin main
  

Part 2: Markdown and Team Communication (6 points)

Open your local workspace using Cursor and open the USING_MARKDOWN.md file and begin reading it. You will be asked to preview it. Be sure to do that to make it more clear.

Many of the homework assignments this semester will require that you submit your work in Markdown format. You will be allowed to use AI to help in that process, but it will be very helpfult to know the basic syntax and rules because you'll need to edit.

In the hw01 directory in your repository, create a document named team.md in which you will record the names of your team members and the agreed-upon contact methods for each person. Also, find a set time each week besides Thursday when all team members are available to meet if needed. Record this meeting time in the document. This document can be created once and shared among the team. Be sure to preview the file to make sure it is formatted properly.

Part 3: App Critique (8 points)

• Affordances: What actions seem possible on the main screen? Are the affordances clear (e.g., buttons look clickable) or hidden?
• Signifiers: What visual cues (color, icons, text labels) help you understand what to do? Are any signifiers misleading?
• Feedback: How does the system respond when you log an item or complete a task? Is the feedback immediate and clear?

Include at least two annotated screenshots highlighting specific examples of good or bad affordances/signifiers. Your written document should be in a nicely-formatted Markdown document named hw01/app_critique.md and the screenshots should be stored in the hw01 directory under the names screenshot1.png and screenshot2.png.

Part 4: Mobile vs. Web Platform Comparison (6 points)

• Navigation: How does the menu structure differ? (e.g., Bottom tab bar on mobile vs. Top header on web).
• Data Density: Which platform shows more data at once? Why?

• Interaction: Identify one task that is easier to do on mobile and one that is easier on web. Explain why based on platform constraints (e.g., thumb zone vs. mouse precision).

Your comparison notes will be in a separate section of the hw01/app_critique.md file created in part 3 above.