Meetings:

Feb 17th, 1.5 hrs:

All team members present and on time

Agenda:

• Lobby poster review and discussion

• Hi-fi review

• Logo survey dissemination and hi-fi script

• Hi-fi testing prep

• Branding touchpoint

• Jira Touchpoint/dev updates/demos

Feb 20th, 2.5 hrs:

All team members present and on time

Agenda:

• Logo survey review

• Sketches review/Hi-fi realignment

• Jira touchpoint

Feb 24th, 1. 25 hrs:

All team members present and on time

Agenda:

• High fi changes review

• UX testing script/signup check in

• Jira scope assignment and realignment

• Intitial Beta Presentation discussion

Closed Tasks:

Swift funding Doc: Leah

Due Date: Feb 17th

Description: For this task our team applied for 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 requested 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 sought to recompense for the Apple Developer account purchase, but this is a lower priority since we already purchased it initially.

Lobby Poster: Jill & Nikki

Due Date: Feb 20th

Description: After receiving feedback our team made edits and refined our Lobby poster for Juncture to the finalized version seen below.

Takeaways:

• We reorganized the layouts of both posters to have more clarity with our content and branding after we were able to input more updated information.

• Insightful statistics were put where we had placeholders and we iterated on different taglines that would best represent our app until we found one that fit.

• We updated the prototype screens on the poster following what was updated in the hi-fi prototype.

Logo Survey: Alex

Due Date: Feb 20th

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:

• The logo is generally well-received, with 58.3% finding it appealing, and simplicity is its strongest asset (75% selected it as a positive aspect), though memorability is a significant concern (50% selected it as a negative aspect).

• Most respondents (54.1%) find the logo mostly or perfectly fitting for a social planning app, but many suggested adding elements that better convey the social/event planning aspect.

• Respondents selected that the logo conveys a professional and sleek personality and is perceived as modern, but may appear too corporate and not energetic enough for a social planning app.

High-fi Testing Script: Alex

Due Date: Feb 24th

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.

Visual Identity and Branding: Jill, Nikki

Due Date: Feb 24th

Description: For this task we consolidated and standardized our app's visual identity & branding, including logo design and other unique art asset exploration.

Takeaways:

• Building out a branded visual identity to apply in our app was done with the ultimate aim of curating our experience to to seem less sterile and more friendly than competitor calendars.

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

High-Fi Prototype Designs: Jill, Nikki

Due Date: Feb 24th

Description: Using feedback gained from Mid-Fi testing, our team iterated on our last major app designs for our MVP prototype, employing new flow elements and some significant revisions based on team discussions and realignment over Juncture's main value offering, the comparability feature.

Takeaways:

• Creating the hi-fi prototype allowed us to refine consistent visual identity and interactions within Juncture.

• We struggled with a design challenge around accommodating two equal pathways when choosing a time, and sketch ideations from each group member allowed us to align on two design solutions to A/B test. Alongside testing, we plan to align the design system with these updates in preparation for dev handoff.

Show Invitee In-App Notifications: Anuj, Leah

Due Date: Feb 24th

Description: For this task we created the functionality that when a user is invited to an event, it becomes visible in their inbox. This task also broadly includes most of the notification center functionality.

Takeaways:

• This task was fairly challenging, and definitely gave us some trouble. We had to iterate through a couple of different options-- first attempting a system that was heavily tied to events

• In order to proceed, we needed to prioritize the most critical notifications that we would display. Invitations being the most critical were thus first priority. Next, the event statuses (Going/Not Going/Maybe) were implemented. Now, when a user says whether they’re going or not, this will send a notification to the creator.

• While we have more notifications we want to and plan to implement, we felt that for the general completion of this task this was the best way to proceed. We feel strongly that this is a great place for us to expand upon as we progress.

Download Photos to Camera Roll: Anuj, Leah

Due Date: Feb 17th

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

Takeaways:

• This task was fairly simple to do. While it was lower priority, it took a negligible amount of time and is an important piece of the memory function. Thus, we felt it was worth implementing so we had it complete.

Memory Wall Sync: Anuj, Leah

Due Date: Feb 17th

Description: For this task, Event Creator and Invitee memory wall pages should be synced up to contain the same images for the same event.

Takeaways:

• With all of our previous experience syncing features between invitees and event creators, this task wasn’t much of an issue.

• We were able to take advantage of our previous database and code setups in order to establish this syncing functionality between memory walls.

Render Custom Header for Day/3-Day Views: Anuj, Leah

Due Date: Feb 17th

Description: For this task, we implemented functionality that implements our Hi-Fi Design's custom header into our latest TestFlight Build.

Takeaways:

• This task was a little bit tricky, but not too bad. We had to do a little research in the documentation of our calendar library, React Native Big Calendar, in order to achieve this.

• We had to investigate how to manipulate this header. Once we did so, we were then able to recreate the designs and intended behavior within Juncture.

• Being able to delve further in to our calendar library’s documentation gave us a better picture of what we were working with, which should streamline development if we encounter another issue with it in the future.

RVSP Status Update: Anuj, Leah

Due Date: Feb 17th

Description: For this task, we implemented a feature so that when a user updates their attendance status on an event, that should be reflected to other users and the event creator.

Takeaways:

• Since this task went hand-in-hand with notifications, it did give us a little trouble. We had to record the states of attendance accurately, and had to update older code in order to update this status dynamically.

• Previously, we had been doing a lot of more explicit work in the database to update the status, but with our new system we have eliminated that extra effort.

Remove User From Existing Event: Anuj, Leah

Due Date: Feb 20th

Description: For this task, we implemented functionality that allows an event creator to remove an attendee from their event.

Takeaways:

• This was certainly a little bit tricky; we had to update multiple calendars-- creator, invitees, and the user who was removed. However, we were able to utilize existing features, such as deleting and editing events, in order to inform our process.

• While the task still gave us some trouble, this previous work gave us a good jumping off point for us to implement this feature.

Invite Another User to an Existing Event: Anuj, Leah

Due Date: Feb 20th

Description: For this task, we implemented functionality that allows an event creator to invitee attendees they are connected with to an event. This invite should appear in the Notifications Center.

Takeaways:

• Similar to the “remove a user” task, we were able to base off of previous work here. Again, it was still not the easiest task in the world, due to the manipulation of our database and calendars we had to do, but it was far easier than it could’ve been.

• Since adding a user to an event was already part of the event creation process, it wasn’t too much of an additional burden to then utilize a similar flow once the event was already created. It just required a little additional tinkering.

Show Personal Google Calendar Events in Juncture: Anuj, Leah

Due Date: Feb 27th

Description: For this task, we are implementing functionality that allows a user's personal Google events to be seen within Juncture's calendar interface.

Takeaways:

• This task didn’t take a lot of effort as we have our Nylas API working. We conducted research as to what would be best way to import google calendar events data and juncture events data and combine them to showcase in one calendar view.

• We came up with a better picture of how we should be storing and manipulating our events, which gave us great insights into the future.

• However, we are having issues with event colors. Initially, we assumed that Nylas would pull the exact color from Google Calendar. However, Nylas seems to manipulate the color in a way which was unexplained in their documentation. While this isn’t necessarily a major issue, we do need to discuss with our designers to see how they would like us to proceed.

Open Tasks:

Beta Presentation Preparation: Entire Team

Due Date: March 13th

Description: For this task, we the entire team is preparing for relevant activities surrounding our beta presentation. This includes slideshow visual design with our Juncture Branding, content curation, and run through practice.

Takeaways:

• Currently the team is consolidating all of our relevant content and data for presentation preparation.

• Additionally, we are workshopping slide flow and assigning specific pages to team members based on subject matter.

Hi-Fi Testing: Alex

Due Date: March 7th

Description: For this task, we are performing a comprehensive final round of testing on our Hi-fi Prototype with the aim of getting additional feedback before coalescing around a final design structure for Juncture.

Takeaways:

• We have only done one testing session so far, but have several other scheduled in the upcoming week and a half, and will also be scheduling sessions with Troy and Jervo.

• For our testing we are splitting the participants into groups A and B, and, so far, the group A testing flow has gone smoothly without any hiccups. We have not tested a group B participant yet.

Design System Updates: Jill

Due Date: March 7th

Description: For this task, now that our hi-fi designs are finalized, we are going back and updating the design system to reflect these new design changes and decisions.

Takeaways:

• This will help streamline the design to dev handoff by having a clear documentation source for components and their variants.

Site Map: Nikki

Due Date: March 3rd

Description: For this task, we are creating designs for every possible page a user could technically navigate to that has not yet been created outside our main flow, including profile and settings pages to name a few examples. This will give us a complete and detailed site map of our entire application.

Takeaways:

• While in progress, we’re beginning this sitemap to visualize and analyze all of the different pages and features in our app so we know what will have to be designed, built, and connected.

• Will be using the IX Audit to help reference what features may need to be highlighted during this process.

IX Audit: Durando

Due Date: March 3rd

Description: For this task, we are creating a data hub of all Juncture's interactions. The goal of this list is to assess all of our interactions and catalogue them so everything is in place for our final IX flows.

Takeaways:

• This task has been proceeding at pace, it just is time consuming cataloguing every interaction we have but this task should be complete by the due date.

• Completion of this task will be helpful information to have prior to our final IX Wireflow activities.

New Tasks:

Final IX Flows: Jill, Nikki

Due Date: March 10th

Description: For this task, we will use the results of our IX audit as well as Hi-fi testing to create our final directory of all IX interactions within Juncture, focusing on Triggers, Signifiers, Loops, & modes. This will be used to guide developer refinement of our build in the coming months.

Figma UI Implementation: Anuj, Leah

Due Date: March 21st

Description: For this task, we aim to use our completed HI-fi prototype to begin porting over the majority of our Figma assets and designs into our development environment and start harmonizing our build's appearance with that of the designs.