Meetings:

Jan 20th, 45 min:

All team members present and on time

Agenda:

• Go over pipeline deliverable

• Recruitment for mid-fi touchpoint

• Testing script/schedule

• design system touchpoint

• dev touchpoint

• Jira scoping

Jan 23th, 2.5 hrs:

Leah absent but excused

Agenda:

• Jira Touchpoint

• Reviewing team progress and working session

Closed Tasks:

Mid-fi Testing Script: Alex

Due Date: Jan 19th

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.

Design to Dev Pipeline: Nikki, Anuj

Due Date: Jan 19th

Description: Per an instructor request we needed to show an example of our design to dev pipeline in action

Takeaways:

• Our pipeline consists of a robust custom figma library created by our designers with all assets and documentation needed for developers to code our pages within the design parameter

• Color, typography, buttons, lengths/widths, etc are all clearly laid out and accessible so that developers can quickly and easily see how to implement a design in their environment.

Mid-Fi design System: Jill

Due Date: Jan 31st

Description: Our mid-fi component system is designed to streamline the hi-fi prototyping process and improve the design-to-development handoff. Components are organized and documented for efficient use, indicating which elements are pending further iteration based on mid-fi testing feedback.

Takeaways:

• We have documented that some components are pending depending on mid-fi testing feedback, and these will be completed after testing synthesis and another design iteration.

• Going forward, design gaps have been documented, allowing the design team to prioritize refining these areas during the hi-fi stage while quickly integrating existing components.

Initial IX Flows: 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

Takeaways:

• Setting up IX rules for all features we’ll likely have for our MVP, keeping in mind that some features may be redesigned during the hi-fi prototype

• Noting down features that would have the same microinteractions for consistency

• Ideating best practices for microinteractions and IX flows to prepare for when we develop them

Calendar Comparison feature: Anuj, Leah

Due Date: Jan 31st

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 was much more difficult than expected. While we experimented with using Nylas' availability endpoint, we also explored using our own system to compare availability. It was a frustrating process

• It was also difficult to create the “Compare Availability” view, as it was somewhat different than a normal calendar.

• Furthermore, restructuring with our calendar library 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 used CRUD to edit/update event in firebase db.

• Implementation required consultation with designers in order to correctly handle the execution of this feature

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:

• Final research on implementation is needed but this functionality very much mimicked that of the "edit event ticket"

Upload Profile Picture: Anuj, Leah

Due Date: Jan 23rd

Description: The user can now upload a photo to be used as their profile photo within Juncture. This appears to their friends and on their profile page.

Takeaways:

• This task was fairly straightforward. Since we’d already worked on image uploading for the thumbnails, this was merely an extension of that process.

Show Current Month Name: Anuj, Leah

Due Date: Jan 23rd

Description: Users will be able to see month name when they scroll through different months

Takeaways:

• This was very straightforward task. We had to get current month name when we change months, so we added an event listener for this.

Show Suggested Friends List: Anuj, Leah

Due Date: Jan 19th

Description: When a Juncture user hopes to invite friends to an event, they should see a list of suggested friends.

Takeaways:

• This task was a little difficult to implement, but not too challenging. While we had to discuss a little bit as to what the list would look like (is it sorted? is it “smart” as to who you might invite?), we ultimately decided that for MVP implementation it was fine to just go down the line of the user’s friend list.

• Since we had to use the database, the challenge was in making sure we were gathering the right information and doing so efficiently, but we managed this. This reaffirmed our current database design, since the information was easily accessible.

Add Events to Invitee's Calendar: Anuj, Leah

Due Date: Jan 27th

Description: When user will be invited to an event it will show in their calendar.

Takeaways:

• This was a very challenging task to do. We had to write some database rules in order to add allow event organizer to add calendar event to the invitee’s calendar. Manipulating permissions in this way was not easy, and it required us to be very careful as to not affect data we did not intend to.

• Luckily, despite the challenges we managed to complete the task, and gained a better understanding of using database rules effectively. While we still need to update some of how the event syncing happens, the core system for this task is done.

Add Color to an Event: Anuj, Leah

Due Date: Jan 27th

Description: Users should be able to select and apply different colors to individual calendar events

Takeaways:

• While this task was straightforward for the most part, we did have to fight our calendar library a little bit.

• The library we are using needs a very specific set of requirements to get color customization when creating events, so we had to write code that fit within those restraints. This added a little more work than just having a user select a color and passing that color to the component’s style, for instance.

• Regardless, it gave us a better understanding of the library since we now know more about how event coloring works.

Add friends to Friend List: Anuj, Leah

Due Date: Jan 27th

Description: A juncture user should be able to send and receive friend requests. When those requests are accepted, the two users will become connected within Juncture.

Takeaways:

• This task built upon previous work using the “share calendar” feature. However, this time, we created a more robust friend system. The old system was sharing a whole calendar, but we just wanted access to that friend’s availability data for event creation, and a connection to them for inviting to events.

• Now, you can send someone a friend request. Once accepted, you’ll be friends with each other. We had to be careful as to how we managed things on the database side, as we needed to ensure that things were linked between both parties, and to preserve requests that were “pending.”

Open Tasks:

Mid-fi Testing: Alex, Team Support

Due Date: Feb 2nd

Description: For this task we are officially conducting testing on our mid-fi prototype. We have conducted 6 interviews so far and plan to do 4 more in order to go gain a meaningful amount of feedback of 5 participants per section.

Takeaways:

• Preliminary findings suggest that we may be giving the user too many options on how to create an event. Currently they can manually make a time, add friends and use the suggested times, or add friends and compare their availability, which may be too much at once.

• Preliminary findings suggest that our "Compare Availability" screen has become a lot more clear when compared to feedback received in low-fi testing.

• Preliminary findings suggest that the inbox for notifications could have more distinction between action items and non-action items.

New Tasks:

Visual Identity and Branding: Jill, Nikki

Due Date: Feb 11th

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

Show Invitee In-App Notifications: Anuj, Leah

Due Date: Feb 9th

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

Upload Photos to an Event: Anuj, Leah

Due Date: Feb 9th

Description: For this task we are building out the core functionality of our photo sharing/upload feature in app.