Status Post 4: The Finer Things
Jan 15, 2026

Completed Tasks
Desktop Designs
Person Responsible: Enoch, Chem
Due Date: Jan 15
We are finalizing our desktop designs. In many cases we are just increasing font, margin, and spacing by 1.5. The goal is to maintain the same look, feel, and experience. The main interactive difference involves adding hover effects that aren't possible on mobile. Unlike many social media services, like instagram, we want our desktop view to be as intuitive and functional as our mobile version.



High Fidelity Testing
Person(s) Responsible: Gavin, Max
Due Date: Jan 8
The onboarding steps had some confusing language that broke up the experience a bit. We want to make sure that there is no room for confusing in this language, we will revise it for clarity.
The current friction modal might lack impact, while our users agree with it in concept, in practice most users said they don't imagine it being very effective. Some users even said they don't imagine there will be an opportunity for doomscrolling considering the nature of the app, making it obsolete. We will include this in our first beta version and test it live to determine if it is necessary.
Users embraced the idea of having comments with those you are not connected with appear under an anonymous user. This could allow for important context without compromising privacy or performance.
One user suggested having the ability to request to see who an anonymous user is (should they want to connect, or just know who they are talking to). Giving agency of privacy and digital connection to the user.
The Emoji Reaction Experience still leaves a lot to be desired - users were confused where to react. A lot thought the already-reacted emojis were quick reactions instead. We need to revisit the design here.
There was a lot of confusion on the difference and purpose of posting to your feed and posting to your profile. They were in different spots, and at points accomplished the same function and at points didn't. rather then making the user choose whether a post goes to profile or the feed by having two different post buttons in two different place, we are going to change our strategy to having one post button and a toggle at the end that allows the user to save the post to their profile.
There is more work to be done in explaining and intuitively designing branches, not every user understood how they function entirely. Once explained they appreciated the feature, we just need to bridge that gap between understanding and interaction a little better.
Another user suggested that we make the profile a little more customizable. They wanted the ability to reorder the profile items to the way they see fit.
New Feed post-card
Person(s) Responsible: Chem
Due Date: Jan 15
We are updating the post card view to be more visually appealing and improve specific experiences:-
Condensing the title and caption into one block
Rearranging the emoji reaction experience
Improving the entry point for comments to be more intuitive.

Back-end Functionality
Person(s) Responsible: Ella, Max
Due Date: Jan 15
We are working on finalizing the back-end functionality for our web-app. We want to make sure everything functions so that the only things left to do is develop the design and interactions.

Post-in-feed life span Discovery
Person(s) Responsible: Gavin
Due Date: Jan 15
I found articles and studies that will be used to inform how long a post should live on the feed within Loam based on how long posts receive interaction on certain platforms. One study focused on people’s post tendencies on WeChat which encourages limiting who sees your posts and how long they can see it for which was pretty helpful, they studied 21 people for 15 days and found that they post an average of 3 times a day when sharing to only close friends or family and they tend to use the option that only lets people see it for 3 days.
After studying millions of posts on Reddit, In summary, while information can hop between networks in minutes, its active lifespan is largely confined to the first 12 to 24 hours, after which new interactions become negligible. On Facebook, for younger users (ages 18–30), the average lifespan of a post, the point at which engagement peaks, is approximately 7 hours but some interaction continues until about hour 50. On instagram the interaction happens much quicker in the first few hours of a post but has a slightly longer lifespan with an average of 55 hours before interaction completely drops off.
Open Tasks
New Posting UX Exploration
Person(s) Responsible: Dom
Due Date: Jan 15
In response to our frequent feedback suggesting that our posting experience is lacking, we are exploring a new UX for posting that involves concentrating everything to one view/wizard.
All posts (to the feed and profile) will come from the post button in the nav bar. The user will see options for image, text, prompts, listening, watching, reading.
They will also have the option to save the item to their profile in this view

Front-End Dev Strategy
Person(s) Responsible: Ella, max
Due Date: Jan 19
We need to establish a plan for getting the front-end of the site done. We want to be as efficient and organized as possible, and get help from other members of the team, meaning we need an organized plan to get started.
Physical Product Development
Person(s) Responsible: Chem
Due Date: Ongoing
We are in the process of iterating renderings for the physical caribiner product.
NFC Tag Exploration
Person(s) Responsible: Max
Due Date: Ongoing
Playing around with NFC tags to see how we can implement the physical product within the web-app. The goal is to have it open to the owner's profile, we will see if that is realistic.
Design System Finalization
Person(s) Responsible: Ella
Due Date: Ongoing
As we wrap up the majority of our design, we need to make sure our design system is finalized as well. This will help inform how we want to set up our components and styling in dev.
Notification Strategy
Person(s) Responsible: Joe
Due Date: Jan 21
We need to established a notification strategy that is ethical and logical within the limits of email notifications. Because we are doing a web-app, email notifications are what we rely on to notify users of important info, we need to establish some logic for what those notifications should be.
New Tasks
Anonymous Comment flow
Person(s) Responsible: tbd
Due Date: jan 21
We need to finalize our strategy and design for how anonymous comments will function. We received positive feedback in our testing so we know that some form of it should be implemented. We need to finalize our flow for what they will be.
Lobby Poster
Person(s) Responsible: tbd
Due Date: tbd
Waiting on further instruction.
Onboarding Language Refinement
Person(s) Responsible: tbd
Due Date: Jan 22
Based on feedback from our testing we need to revisit our onboarding language for clarity
Icon Library Refinement
Person(s) Responsible: Chem, Enoch
Due Date: Jan 22
We need to finalize our icon library for dev and design. This includes icons for things like listening, watching, buds, branches, etc.
Component Building
Person(s) Responsible: tbd
Due Date: tbd
We need to start styling and implementing components in the web-app for consistency through out.
Meetings
2026-01-08, In Person
Whole Team
Agenda
Desktop views
Hi fi changes needed
when looking at another users profile, nav menu should disappear
settings and connections management should not be modal
Make onboarding more geared toward desktop sizing
match sizings to design system / 1.5 everything
branches are too wide
lower the width on the request/requested/connected
“What are you reading” size and boldness
Archive layout should match profile
another version of the feed view
clean up emoji reactions (overlap, shadow, etc.)
cleanup where the reaction button goes
check in on design system
carabiner check-in
feed time limit?
how often should feed be updated
Components needed
Front-end dev plan / whats left for back-end
live set testing plan
2026-01-12, Zoom
Max, Dom, Joe, Gavin
Agenda
Check in on Final desktop and HiFi updates
Check in on posting ux exploration
established that more exploration was needed but refined the direction further
Joe working on notifications
Dev check in
Physical product check in
Research Check in
Project
About
Blog
Contact
Resources
GitHub
Team
Status