Meetings:

Jan 5th, 1 hr:

All team members present and on time

Agenda:

• Jira touchpoints at all levels

• assigning next tasks in Jira for coming week

Jan 6th, 1.5 hrs:

All team members present and on time

Agenda:

• UX testing post mortem, analysis and takeaways

• Style Guide touchpoint

• Development demo of where we are at & touchpoint

• Discuss notifications center criteria

Jan 9th, 1.5 hrs:

All team members present and on time

Agenda:

• Working/collaboration session

Jan 13th, 1.5 hrs:

All team members present and on time

Agenda:

• Status post updates for team visibility

• Review mid-fi prototype progress

• Jira touchpoints (mid-fi, style guide, dev load)

  
  

Closed Tasks:

Low-Fi Testing: Alex & Leah

Due Date: Jan 6th

Description: After concluding our Low-Fi designs before winter holiday, we undertook our user testing interviews during the break in order to gather all our relevant feedback in order to be ready to launch into our Mid-Fi designs

Takeaways:

• Conducted six 30-40 min interviews to test low-fidelity wireframes

• Participants were shown different daily schedule views, event creation screens, the availability comparison feature, default calendar layout, and memories page

• Key features tested: Single-day vs. two-day schedule views, event creation flow w/ suggested times, compare availability screen, default calendar layout and navigation, notifications and RSVP process, memories feature

• Testing went overall well, with participants thinking aloud and engaging with deeper questions. All provided useful feedback and opinions.

  
  

Low-Fi Testing Synthesis: Alex & Leah

Due Date: Jan 10th

Description: After concluding our Low-Fi user testing interviews our team needed to gather and synthesis all of our relevant feedback to derive our main takeaways in order to elevate our designs and experiences for our Mid-Fi prototype

Takeaways:

• Single day view was preferred, but participants saw value in a two day view for planning adjacent days. Week view also seemed useful.

• Suggested times should be more prominent in event creation

• Compare availability screen was confusing at first, and needs to be clarified. Especially since that is one of our differentiators

• Notifications and RSVP flow are mostly intuitive, but could have quicker access to checking your own availability to prevent back and forth checking

• Memories feature is familiar and is an expected design

  

Mid-Fi Prototype Design: Jill & Nikki

Due Date: Jan 17th

Description: Based on our user interview synthesis, our designers created a Mid-Fi prototype that enhanced our flows as well as incorporated color and typography

Takeaways:

• We designed pages with brand colors, typography styles, and components applied. Addressed concerns from usability testing alongside internal team questions, such as:

  • How available times within a group of invitees are displayed

  • Displaying different calendar events (imported from Google, declined, “maybe” going)

  • In-app notifications system

    • RSVPs to events with transparency into user’s visibility

  • Photo album details

• After understanding what to represent in mid-fi, we’re starting to outline more detailed features we’ll need to represent in hi-fi.

  

Juncture Event Thumbnail Image: Anuj, Leah

Due Date: Jan 15th

Description: This small but important feature allows a Juncture event creator to upload a custom event image thumbnail.

Takeaways:

• Adding an event thumbnail was a surprisingly straightforward process.

• To handle the photo uploads, we began using Supabase exclusively for photos, and then return the thumbnail URL to Firebase so that the image can be loaded quickly.

• This process allows us to manage storage in different places, since Supabase has better image storage without requiring payment. The process is a little convoluted, but it’s effective for event thumbnails.

Juncture Event Details View: Anuj, Leah

Due Date: Jan 17th

Description: Developed a feature that allows users to view details of calendar events. The view displays all relevant event information including title, date/time, location, and notes or attachments associated with the event.

Takeaways:

• Fetching and displaying event details turned out to be straightforward, especially with Firebase's real-time capabilities.

• Using the current logged-in user's information and their associated event ID simplifies retrieving the correct event details.

Open Tasks:

Style Guide Design: Jill & Nikki

Due Date: Jan 31st

Description: Alongside our other design activities, our team has begun work on our app's style guide, which includes our color palette, typography, design system, and branding

Takeaways:

• Intentionality behind the colors we chose and how they are applied was foundational for mid-fi designs, and continued intentionality with design elements will be crucial in continued design iterations.

Calendar Comparison feature: Anuj, Leah

Due Date: Jan 19th

Description: For this task, we are focusing on the main aspect of our core flow of comparing someone's live calendar with another user. This task's success is also critical in order to built every major feature for our application and we have allocated lots of time for its implementation.

Takeaways:

• This task has been more difficult than expected. While we’ve experimented with using Nylas' availability endpoint, we have also explored using our own system to compare availability. It’s been a frustrating process with little success so far.

• We’ve been blocked by issues with getting other participants working, which has made comparing participant times that much harder.

• Our goal is to further explore this task using Nylas but potentially adjust things using our own data.

• It’s also been difficult to create the “Compare Availability” view, as it’s somewhat different than a normal calendar. We have a plan going forwards, but we’ve been struggling to get anything produced.

• Furthermore, restructuring with our calendar library has affected setup for this task.

Edit Calendar Event: Anuj, Leah

Due Date: Jan 19th

Description: For this task, we are focusing on the implementation of a core feature. This task resolves around a coded solution that allows a Juncture calendar event owner to be able to edit and update all event fields in an event they created

Takeaways:

• We are exploring CRUD to edit/update event in firebase db.

• The research is almost done we just need some clarification on how edit process will be executed. We’re unsure where the best place for it is in the event details, so we have to quickly discuss with the designers as to how it should be handled.

• Editing an event is not too difficult and it’s close to completion, but requires a little additional refinement.

Delete Calendar Event: Anuj, Leah

Due Date: Jan 19th

Description: For this task, we are focusing on the implementation of another core feature. This task resolves around a coded solution that allows a Juncture calendar event owner to be able to delete an event they created, regardless if people have accepted. the event should be removed from all attendees Juncture calendars upon deletion

Takeaways:

• As mentioned in the “Edit Event” task, the research is almost complete; we just need some clarification on how delete process will be executed.
  
  

• Events can be deleted, but again, the process needs further input from designers.

New Tasks:

Mid-Fi Testing Script: Alex

Due Date: Jan 19th

Description: For this task we are creating the script that we will use when conducting mid-fi-testing

IX Flows: Jill, Nikki

Due Date: Jan 27th

Description: For this task we are creating the IX flow mapping for our core flows and pages, outlining all the relevant triggers, feedback, rules, & loopholes