Meetings:

Jan 29th, 1.5 hrs:

All team members present and on time

Agenda:

• Working session

• Jira Scope alignment based of NUF feature matrix

• Design and Dev demos/touchpoints

Feb 3rd, 1 hrs:

All team members present and on time

Agenda:

• Jira touchpoint on design/dev tasks

• Mid-fi testing review

• Status post feedback reflection discussion

• Design/branding/logo discussion

Feb 6rd, 2 hrs:

All team members present and on time

Agenda:

• Working session

Feb 10th, 1.25 hrs:

All team members present and on time

Agenda:

• Jira Touchpoint

• Hi-Fi review

• Lobby Poster Discussion

• Dev and Design Updates

• Status post update

Closed Tasks:

Mid-fi Testing: Alex, Team Support

Due Date: Feb 2nd

Description: After making updates to our low-fi designs based on our first round of testing, we created a mid-fid moderator guide to further learn more about the the usability, flow, and comprehension of our updated designs.

Takeaways:

• Structuring interviews into two parts allowed for deeper, more focused interviews without participants feeling rushed.

• Making sure that participants have enough background information is crucial to keep context between both sections of interviews.

• Having discussions on what we wanted to learn from this testing session made script writing more straightforward.

Mid-fi Testing Synthesis: Alex

Due Date: Feb 8th

Description: For this task our team synthesized all the data collected during mid-fi testing in order to make takeaways easy and accessible to the team for hi-fi prototype adjustments.

Takeaways:

• Beyond adding friends, our event creation flow presented many options to users at once, overwhelming participants. We are taking the good feedback from our "adding friends" sub-flow and applying it to the whole event creation, breaking steps out when necessary. This will hopefully alleviate any overload, showcase our main compare availability feature more prominently, and allow us to better control the users decision timing.

• Testing showed that there was confusion between actionable and non actionable notifications. Using UI elements and/or filtering to differentiate them might limit the user confusion that was present in testing.

• Participants had many different answers when asked how they would RSVP or change their RSVP on the event details page. Clarifying and unifying the way RSVPing works and is shown across pages might make how a user would select or change an RSVP more obvious.

Lobby Poster Draft: Jill & Nikki

Due Date: Feb 13th

Description: For this task, our team created our initial lobby poster rough draft (seen below), using all of our existing visual branding, and design system components.

Takeaways:

• Planning to continue iteration and fine-tune designs that reflect our brand and balance simplicity and engagement.

Upload Photos to an Event: Anuj, Leah

Due Date: Feb 9th

Description: For this task we created a feature that allows our attendees to upload an image to an event they are a part of.

Takeaways:

• This task was not too difficult, since we had already established image uploading procedures from thumbnails and profile images.

• The biggest issue is there are some bugs happening with attendees being unable to see the photos, which has been a recurring theme with syncing events.

• Uploading a lot of photos takes a lot of time and storage at the moment, so we’re restricting it to one upload at a time at the moment. However, with server upgrades and database storage increases we could address this issue.

Test Flight Integration: Anuj, Leah

Due Date: Feb 11th

Description: For this task our team set up the pipeline for pushing our code to TestFlight, migrating our builds away from ExpoGo and into the TestFlight environment.

Takeaways:

• With Juncture being available on TestFlight for team/professor access, we are setting ourselves up for success in the future when we need to demo Juncture.

• Since building for TestFlight is a non-trivial amount of work, laying down a foundation of the app being on TestFlight is helpful for the future. It will save us time when we do not have to do this process in the future.

• Additionally, now that the whole team has access it allows us a more concrete and accessible way for our team to discuss development.

Delete Calendar Event Sync: Anuj, Leah

Due Date: Feb 11th

Description: For this task we created logic so that when the event organizer deletes an event, that event should also be deleted from the invitees calendar.

Takeaways:

• This was a challenging task, but luckily we had insight from previous syncing systems.

• However, it still took us a while to figure things out since the systems were slightly different, and we had to be very careful of how we were accessing and updating our database when deleting events.

• This task and edit syncing were very similar, which also helped us work on them.

Edit Calendar Event Sync: Anuj, Leah

Due Date: Feb 11th

Description: For this task we created logic so that when the event organizer edits an event, that event should be updated on the invitees calendar.

Takeaways:

• This was a challenging task, but luckily we had insight from previous syncing systems. Since we had events being synced to invitees calendars already, we were able to base the new database rules we wrote on those previous ones.

• However, it still took us a while to figure things out since the systems were slightly different, and we had to be very careful of how we were accessing and updating our database when editing events.

• This task and delete syncing were very similar, which also helped us work on them.

Open Tasks:

Logo Survey: Alex

Due Date: Feb 15th

Description: After our initial Logo ideation, our team thought it valuable to send out a brief survey to get feedback on our designs and make revisions as needed.

Takeaways:

• Keeping the logo survey as short as possible will hopefully increase chance of full completion.

• Asking questions about the logo without the context of the app and then with the context will identify if there is a disconnect with the logos perception and our app as a whole, or if it goes well with it.

Swift funding Doc: Leah

Due Date: Feb 17th

Description: For this task we want to try and gain access to Swift funding to offset some of our development costs and potentially pay for features that will improve our demo for the DIGM Showcase.

Takeaways:

• It has been enlightening to consider our funding needs and goals. We’ve had good discussion of the timeline on when we need upgrades and features, and how valuable certain metrics are.

• We identified Nylas account connections as our highest funding priority, though luckily they are not needed until May when we begin testing more intensely.

  However, we also need Render and Supabase upgrades for server performance and storage respectively. We discussed a few plan options, and settled on the first paid tier for both.

• Lastly, we’re seeking recompense for the Apple Developer account purchase, but this is a lower priority since we already purchased it initially.

  
  

High-fi Testing Script: Alex

Due Date: Feb 17th

Description: For this task we are updating our testing script in order to reflect the flow changes being made in our new high-fi designs.

Takeaways:

• Focusing on main, large, changes in this testing sprint will allow for more in depth feedback on changes that matter the most and allows for further refinement even though some of those designs may be “newer”.

• Smaller changes made from mid-fi can be covered quickly or skipped in this round of testing.

High-Fi Prototype Designs: Jill, Nikki

Due Date: Feb 17th

Description: Using feedback gained from Mid-Fi testing, our team is iterating on our last major app designs for our MVP prototype, employing new flow elements and some significant revisions.

Takeaways:

• Beyond mid-fi feedback action items, we’re working on filling in design gaps and ensuring consistency across all pages.

• Beyond that, we’ve been iterating on how to communicate a cohesive brand through our design elements.

Visual Identity and Branding: Jill, Nikki

Due Date: Feb 21th

Description: For this task we are moving forward to visual identity branding, including logo design and other unique art asset exploration.

Takeaways:

• As the brand evolves alongside our high-fidelity designs, we’ve started to embrace the leaf-like shape stemming from Juncture’s logo, which has unlocked opportunities to create patterns and embrace this shape as a core part of the brand.

Show Invitee In-App Notifications: Anuj, Leah

Due Date: Feb 21st

Description: For this task we are creating the functionality that when a user is invited to an event, it becomes visible in their inbox.

Takeaways:

• This task is fairly challenging, and has been giving us some trouble. While we didn’t anticipate it being as difficult as it has been, we’re struggling with how to proceed.

• Our current system that we’re testing avoids creating a new collection in our database, but we anticipate needing to adjust that as we polish up this task.

• For event based notifications, we currently have them being tied to the events. But for other notifications that might come from other sources, this won’t work. Thus, we might need a more dedicated/effective place to store notifications.

• However, we do have some success from this task-- our “Going/Not Going/Maybe” system is synced up and works. This is a good sign, since it’s important to indicate availability.

New Tasks:

Lobby Poster Final: Jill, Nikki

Due Date: Feb 21st

Description: For this task, we will take all the feedback we receive to update and refine our lobby poster designs for next week's due date.

Download Photos to Camera Roll: Anuj, Leah

Due Date: Feb 21st

Description: For this task, we are preparing to implement functionality that allows a user to download a photo out of juncture to their personal camera roll.

Invite a User to an Existing Event: Anuj, Leah

Due Date: Feb 21st

Description: For this task, we are creating logic that allows an event owner to invite a user to an event that already exists.

Remove a User From an Existing Event: Anuj, Leah

Due Date: Feb 21st

Description: For this task, we are also creating logic that allows an event owner to remove a user from an event that already exists.