Lolo Patch Notes
Lolo Patch Notes — June 20 to 26, 2026
Lolo is like Find My Friends for your broader social, professional, and community graph. This week was mostly about making the mobile app more reliable, making Smart Plans feel more alive, and giving the map better feedback as the network grows.
What shipped
- Smart Plans got better notifications: Lolo added more notification support around plan activity, including join requests, RSVPs, messages, venue updates, reminders, and attendance-style follow-up moments.
- Plan sharing controls improved: plan owners can change a Smart Plan between private and public from Upcoming, and the Share sheet now has cleaner dismissal behavior.
- iOS X login became more reliable: the mobile callback loop was fixed, the X OAuth handoff was restored to the more reliable Twitter universal-link path, and Lolo added recovery for post-auth chunk-load errors.
- The map loading indicator returned: Lolo brought back a small, cleaner loading spinner so users get visible feedback while map people, places, and boundaries are loading.
What improved
- Mobile auth and onboarding got steadier: native deep links, Phantom callbacks, session handoffs, notification routing, and nearby-suggestion paths all received reliability work.
- iOS push plumbing improved behind the scenes: native iOS push registration and token syncing were tightened so Lolo can make mobile notifications more consistent in future builds.
- Map and backend load were reduced: adaptive polling, TTL caching, batched boundary work, friends summaries, and request logging reduced unnecessary Supabase/API pressure as the map scales.
- Message and friend data paths were cleaned up: fixes addressed unread group behavior, friends summary reads, avatar proxying, and request-storm edge cases that could make the app feel noisy or slow.
- Profile images got more resilient: profile avatar handling and server-side thumbnail support were cleaned up so map and profile surfaces can show people more consistently.
- Email verification is less brittle: verification flows were made less dependent on a single active session, which should make account confirmation more forgiving.
Growth/community notes
- Lolo crossed 10,000 signed-up users: the latest internal snapshot this week showed 10,506 signed-up users, 5,861 people who have pinged on the map, and 4,617 active map pings at that point in time.
- The network is getting more global: a fresh geography snapshot showed active usage across cities including São Paulo, Bogotá, Santiago, Lima, and San Francisco, with strong all-time ping volume across Argentina, Thailand, Colombia, Indonesia, and the United States.
- Contact-based growth is being prepared, not launched yet: native contact-sharing entry points were worked on, but the visible contacts banner was intentionally hidden until the mobile release actually supports that flow.
What’s next
- Retest iOS in the real world: confirm App Store 1.0.5 availability, retest X login on-device, and verify that users who grant location permission reliably appear on the map without manual repair.
- Keep pushing notifications for mobile 1.0.6: the next pass is focused on more consistent iOS push, Smart Plans notifications, “Did you pull up?” attendance prompts, and contact-sharing/contact-import support.
- Make Smart Plans more flexible: upcoming product asks include distance indicators on recommendations, a Remix button for alternate places, better multi-step plan understanding, and Spanish defaults in Spanish-speaking contexts.
- Improve App Store presentation: the App Store listing and screenshots still need a broader polish pass now that the mobile app is moving through early distribution.
- Keep growth loops honest: referrals, Circle links, X friend discovery, and contact imports should keep being measured by real signup, ping, friend, message, and plan behavior — not just clicks.
Source notes
- Compiled from the Lolo agent brief, the Lolo open-loop tracker, recent Hermes session search, and
git log --since='7 days ago'onconsort-tech/lolo-mvp-1. - Items described as shipped are backed by main-branch commits or durable project notes. Mobile distribution, contacts, and real-device iOS behavior are labeled as rollout / verification work where confirmation is still pending.
- No secrets, tokens, private operational details, or unverified private implementation data are included here.