Sircles Work Session

1. Server Stability & Midnight UTC Disruptions

Engineering reported a major breakthrough regarding the daily CPU spikes and server lag occurring at midnight UTC. After an exhaustive log review, the team determined the issue was not caused by internal code or cron jobs, but by the default AWS Elastic Beanstalk "log rotate" functionality, which attempts to zip and clean logs every midnight . To resolve the disruption during peak hours, the team decided to shift this process to 11:00 AM UTC (approx. 3:00–4:30 AM for local developers). Code changes for this timing adjustment have been made and will be deployed to production tonight to ensure a smoother experience during high-traffic periods.

2. Web View Performance & Enhanced Interactivity

The web view has seen significant progress, particularly with the implementation of an "infinite scroll" component that has greatly improved scrolling fluidity . While early testing revealed intermittent freezing when scrolling over specific UI cards, engineering was able to resolve these issues by refining the list's configuration . The team also successfully integrated message reactions into the web interface. To further enhance the experience, developers are transitioning from lazy loading to eager loading for images to prevent "popping" artifacts, and they are investigating the addition of a "Listen Live" button for podcasts to match the app's functionality .

3. Permissions & Device Logic Refinement

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 previously denied, the app now directs the user straight to their device settings to toggle the permission manually rather than failing silently . Additionally, there was a discussion about potential refinements to the clipboard-based invite check to eliminate false positives by specifically detecting rare text formats, though the team noted that standard mobile libraries for this are somewhat limited .

4. Link Previews & Dynamic Sizing

A new initiative is underway to improve internal link previews so that sharing an invite from one chat to another displays the appropriate image and metadata . Developers identified that a lack of backend dimensions was causing "scrolling jumps" as the frontend struggled to calculate image and video sizes after they loaded . To fix this, the backend will now return width and height data directly, allowing the interface to render the correct layout immediately .

5. Architecture Stability & Environment Debugging

While the new architecture is approaching a stable state, the team is working through several navigation bugs, such as a glitch where tapping a topic notification incorrectly redirects the user to the home screen . This was traced to a JavaScript reference being cleared too early in the navigation cycle . Some developers reported significant time lost to local environment issues, specifically with Xcode 16 compatibility on the older architecture . Despite these hurdles, a comprehensive team-wide QA session is planned for Monday to stress-test the new architecture build in a production-like environment.

6. International Onboarding & Authentication

The team continues to examine onboarding strategies from other social apps to improve conversion rates for international users. One identified improvement is detecting when an SMS verification code fails and automatically offering WhatsApp as a fallback method . This approach has proven successful in other regions where standard SMS delivery is unreliable . Leadership remains focused on troubleshooting why thousands of generated invites in markets like South Africa are not resulting in clicks or installs on Android devices .

button in the chat interface?