Sircles Work Session

1. Server Testing & Pipeline Infrastructure

The engineering team reported that they have successfully resolved the issues with the broken test cases on the GitHub pipeline . All builds are now passing, and the team is continuing to add more server-level test cases for the message module to ensure long-term stability. A request was also made to identify new high-priority tasks while these foundational tests are being finalized.

2. Web View Development & Enhanced Interactivity

Significant progress was demonstrated on the web view, specifically with the implementation of an "infinite scroll list" library that has made the scrolling experience much smoother . The latest demo showcased functional message reactions and topic switching, though browser-based "long-press" actions are still being refined to prevent "trigger-happy" popups during normal clicks . Strategic updates now allow the team to open or close web chats on demand from the backend, and they are currently working on a manual screening queue in the admin portal to approve or deny initial messages from web-based participants .

3. Performance Diagnostics & Sentry Integration

The team investigated widespread reports of app freezes and sluggishness, identifying the latest version of Sentry's session replay as a likely culprit for "application not responding" errors on Android . Consequently, the team has downgraded Sentry to a previous stable version in the latest builds to eliminate these freezes . Developers also addressed an excessive logging issue where component rerenders were triggering multiple logs per second, and they are testing new experimental canvas-capturing strategies to improve UI performance .

4. Architecture Stability & Navigation Fixes

Development on the new architecture continues with a focus on resolving several navigation bugs, including a glitch where tapping a topic notification incorrectly redirects users to the home screen . This was traced to a topic reference being cleared prematurely in the JavaScript logic . The team also successfully fixed a "scroll jump" issue occurring during pagination by adjusting the Apollo cache fetch policy to prevent new data from overriding the existing list position . A comprehensive QA session with the full engineering team is planned for Monday to stress-test these features before a full production release .

5. Media Sizing & UI Improvements

Developers have polished the dynamic sizing for images and videos in the new architecture, ensuring full media capture fits the screen without overflowing . This logic now pulls height and width data directly from the backend to prevent "scrolling jumps" that occur when the frontend calculates dimensions after a file loads . Additionally, the team is working on a "Listen Live" button for podcasts, which will include a small animation and be dynamically hidden from the backend when a stream is offline .

6. Permissions & Security Measures

The team addressed a recurring issue where the camera would fail to open if a user had previously denied permissions . The logic was updated to check for existing permissions first; if they are missing or were denied, the app now directs the user straight to device settings to toggle the permission manually . Security efforts also remain focused on identifying bad actors using VPNs and UK-based burner numbers to bypass carrier checks, with the team investigating specific carrier patterns to improve manual review flagging .

7. Backend Performance & Image Corruption

Engineering investigated a critical issue where large images (over 45 MB) were failing to load due to a transformation process that was unnecessarily adding watermark properties twice, leading to corrupted URLs . A fix has been implemented to verify existing properties before adding new ones . Regarding general performance, a breakthrough was made regarding recurring CPU spikes at midnight UTC; the issue was traced to AWS Elastic Beanstalk's default "log rotate" functionality . To resolve the lag during peak hours, this process has been shifted to an off-peak time of 11:00 AM UTC .

8. Strategic Onboarding & Market Challenges

The team continues to examine onboarding strategies from other social apps to improve conversion rates for international users, specifically noting how some apps offer WhatsApp as a fallback for failed SMS codes . Leadership remains focused on troubleshooting why over 1,600 invites generated in markets like South Africa have resulted in only six conversions on Android . To address this, the company plans to engage local regional marketing agencies to identify technical blocks and tailor the promotional strategy to local cultures .