Got It Week 4

Introduction

This week, the team focused on advancing the user experience and refining the app’s visual and functional direction. Key efforts included completing foundational research, improving the prototype, and planning the next stage of development and branding.

Progress of the Week

October 6

• Held an internal meeting to align on deliverables.

• Achievements:

  • Completed user persona and user research.

  • Finished competitive analysis.

  • Developed low-fidelity to mid-fidelity prototypes.

  • Created the initial interactive prototype.

  • Published the weekly blog.

• Blockers:

  • Copyright concerns (pending review).

  • User testing not yet conducted.

  • Logo design received feedback—it currently resembles the Gatorade logo.

• Micaela: Summarized meeting notes with Shifra.

Moving Forward:

• Begin user testing with focus on features, functionality, and layout design.

• Polish logo and branding direction.

• Continue weekly blog updates.

October 7

• Created the user flow for the MVP.

• Conducted research on APIs, sandboxing, and copyright issues.

• Delegated upcoming tasks among team members.

• Important Dates:

  • October 23: Business and Media Event.

  • October 28: Midterm Presentation.

Henry’s Research Areas:

• Design systems and modular architecture.

• Atomic design (atoms, molecules, templates, pages).

• Feature slice design, UI libraries, and base UI systems.

• Tools explored: Shadcn, Headless UI, React Native reusables, Unistyl (React Native Unistyles), Motion.dev, Moti.fyi, and Pragmatic Data Platform Architecture.

October 9

• Reviewed the low-fidelity prototype to map out user flow.

• Defined screen-by-screen feature placement and logic.

• Reached consensus that the backend will supply books for users, automatically displayed on the dashboard.

• Decided to retain Add and Upload buttons for users who wish to upload their own study materials.

October 10

• Began storyboarding for video concepts.

• Team agreed on a creative tone: memes, glitchy pop bubbles, and a sense of humorous overwhelm (e.g., “That’s the 5th one this week!”).

Feedback

From Daemon:

• Preferred the Omega logo over others.

• Liked the homepage design (Kayla) — found it more digestible.

• Suggested adjusting letter spacing and line spacing, and to verify if “letter spacing” is necessary.

• Recommended adding a collapsible panel feature.

• Appreciated the toggle feature to compare original vs. edited versions.

• Reassured team not to worry about copyright at this stage.

• Suggested placing adjustments and edits at the bottom of the interface (like in Figma or FigJam).

From Henry:

• Also liked Kayla’s homepage.

• Appreciated Pat’s mindmap concept.

• Praised Mai’s focus on reducing user anxiety through simplified information design.

Next Steps

• Refine low-fidelity designs into updated mid-fidelity versions.

• Finalize branding and style guide.

• Refine design components and interface consistency.

• Begin development phase.

• Create marketing storyboard.

• Conduct user testing for usability and visual feedback.