Lolo Patch Notes — May 30 to June 6, 2026

Current numbers

Production Supabase snapshot measured June 6, 2026 at 22:54 UTC. Period metrics cover May 30, 2026 00:00 UTC through June 5, 2026 23:59 UTC.

Smart Plans became the main new product loop

• Smart Plans shipped into the product: The Plans tab now centers on a fast coordination flow: type what you want to do, confirm the plan, invite people, and turn it into a real plan instead of a heavy event-creation form.
• Venue help got smarter: Smart Plans can infer useful venues, rank options with route / ETA context, cap recommendations to a clearer set, show venue photos, and produce richer plan-pin sheets so the suggestion feels grounded.
• Plan chats are becoming useful: Plan creation can open a group chat with a dedicated Lolo agent member. The assistant now responds more readily in the plan chat, links back to grounded venues, and can show in-chat venue cards.
• Invites, RSVPs, and join requests improved: Public/private plan behavior, owner RSVP state, membership-aware Upcoming cards, request-to-join flows, host approval, and approve/deny actions from notifications all landed this week.
• Social planning got easier: Multi-name planning, chat @-mentions, username / profile-photo pickers, and plan member sheets make it easier to coordinate with actual people instead of abstract attendee lists.

Onboarding and social graph

• Onboarding got shorter: The first-run flow was tightened around the important early steps: add relevant people, then add a profile photo / username. Circles and generic X prompts are no longer the center of first-session onboarding.
• Add all for friend suggestions: New users can add the whole suggested set quickly instead of tapping through each person one by one.
• Better first people: Suggestions now prioritize recognizable, higher-quality accounts: profile photos, linked X context, friend-count signals, and credibility over blank or anonymous-looking users.
• Welcome from Lolo: The app can seed a welcome message and in-app notification from @lolo, pointing people toward nearby connections, the Network tab, and Plans.
• Referral leaderboard fixed: Joined counts and leaderboard credit now count when someone creates an account after using a referral link, not only after they later ping.
• Friend requests kept growing: In the measured last-7-day window, 805 users sent 3,070 friend requests. That is the graph-building loop to keep compounding.

Notifications and messaging

• Notification prompts moved to better moments: Lolo now waits for clearer context, like after welcome-message or notification-sheet interaction, instead of asking too early during cold onboarding.
• World App notification routing improved: World App users go through MiniKit notification permission requests, while regular web users stay on the web / OneSignal path. Unsupported browsers are tracked separately.
• Notification copy is cleaner: Dynamic preview templates, more natural actor names, and real person / event image previews make notification cards feel less generic.
• Group chats got leave controls: Group chats now have an overflow menu and confirmed Leave group action that removes the membership and hides the group from the list.
• Unread previews clean themselves up: Floating message / notification bubbles can be tapped, swiped away, and cleared when the underlying item is read.
• Messages are becoming a planning surface: Group members sheets, in-chat venue cards, @-mentions, and richer plan links make chat feel closer to the place where coordination actually happens.

Map, location, and mobile UX

• Map reliability improved: Mapbox lifecycle cleanup hardened the map against repeated mount / unmount issues, and exact map stats moved past the previous row-cap artifact.
• NYC boundaries got much better: First-time NYC users now default to useful city / borough-level pings instead of a too-broad state-level area, and Lolo remembers each user’s last selected ping granularity.
• Boundary rendering got polished: New York / Manhattan context is less likely to disappear, avatar anchors derive from boundary geometry when cached centers are stale, and map boundary behavior was tuned through several rounds of polish.
• Mobile sheets feel more native: Network, Events, Tap Area, filters, notifications, and sheet headers got more reliable swipe / grab behavior, fewer unnecessary close buttons, and better touch ergonomics.
• iOS layout got safer: Map controls now sit below the iOS status bar so the native shell does not crowd key actions into unsafe screen areas.
• Native location work started: The iOS shell now includes a native location bridge so location behavior can feel more reliable outside the browser.

Internationalization, community, and polish

• Spanish coverage expanded: Spanish translations now cover group chat, member sheets, venue cards, notifications, and plan pin details.
• Connect recovery improved: The Connect flow can recover from corrupted wallet session state and give users a cleaner retry path instead of leaving them stuck on wallet decrypt errors.
• Global map footprint: Lolo users have pinged from 61 countries in total, and 57 countries currently have live active pings on the map.
• Circle and token-community loops still matter: Circle links, referrals, and token-community spaces like the Velvet Circle continue to point toward the larger thesis: online communities becoming real-world communities.
• Profile and notification behavior remain key: The strongest activation still starts with pings, but the next retention gains come from profile completion, friend graph depth, notification opt-in, messaging, and successful plans.

What’s next

• Keep compounding the graph: Make first friends, friend requests, accepted friends, X context, referrals, and suggested people work together as one graph-growth system.
• Polish coordination details: Clickable links, message timestamps, scroll position, notification clarity, plan preferences, and host / attendee workflows are the next product-quality layer.
• Keep privacy legible: Lolo should continue to feel like “I’m around,” not live 24/7 tracking. Boundary-level pings, user control, Ghost Mode, and visible intent matter.

Source notes

• Compiled from recent Lolo project context, the Lolo agent brief / open-loop notes, production Supabase metrics, git log on consort-tech/lolo-mvp-1, and git log on consort-tech/lolo-mobile.
• Items described as shipped are backed by main-branch commits, mobile-shell commits, or durable project notes.