Status Post 02: More Cronchy Updates
Nov 11, 2025
Closed Tasks
Research Deliverables for Status Post 01 - Yi Huan
Due Date: 10/29/25
Task Time: Yi Huan (2 hrs)
Description: I optimized the Research Team deliverables for Status Post 01, including Affinity Map, NUF Analysis, Gantt Chart, Personas, and Journey Maps so that deliverable links led to full-screen images, instead of zoomed-out links. For the Affinity Map, I extracted the findings and reorganized them into a chart for improved readability and clearer visualization. For the NUF Analysis, Gantt Chart, Personas, and Journey Maps, I made sure to standardize the color palette with our new findings and update the links for Status Post 01.
Deliverable: Figma File to Research Deliverables
Takeaways:
In the process of reorganizing the Affinity Map, I realized some things could have been better categorized, and some labels could have been better phrased.
New category for “User Emotions” relevant to the journey maps.
Jira Setup - Yi Huan, Yen, Maria
Due Date: 10/31/25
Task Time: Yi Huan (1.5 hrs), Yen (1 hr), Maria (1 hr)
Description: This task involved learning the platform to utilize the productivity tools effectively and migrating all tasks over from the Gantt chart. All team members were promptly invited to add any additional tasks and to update tasks with deliverable links. Notifications were also customized to nudge members within respective teams when a new task is added, adjusted, or commented on.
Deliverable: Jira - All Tasks
Takeaways:
Jira might not be our most optimal project management tool.
A lot of features to customize and research.
Jira has a lot of potential.
Database Development - Maria
Due Date: 11/03/25
Task Time: Maria (1.5 hrs)
Description: I set up Supabase as our backend to manage user logins, databases, and API connections within our SvelteKit 5 project. I created a new Supabase project and connected it to our local environment for testing. Using the terminal and browser, I confirmed that data could be read, written, and updated smoothly. This setup gives us a solid and secure backend that can grow as we add more features.
Deliverable: Supabase
Takeaways:
Supabase works well with SvelteKit 5 and supports live database updates.
Local testing showed fast and reliable performance.
Provides a strong backend foundation for future development.
APIs Integration - Maria
Due Date: 11/03/25
Task Time: Maria (4.5 hrs)
Description: Based on the APIs Research document created in our first sprint, I ran a series of integration tests to evaluate how the Spoonacular API and Tesseract.js fit into our development stack – SvelteKit 5, Supabase, and GitHub. The goal was to confirm compatibility, performance, and ease of setup before implementing these tools in our main project. I tested API calls, receipt scanning, and data handling via my local terminal to ensure smooth communication between the APIs.
Deliverable: API Testing Branch
Takeaways:
Spoonacular API offers easy integration for tracking grocery costs, supporting mindful spending with instant access.
Tesseract.js is an open-source OCR tool that makes it ideal for receipt scanning without specific, complex API keys.
Since both integrations ran successfully without major issues, we are confirming they can be effectively incorporated into our future builds.
Screener Survey - Sreeja, Fei, Yi Huan
Due Date: 11/04/25
Task Time: Sreeja (6), Fei (1.5 hrs), Yi Huan (4 hrs)
Description: This survey was created to collect data about who our demographic was and to validate our product. By collecting concrete data about our users, their usage of groceries and budgeting, and overall pain points, we gained a greater understanding of our target audience and features to implement in our overall design. The survey consists of three parts: General Data/Interest, Deeper Dive, and Contact for Further Testing. To create the survey, the team each took a section to brainstorm questions for, then reconvened to edit and finalize everything. There were several adjustments even after the meeting to ensure a thoughtful survey was delivered. We took into account feedback following further revision by our team and other resources. Team Cronch plans on keeping this survey open for the full 20 weeks of this project for data collection. The survey is also set up so that, depending on what users answer in the first section of “General Data”, they may be directed to the end of the survey, skipping over “Deeper Dive”.
Deliverable: Responder Link for Screener Survey
Takeaways:
Always clarify, clarify, clarify to the most extreme extent.
Google Forms has the ability to conditionally move users past different sections based on their responses.
We can ask users what certain phrasings mean to them (Ex: what does automated portioning mean to you?).
Gained further understanding of our target audience and pain points to focus on in further iterations of our prototype.
Wireframe/Paper Prototype - Yen, Fei, Maria
Due Date: 11/04/25
Task Time: Yen (8 hrs), Fei (1 hr), Maria (1 hr)
Description: During the design meeting, the team reviewed sketches from each member and selected key frames to develop into the wireframe. Together, we defined the main navigation structure and established the primary user flow to ensure a clear and intuitive experience. After completing the first draft, we presented the wireframe during the Tuesday all-hands meeting for final feedback and approval, preparing it for print and integration into the upcoming paper prototype testing.
Deliverable: Wireframe/Paper Prototype
Takeaways:
Collaborating as a team allowed us to merge different design ideas into a cohesive layout.
Finalizing the navigation and user flow early helped us align on core interaction and ensure the design supports user goals.
Paper Prototype: Interview Script - Sreeja, Fei, Yi Huan
Due Date: 11/07/25
Task Time: Sreeja (3 hrs), Fei (2.5 hrs), Yi Huan (2 hrs)
Description: This interview script was written to provide structure for the testing of our first prototype and usability testing. While interviewers will be encouraged to follow the script as closely as possible, we are open to follow-up questions from users to gain more insight into their thought process as they navigate our app. To create this script, we broke down the writing process into 4 stages: brainstorming, draft 1, draft 2, and final draft. In the writing process, we made sure to introduce ourselves, encourage user feedback, ensure the inclusion of a user consent and confidentiality statement, and provide clarity to each question asked.
Deliverable: Paper Prototype Interview Script
Takeaways:
In this process, we found it critical for smooth script writing to read everything out loud to ensure a natural flow. This ensured that the script was written with a natural speaking cadence and would be read as smooth as possible.
We made sure to include in the script off-camera parts, like asking the user for consent before the recording. Writing these on our communal script ensured that our interviews would be as synonymous as possible.
While it is important to encourage users to seek clarity, it is also important to let them know that we will not be addressing confusions that arise from navigating the prototype to ensure that we address them as we iterate our product.
Format and Print Paper Prototype - Sreeja, Fei
Due Date: 11/07/25
Task Time: Sreeja (2 hr), Fei (2 hr)
Description: We took our wireframes and resized them to fit into an 8.5 x 11-inch or 2550 x 3300 pixel frame for printing. After reformatting and resizing each frame into a separate page to ensure readability, we printed and delivered a copy to each member.
Deliverable:
Takeaways:
Shifting between media types presented its own challenges. We needed to experiment with sizes to ensure that frames were not cut off while printing. We had to consider legibility and viewability of each screen to make sure no one strains to read content.
Color and Typography Validation Test Draft - Yen
Due Date: 11/10/25
Task Time: Yen (5 hrs)
Description: Based on the team color palette and the WCAG accessibility guidelines, I identified that the contrast ratio of our primary color did not meet accessibility requirements. To fix this, I revised both the primary and secondary colors and created two wireframe versions, one using the original color palette and one using the modified palette. These assets were handed off to the research team to begin user testing, allowing us to validate both color and typography choices.
Deliverable: Validation Test
Takeaways:
Identified color contrast issues that affected accessibility compliance.
Revised color palette to improve readability and visual hierarchy.
Prepared 2 versions to compare user perception and accessibility performance.
Ensured that both color and typography align with the overall branding tone and identity.
Download and Organize Deliverables - Fei
Due Date: 11/10/25
Task Time: Fei (2 hrs)
Description: To promote more organization, I downloaded all of our deliverables from their Figma files and converted them into JPEGs. This practice will save us time in the future when we are searching for assets to add to a case study.
Deliverable: Google Drive
Takeaways:
It is more efficient to refine, download, and compress the deliverables on the day of to avoid things getting lost.
It is important to inform the content team when a new deliverable is created.
Paper Prototype Testing - Sreeja, Fei, Yi Huan
Due Date: 11/11/25
Task Time: Sreeja (2 hrs ), Fei (2 hrs), Yi Huan (2 hrs)
Description: Each of the Research team members conducted 2 Paper Prototype Usability Tests to inform our design decisions. These are our initial interviews, and they provided us with more insight into how our design decisions are being received by our user base.
Deliverable: Recordings
Takeaways:
User testing helps us gain a better understanding of our app as we see it through the eyes of a new user.
We were able to catch small mistakes in both the usability testing wireframes and the script.
We found that there is some adlibbing to be done, but it ensures a more natural feel to the testing.
This round of testing was very insightful, and we will adjust the next round according to our experience and feedback.
Open Tasks
Brand Logo - Yen, Fei, Maria
Due Date: 11/11/25
Description: After Week 6, the team voted on the main logo concept. The design team will now continue refining and iterating on the selected design to develop the final version. This process will include adjusting proportions, refining typography and color applications, and exploring logo variations.
Analyzing Paper Prototype Interviews - Sreeja, Fei, Yi Huan
Due Date: 11/11/25
Description: Once we complete our 6 paper prototype interviews, we will upload the completed interview script and interview recording to our files. We will come together as a group and gather insights from our interviews, looking into common threads, pain points, and overall insights. We will relay this to the design team so that they can take this feedback into account for the mid-fidelity prototype.
New Tasks
Mid-fidelity Prototype - Yen, Fei, Maria
Due Date: 11/21/25
Description: After receiving feedback from the paper prototype testing conducted by the research team, the design team will begin implementing the suggested improvements into the mid-fidelity prototype.
Design System - Yen, Fei, Maria
Due Date: 11/21/25
Description: Using insights from the color palette and typography testing, the design team will develop a comprehensive design system to ensure visual and functional consistency across the prototype. This system will include standardized components such as buttons, inputs, icons, and text styles, establishing a cohesive foundation for the app’s interface and future iterations.
A/B Testing: Color and Typography Validation - Sreeja, Fei, Yi Huan
Due Date: 11/14/25
Description: The research team will take the Validation test script and test with users to validate our color and typography choices. We are going to complete A/B testing with two different versions of the same screens. We will ask users a series of questions and see which version they prefer, as well as their reasoning behind it. This will give us a concrete basis for our mid-fidelity prototype, where we will incorporate our color and typography choices.
Functionality - Reuben, Maria, Yen
Due Date: 11/30/25
Description: Our next focus for the dev team is building out the app’s core functionality. We’ll be working on incorporating the API receipt scanner code used for the test and coding new functions to display the acquired information to the users.
Frontend - Reuben, Maria, Yen
Due Date: 11/30/25
Description: We’ll begin developing the app’s frontend based on the designs we have from our Figma files. Creating the components on each page and then implementing them through svelte to create our alpha version
Meetings
All-hands Meeting: (10/28/25) | 1.5 hrs
Attendees: All team members present and on time
Meeting Agenda:
General Updates
Update your section with what you will update the team about (5 min)
Yi Huan Receipt App Demo (Fetch app)
Status Post (Fix before Wednesday midnight)
Fix links and make sure they move into new tab (Dev)
Summary of product Links to Figma should not be linked to the entire file
Move to prototype shareable link
Give dev team live links to adjust later on
Design + Research will need to adjust all figma file deliverables
Adjust template to reflect individual hours on a task
MM/DD/YY
“Deliverable” vs Deliverable link
Template (Reuben)
Task name will be header 3
Bold your: “Due date, Description”
Jira
Invite Jervo st966rc2
Deliverable docs for submission
Yen tried to add something in the timeline
Make sure to edit or delete
Design
Done with sketches → start wireframe this week
Gallery view vs list view (A/B testing potential)
Concerns with dev and fridge view screen (will the user know that the fridge is openable?)
Color palette research survey/testing
Brand logo
Typography
Style guide –removed
Information architecture of app - user flows
Helping to figure out what we should
User flow → wireframe → paper prototype → mid fidelity
Wireframe 1: paper prototype
Wireframe 2: wireframe/alpha
Design will have wireframe 1 by Thursday
Today and tomorrow – move sketches to figma
Thursday – put wireframe together
Screen size
Newest: iPhone 17 pro
Most commonly used:
1170 x 2532 pixels for the iPhone 13/13 Pro
1179 x 2556 pixels for the iPhone 15/16, 14 Pro models
Research
Focus on collecting users and starting usability testing
Collect more affinity mapping information?
Test colors and design choices
A/B Testing for each
Action Items:
FINALIZE 3-5 USERS
Create screener questions
Create survey questions to justify design choices (color, typography, vibes)
Competitor usability test?
Development
Done:
Added a README.md file (reflects landing page content)
Added short description of what Food At Home is in Framer LP
Action Items:
Remove “Assets” folder from GitHub Repo
Status Post
Fix links on Framer to open in New Tab
URL → Hyperlinked Text
Content
Done:
Added placeholders
Organized Teams and Google Drive
Added direct links to Framer and Jira
Upload all sketches to Teams and Google Drive
Action Items:
Rename all files “FAH-title”, Google Docs can read: FAH Title
Rename + organize logo sketch files
Add all Google Docs into folders on Teams
All-hands Meeting: (10/31/25) | 1.5 hrs
Attendees: Yi Huan, Sreeja, Fei, Yen, Maria (Reuben async)
Meeting Agenda:
General Updates
Update your section with what you will update the team about (5 min)
Jira updated!
Let Yi Huan know what new tasks to add to the Jira + who is primarily responsible for completing the task
Subteam meetings
Put hours into subteam meeting notes for status post updates
Next Tuesday we meet at Arterial Cafe at 9:30 AM : D
Design
Done
Cleaned up Figma file architecture except “Food At Home - Design”
Site mapping is done
A/B Testing
FAH app has 5 icon nav system – scanner in the middle
Left to right will be Home, Type A Categories (condiments, drinks, produce) OR Type B (specific fridge, freezer, cabinets, pantry)
Budget Snapshot (“This is how much you saved this month”)
Tab for analytics; tab for budgeting
Analytics – graphs, pie charts, snapshots
First draft of the wireframe is done
Should be good by Monday to start first round of testing
Research team starts with the script?
Wireframe done by tues
Put Insights + Analytics on the same screen
Use two button tabs to switch between Insights and Analytics
Not integrating bank account info
Action items:
Shift A/B testing for inventory screen (location/category) till low-fi prototype
Setting up for color palette and typography testing
Logo vote by the end of weekend, so we can have it by tuesday
Add a budget input section on wireframe
Research
Done:
Screener Survey: https://docs.google.com/forms/d/1f2RSfQcGYl9bseU3bU2yrGskIi-4Zk3VDGfZHwZPfss/preview
Kicks you out based on specific answers
Maybe add “there are no right/wrong answers – we’re only looking to see your experiences” or something like that
Action Items:
Refining screener survey based on group feedback
Send the survey out to people
Upcoming tasks:
Refining user testers based on screener survey results
Introductory qualitative interviews
Add a section during usability testing to gather further insights on the user’s personal grocery journey
Unstructured vs structured?
Walk us through a scenario?
Usability testing for a paper prototype
Development
Added a short description of what Food At Home is in Framer LP
Status Post
Fixed links on Framer to open in a New Tab
URLs are now Hyperlinked Text
Action Items
Begin testing APIs – Reuben’s thing?
Content
Continued cleaning up files
Uploaded deliverables
Action Items:
Rename all files “FAH-title”, Google Docs can read: FAH Title
Rename + organize logo sketch files
Add all Google Docs to folders on Teams
Convert deliverables to .webp format
All-hands Meeting: (11/04/25) | 1.5 hrs
Attendees: All team members present and on time
Meeting Agenda:
General Updates
Update your section with what you will update the team about (5 min)
Screener Survey
Ready to send out to as many people as possible and get responses by Tuesday
Next status post
Subteam meetings – record hours in subteam meeting notes for status post updates
Jira populated with tasks – please review (link)
Let Yi Huan know what new tasks your section has so that she can put them into Jira
Due date >> oldest >> newest
Add labels and change/edit ‘Status’ [completed: ~30 min]
Jira Guideline Doc [completed: ~ 30 min]
Team leads update deliverables for completed tasks on Jira by Friday, 11/07
Completed Tasks – team leads need to attach deliverables
Ground Rules
Schedule team Event
Competitor Research
Project Pitch
Setting up Teams Organization
Placeholder Images added to assets
Github Repository
Github File Structure Organization
Affinity Mapping
Personas
Revised Project Pitch
Gantt Chart
Color Palette
NUF Analysis
APIs Research
Framer Banner
Framer Setup
Sketches
Google Drive Folder System
Journey Mapping
In Progress
Wireframes – due Oct 31
User Flow – due Oct 31
Typography – due Oct 31
Database Development – due 11/03
Brand Logo – due 11/03
APIs Integration – due 11/03
Survey – due 11/04
Branding/Style Guide – due 11/07
To Do
Interview Script – due 11/07
Figma Prototype –
Design Systems –
Microinteractions –
Usability Testing –
Surveying –
Frontend –
Functionality –
Design
Changes to Wireframe
Change lists to inventory on the navbar, cause inventory is more important
Move grocery list to home page
Set a budget for the month
Add new item screen
Need more details on the analytics screen
Add wireflow
Paper prototype
Make any final changes before printing out for paper prototype testing
Paper prototype testing starts on Frida,y 11/07, ends on 11/11
Continue to work on the logo, will update on Friday
Action Items
Finalize the wireframe to get ready for paper prototype testing
Make the print size to print out
Research
Done
Finalized screener survey
https://forms.gle/xEzBDSL8t7ePMbvr9
Revisit weekly and monthly questions?
Ready to send out to as many people as possible and get responses by Tuesday
Action Items
Interview script 11/07
Settle on user testers based on responses
Analyze responses from Tuesday-Friday and settle on the list by Friday
Go to the first round of user testing
Paper prototype testing
Paper prototype testing starts on Friday, 11/07, and ends on 11/11
Development
Reuben will be inactive this week as he will be gone this Friday to Sunday
Refer to Maria for dev-related tasks while Reuben is MIA this weekend
Dev tasks are API integration and Database Development
Database Development will be set up in Supabase [complete: ~2 hours]
API integration will just be a simple test to see if recipe data can be transcribed on a page
Maria will start on API integration
Created a draft template for our Status Post 02 – remember to note down takeaways!
Maria will copy/paste most notes into the second status post
[draft created: ~30 minutes]
Content
Continued cleaning up files
Uploaded deliverables
Rename all files “FAH-title”, Google Docs can read: FAH Title
Action Items:
Rename + organize logo sketch files
Add all Google Docs into folders on Teams
Convert deliverables to .webp format
All-hands Meeting: (11/07/25) | 1.5 hrs
Attendees: Yi Huan, Sreeja, Fei, Yen, Maria
Meeting Agenda:
General Updates
Update your section with what you will update the team about (5 min)
Survey - 63 responses!!
Created Jira Guideline doc
This is so good
Status Post 02 is coming up!
Jira
Completed
Wireframes – due Oct 31
User Flow – due Oct 31
Database Development – due 11/03
APIs Integration – due 11/03
Survey – due 11/04
Interview Script – due 11/07
In Progress
Branding/Style Guide – due 11/07
Brand Logo first draft – due 11/11
Typography – due 11/18
To Do
Figma Prototype –
Design Systems –
Microinteractions –
Usability Testing –
Surveying –
Frontend –
Functionality –
Notes
Take off Sreeja’s account without the PFP
Design
No update on logo yet :( will be on Tuesday
Wireframe is ready to print out after the meeting, just need a little cleanup
Looking into color validation, the color palette is coming soon with more details
Color palette updates on Tuesday
We’re a little behind on schedule, probably need to shift everything back 1 week (might have to work on Thanksgiving)
Skip lofi → move straight into mid-fi prototype + mid-fi testing
Research
Completed
Survey
Interview Script - Interview Script
The paper prototype is printed
In Progress
Consolidating users to decide who to test with
To Do:
Finalize user list (3-6 people)
Clarify further testing
Paper prototype, low-fi, A/B testing, and then mid-fi?
Paper prototype → Mid fi → A/B testing
A/B testing time and method
For typography – how wide, how tall, how round for readability
The article says it usually compares serif and sans-serif
Out n About – can you tell me what you feel about this color, what words come to your mind when you see this color?
Show users colors one by one, then altogether
What do you envision when you see this color?
Development
Successfully tested APIs
Spoonacular API (for groceries, prices, images, etc.)
Tesseract.js (for OCR tech)
I can go through a quick demo…?
Refer to Maria for Status Post 2/any dev work since Reuben will be MIA
Content
Pulling deliverables and placing everything in folders on Teams and Google Drive
Al files have been renamed to FAH -
Complete transfer of deliverables to teams
Each team (except dev) should have a JPG (final deliverables)
Yes! Rename Figma files to “final deliverable - “persona”
Design Meeting: (10/30/25) | 1hr
Attendees: Yen, Fei, Maria
Meeting Agenda:
Sift through the sketches and see which screens overlap.
Wireframe first draft.
Created a wireflow to map out the site map.
Research Meeting: (10/29/25) | 1.5 hrs
Attendees: Sreeja, Fei, Yi Huan
Meeting Agenda:
Talk through screener vs. survey (potential integration)
We should gather statistics from user data to back up why our problem is insightful
Kind of going back to the drawing board
***Integrate screener into quantitative data survey
Screener:
Purpose: to gather users
Gather insights on demographics
“I struggle with…”
X amount of people struggle ___ problem
Push out for 2 weeks
Finish by eod today (10/29)
Survey planning (30 min)
User information
Current experiences with grocery stores
What will help you streamline?
Are you willing to participate as a user tester for each iteration of our app?
Research Meeting: (10/31/25) | 1.5 hrs
Attendees: Sreeja, Fei, Yi Huan
Meeting Agenda:
Finalize Screener Survey
Revise language and streamline questions
Take out questions that are better for qualitative testing
Research meeting: (11/07/25) | 1.5 hrs
Attendees: Sreeja, Fei, Yi Huan
Meeting Agenda:
Go through the interview script and finalize
Go through the script step by step to make sure text is smooth when speaking
Go through future testing phases and audit schedule
Paper Prototype Usability Testings:
Lo-Fi Usability Testings:
A/B Testings:
Mid-Fi Usability Testings
Select users to test based on responses
Framework: (20-28 min for actual interview)
Introducing the session (1-2 min)
Participant Introduction (6-8 min)
Preparing for the Main Task (1 min)
Main Task- Paper Prototype (10-15 min)
Wrap Up (2 min)
To do:
Test users and analyze findings
Done:
Script - Draft 1
Intro - Participant Information: Sreeja (1 hour) and Yi Huan
Main tasks - Conclusion: Fei (30 mins)
Script - Draft 2
Whole Team (1 hr)
